Forward Deployed Engineer

About the role

The role connects clinical ideas to production on Carebricks, closing the loop from stakeholder feedback to platform change. The FDE runs stakeholder interviews, scopes and builds use cases, validates agent behavior, and iterates on live deployments.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Stakeholder conversations surface requirements and constraints that shape production workflows. Use case scoping defines measurable success criteria and a clear path to production for ideas. Use case building converts loosely defined concepts into concrete Carebricks agents and evals that verify behavior. Use case alignment keeps agents delivering value as clinical guidelines and operational needs evolve. Core engineering changes the platform based on user feedback and hands-on experience with Carebricks.

Requirements

A degree is required for this role. Healthcare system integrations expose malformed FHIR payloads and legacy interface constraints that must be handled. You own the full feedback cycle, closing the loop from clinical insight to platform change in days. The role requires fluent communication with clinical champions and the ability to debug production pipelines on demand. Customer outcomes drive priorities, and the work demands comfort with messy clinical realities and frontier AI problems.

Practical notes

The position is based in the San Francisco office for four days per week, with hybrid flexibility and relocation support available. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Work in this role centers on healthcare AI deployment, where clinical safety and operational robustness are essential. The team works with FHIR standards and legacy healthcare infrastructure alongside modern AI agents. Clear communication and ownership are central to succeeding in this position.

Questions to ask

Good questions to ask the employer in the interview: what does success look like in the first six months, how is the team structured, what is the current biggest challenge, and how are decisions made. Asking about growth paths and the review process is also well received. Employers expect questions, and good ones show preparation.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.

About the company

Bunkerhill helps health systems use generative AI to understand each patient's full clinical context and take the right next steps - automatically and at scale.