Who thrives here
- You have a specific recent example of something you deployed, owned, and got working for a real customer. And you care about what happens after the kickoff call.
- You’re comfortable with ambiguity. The most interesting problems here don’t come with detailed specs: you hear something from a customer, you figure out what to build or configure, and you do it. If you prefer a PM and a solutions architect to define the work before you start, this role will be frustrating for you.
- You find the domain genuinely interesting. The compliance constraints, the quality/logistics tension, the fact that what you deploy is moving medication to real patients: these should feel like compelling design constraints, not obstacles. An engineer who finds regulated industries tedious won’t do their best work here.
- You like customers. Not tolerate them, like them. The product and commercial decisions that come out of being in the room with an ops team are the ones worth making, and you’d rather be in that room than shielded from it.
- You’re honest about what you don’t know. We debate hard, change our minds, and challenge each other, but always with the assumption that everyone is trying to get it right.
This role is probably not right for you if you want to go deep on one hard technical problem and be left alone, or if customer contact feels like a tax on engineering time. The surface area is wide: deployment, integrations, core platform code, troubleshooting, and commercial. If switching contexts drains you, this will too.
What we’re looking for
You have 2-10 years of professional experience as a forward deployed engineer, full-stack engineer, solutions/implementation engineer, or in a similar role where you’ve owned customer-facing technical work. You’re genuinely full-stack: comfortable across backend, frontend, and APIs, and able to ship production code on a small senior team. You’ve built 0-1 products and you’re comfortable with the ambiguity that comes with them. You’re strong in TypeScript/React and Python, or close enough to ramp quickly.
You understand data modeling and API design, and you’ve done real integration work (APIs, ETL, webhooks, file feeds) and debugged it in production. You’re comfortable running technical onboarding and scoping integrations directly with customers. You’re based in San Francisco or Chicago and excited about being in the office.
Bonus: experience in logistics, supply chain, healthcare/life sciences, or another regulated, operationally complex domain.