
Founding Forward Deployed Engineer
Posted 18 days ago
The role in short
Embed with clinical customers to build and deploy production software integrations and AI features, often for systems without APIs.
About Optexity
Optexity is a product-driven research lab building clinical reasoning and computer use models on data no other lab can reach. We deploy directly inside clinics and hospitals — including systems with no APIs, using integration infrastructure we've built and open-sourced — and in return become their preferred partner. That gives us proprietary clinical reasoning trajectories from practicing physicians, and a feedback loop between real patient encounters, our models, and the products built on top of them.
We're a small, fast-moving founding team with multiple published papers in NeurIPS, ICML, CVPR etc and background from Apple, Amazon, Microsoft, CMU, IIT.
We are backed by world-class investors and leaders like Jeff Dean, Neotribe VC, PearVC, Together Fund and Zapier Fund.
How we work
- Customer obsession — we start with the customer and work backwards
- Intellectual honesty — ideas matter more than titles; we communicate directly and assume good intent, even in disagreement
- Bias for action — we build and learn with customers rather than debate in the abstract
- Extreme ownership — we own outcomes, not just tasks, and see problems through
About the role
You are a software engineer who works directly with our customers. You will be deployed inside practices, clinics and hospitals in New York, understand how doctors and staff actually work, and build the integrations and product features that make Optexity work in their environment. Many of these systems have no APIs, so you will often be building the way in. You will own the customer’s technical outcome from first meeting to daily usage.
What you’ll do
- Deploy and set up Optexity inside practices and clinics, including systems with no APIs, using the integration infrastructure we’ve built and open-sourced
- Sit with doctors and staff to understand their workflows and requirements, and turn them into working software
- Build and improve data pipelines and integrations with EMRs and other clinical systems
- Work with the core team on our search and chat system, and bring real customer feedback into the product
- Debug and resolve customer issues quickly, and own them until they are fixed
- Help drive customer success: onboarding, training, and increasing usage
- Make general solutions from one-off customer problems, so each deployment makes the next one faster
- Share what you learn with the founders to shape product direction
Ideal candidate
- Bachelor’s in computer science or a related field
- Strong in Python and comfortable with backend work, data and APIs
- Comfortable working directly with customers, including non-technical ones
- Energized by open-ended problems and takes ownership without needing to be guided
- Genuinely wants a startup over big tech, with speed and ambiguity as defaults, not exceptions
- New Grads Welcome to apply
Nice to have
- Prior founder, founding engineer or solutions engineering experience
- Experience with browser or desktop automation, or reverse engineering systems with no APIs
- Built LLM-powered products before
- Familiarity with healthcare data, EMRs, or HIPAA
- Strong product taste
- Ambitions to start your own company someday, and we’ll support that path
- Preferred to be based in SF but remote also considered.
What you get
- Direct, daily work with the founders, plus exposure to board and investor conversations
- Real ownership of technical direction, with scope that grows as the company does
- Full compute and data to do the work properly
- Competitive salary and meaningful equity
Prep for this interview
4 questions likely to come up at Optexity, each matched to a line in this posting.
- 1Integrations and APIs
They wrote: “Deploy and set up Optexity inside practices and clinics, including systems with no APIs, using the integration infrastructure we’ve built and open-sourced”
Walk me through connecting our product to a customer's internal system that has no documentation.
How to answer
Why they ask: This happens weekly in the job. They want a calm, step-by-step method.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- Agree on how failures get reported, and who fixes what
Tip: Talk about finding the owner of the system first. The code is the easy part.
- 2Data and SQL
They wrote: “Build and improve data pipelines and integrations with EMRs and other clinical systems”
How would you design a daily pipeline that feeds customer data into our product?
How to answer
Why they ask: Tests basic data engineering: scheduling, failures, re-runs and monitoring.
- Extract with timestamps or change tracking, not full dumps, when possible
- Transform in steps you can re-run without creating duplicates
- Validate row counts and key fields before loading
- Alert a person on failure, with enough detail to fix it
Tip: Make re-running safe (same input, same result) and say how you'd know it failed.
- 3Coding
They wrote: “Strong in Python and comfortable with backend work, data and APIs”
Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.
How to answer
Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.
- Read with a proper CSV parser; check the header first
- Validate each row and collect errors, not crash on the first one
- Send in batches with retries and a clear report at the end
- Write one or two quick tests for the parsing
Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.
- 4Ownership and working with customers
They wrote: “Extreme ownership — we own outcomes, not just tasks, and see problems through”
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.