Forward Deployed / Solutions Engineer, HealthLeap AI

• You’re a strong backend engineer
• You’ve designed and run real production systems and data pipelines, and you like making two systems that were never meant to talk to each other work together and stay working
• You’re also comfortable in front of a customer, on a call with a hospital’s IT team, working out what’s actually going on and then building the fix
• When a task comes up twice, you build the thing that does it for you. You own the problem, you don’t wait for the ticket
• Deep backend engineering, 5+ years. You’ve designed, built, and operated production services, data models, and APIs
• A big part of your work has been integration engineering: connecting systems that weren’t built to talk to each other (the kind of work companies like Plaid, Stripe, or Merge are built around)
• Customer-facing. You can hold your own on a call with a hospital’s IT or clinical team, scope what’s needed, and explain the tradeoffs
• You debug fast: drop into a system you’ve never seen and work out how it behaves from the code, the logs, and the data
• You build tools to kill your own busywork
• Strong SQL and a real feel for whether the data is right
• You move fast and own the outcome

Desirable

• We’re live at 18 hospitals today. The plan is 44 in the next three months, and another 100 in the six after that. Every one streams patient data to us in real time, and the risk scores clinicians act on are only as good as that data
• Scaling that, the pipelines, the infrastructure, the reliability, is the core problem you own
• Build and scale the data pipelines that pull patient data from each hospital and keep it flowing in real time
• Scale the infrastructure so 8x the hospitals doesn’t mean 8x the fires: monitoring, alerting, reliability
• Stand up new integrations with the record systems hospitals run on, and go deeper on the ones we already support
• Turn getting a hospital live into software, so the next one is faster than the last instead of a fresh project every time
• Build the internal tooling, and a portal hospitals log into to self-test their data, that keeps every integration easy to watch and quick to fix
• When a number looks wrong, work out why, from the hospital’s system through to what clinicians see, and fix it
• We build and run our own systems here. The stack is Python and TypeScript
• We protect deep rest, but a hospital go-live can mean a 60+ hour week

• Our interviews look like the real job. No leetcode, no puzzles. Use the tools you’d use on the job, AI included
• Intro call - Get to know each other
• Technical 1 - System design
• Technical 2 - Live coding
• Onsite - Meet the team in SF
• We decide the same week as the onsite. If it’s a fit, you’ll know fast