Staff / Principal Software EngineerLocation: Lehi, UT - Hybrid (3 days/week in office)
Team: Clozd
Level: Staff or Principal (see How We Level This Role below)
The RoleWe're looking for a senior engineer who is equally comfortable shipping product and shaping the platform underneath it. You'll move fluidly between building features that users touch and the infrastructure that makes those features fast, reliable, and cheap to operate. This is a hands-on role: you'll still impact the code base through AI, but your leverage comes increasingly from the decisions you make, the systems you design, and the engineers you level up around you.
Because you span both the product surface and the platform, you'll see problems end to end - from a slow page load down to the query, the service, and the deployment that caused it. That perspective is exactly what we want.
What You'll Do- Design and build systems across the stack, from user-facing product features to the platform, infrastructure, and tooling that support them.
- Own ambiguous, high-impact problems from framing through delivery - you help decide what to build and why, not just how.
- Set technical direction for Clozd and drive alignment across teams on architecture, standards, and trade-offs.
- Improve the foundations: reliability, performance, developer velocity, and operational cost. Reduce the friction that slows everyone else down.
- Steadily increase and improve our AI leveraging efforts
- Raise the engineering bar through design reviews, code reviews, mentorship, and by example.
- Partner closely with product, design, and other engineering teams to turn goals into shippable, well-scoped work.
- Be a force multiplier - the projects you touch and the people you work with should get better.
What We're Looking For- Substantial experience building and operating production software, with real depth in both application/product engineering and platform, infrastructure, or DevOps.
- A track record of designing systems that held up under growth - and the scars to explain the trade-offs you'd make differently now.
- Strong fundamentals: distributed systems, data modeling, APIs, and the operational side (observability, deployment, incident response).
- Fluency across the stack - you can reason about a frontend performance problem and the database index that fixes it in the same conversation.
- The judgment to know when to build, when to buy, and when to delete. You optimize for impact, not novelty.
- Clear communication with both technical and non-technical audiences, and the ability to build consensus without needing authority.
- A history of elevating the people and teams around you.
We care about what you can do, not a specific number of years or a particular degree.
Nice to Have- Prior experience as a technical lead, architect, or in an equivalent org-wide role.
How We Level This RoleWe're open to hiring at
Staff or
Principal - the right title depends on scope and impact, and we'll calibrate during the process.
- Staff engineers drive technical direction within a team or domain, own significant systems end to end, and multiply the effectiveness of the engineers around them.
- Principal engineers operate across teams and the broader org, set direction on the hardest and most ambiguous problems, and their decisions shape the technical strategy of the company.
If you're not sure which fits, apply anyway - we'll figure it out together.
