Time since we first saw it
Day 101
Up longer than most. Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
SF · San Francisco, California, United States
Open 3 months, first seen by us 101 days agoLocation type: On-siteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: EngineeringFrom the employer’s posting
Open 3 monthsWe first saw this posting 101 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 101
Up longer than most. Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
1 open job
Add your resume to compare the role’s scope, tools and requirements with your experience.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
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.
New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Forward Deployed Engineer, by the work the posting describes.
Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.
Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.
An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.