Forward Deployed Engineer
Posted Aug 11, 2026
The role in short
Embed with healthcare customers to scope, build, and deploy production AI agents and integrations on the Carebricks platform, closing the loop from clinical feedback to shipped code.
We've run agents across 6M patient records and over 10M workflows in the last year, all on our platform, Carebricks.
We're hiring a founding forward deployed engineer to take us through the next 100M.
Healthcare is messy. The distance between a good clinical idea and a working system is enormous, and most of that distance is unglamorous: legacy system integrations that fight back, FHIR resources that arrive malformed from production endpoints, edge cases that change what happens to a patient. The rest is frontier AI work, where there's nothing to copy because nobody has built it yet.
As our first FDE, a typical week looks like:
- Stakeholder meetings. Physicians, hospital IT, clinical and operational champions. Anyone with an idea worth putting into production.
- Use case scoping. Work with internal and external champions to figure out how to productionize an idea, what success actually measures, and the path to get there.
- Use case building. Translate loosely defined ideas into concrete agents inside Carebricks. Build evals to ensure agents are doing what they're supposed to.
- Use case alignment. Ensure use cases continue to deliver value, whether that means updates to agents, updates based on the latest clinical guidelines, or updates based on operational considerations.
- Core engineering. Change the platform based on what you learned from users, and from using Carebricks yourself all week.
We're looking for great engineers who want real ownership. The loop from "a physician told me this is broken" to "the platform no longer works that way" should close in days, and you own the whole loop.
This role wants someone who can hold a conversation with a clinical champion in the morning and debug a production pipeline in the afternoon, and be customer outcome obsessed. If this sounds like a challenge you're up for, we want to meet you.
Our engineering team has 3 core values:
- Build for the patient: We do what we do so that patients get better healthcare.
- Own it and ship it: Own everything you do, and make sure you're always shipping.
- Be bold together: Be part of a high performance team where we take big bets and have each others' backs.
If you want to be a part of making healthcare enterprises around the world AI native, apply and tell us what makes you the ideal fit. This position is based in our San Francisco office (4 days/week in-person), and we are happy to assist with relocation if needed.
Prep for this interview
3 questions likely to come up at Bunkerhill Health, each matched to a line in this posting.
- 1Discovery and scoping
They wrote: “Stakeholder meetings. Physicians, hospital IT, clinical and operational champions. Anyone with an idea worth putting into production.”
A customer says “we want AI in our claims process.” What do you ask in the first meeting?
How to answer
Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- Ask what data you can access, and who signs off on security
Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.
- 2LLMs, RAG and agents
They wrote: “Use case building. Translate loosely defined ideas into concrete agents inside Carebricks. Build evals to ensure agents are doing what they're supposed to.”
How do you know an LLM feature is good enough to ship?
How to answer
Why they ask: Evals are what separate a demo from production. Many roles list them by name.
- Write 50–200 real examples with expected outcomes, with customer experts
- Agree on a pass bar and the errors that are never acceptable
- Score automatically where possible; review a sample by hand
- Re-run on every prompt or model change, and watch live traffic after launch
Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.
- 3Ownership and working with customers
They wrote: “We're looking for great engineers who want real ownership. The loop from "a physician told me this is broken" to "the platform no longer works that way" should close in days, and you own the whole loop.”
Tell me about something you shipped that broke in production.
How to answer
Why they ask: Everyone has broken production. They want to hear you own it and change something afterwards.
- What broke and who it affected
- How you found out and what you did in the first hour
- The root cause, said plainly
- What you changed so it can't happen the same way again
Tip: Pick a real one with a cost. Spend most of the answer on what you changed.
Not the one? Get the next one by email
New roles land here every day. Pick what you want to hear about.
Want the job, not just the posting? Learn how FDEs work.
FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.
Free. One email a week. Unsubscribe in one click.
