Staff Engineer, Tech Lead

## The Role

We're hiring a **Staff Engineer, Tech Lead** to own the technical direction of the platform that moves a repair from intake to paid. This is the heart of ServiceUp: intake, routing work to the right shop, auditing estimates against policy, approvals, and payment, all against a real world of shops, adjusters, and vehicles that don't behave like a clean API. You'll set the architecture, lead a team through building it, and stay close enough to the code to keep us honest.

## What You'll Do

- Own the architecture of the core repair workflow and the services behind it, and make the calls that keep it coherent as it grows
- Lead a team of engineers: set direction, review the hard designs, and raise the bar on how we build
- Build for a two-sided reality where one side is fleets with policies and the other is independent shops with their own tools and habits
- Make money move safely: approvals, estimate auditing, and payment that have to be correct, not just fast
- Partner with product and operations so the system fits how repairs actually happen, not how a diagram wishes they did
- Set the standard for reliability, observability, and the boring things that keep an operations platform trustworthy

## What We're Looking For

- Deep experience designing and shipping backend systems in production, with real ownership of the hard parts
- A track record leading other engineers through ambiguous, high-stakes work without becoming a bottleneck
- Judgment about where to spend complexity and where to keep it simple, especially where money or human steps are involved
- You can go from a messy real-world workflow to a design the team can build and operate

## Strong Advantages

Nice-to-haves, not strict requirements.

- Experience with marketplaces, payments, logistics, or other operations-heavy domains where the real world is the hard part
- You've been an early senior engineer somewhere and shaped the architecture, not just inherited it
- Comfort across the stack enough to debug a production incident that crosses services

## Why This Role Is Special

The hard problem here isn't a novel algorithm, it's making a reliable, correct system out of a workflow that used to run on phone calls and email. You'll set how ServiceUp builds for the next stage, with a product that already has customers depending on it every day.

## Location

Remote in the US. The product team works distributed with regular time together.

## Next Steps

Tell us about one system you led where the real world was the hard part, and how you knew it held up. We care more about how you reason through a messy design than about a clean whiteboard problem.