Founding Member of Technical Staff
Job description
Founding Member of Technical Staff at Nabi Health.
About the role
This role focuses on building an AI-native health system for eating disorder care and integrating it to serve a large patient population.
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
Product integrations connect the Command Center EHR with the Callie intersession product so clinicians can coordinate continuous care with agents.
Patient onboarding tools streamline intake and setup, and the team builds and maintains these tools.
Infrastructure deployment, monitoring, and observability scale as the system grows, and the team maintains this infrastructure.
Requirements
The posting states a minimum of 10 years of experience.
Based in or willing to relocate to San Francisco for an in-person role.
Product instincts evaluate end-to-end decisions from data model to user experience, and ship reliable, performant, great-to-use systems.
Scrappy and fast-moving behavior delivers results quickly while maintaining quality, and build comfortably in ambiguity with little instruction.
Fast learning ramps up quickly on new tools, systems, and domains, and stay aware of latest technology and developments.
Deep empathy and mission alignment care about real people, especially patients and clinicians.
Clear communication distills complex problems and conveys them concisely as a team player.
Nice to have
Experience with Node.js, Elixir, and the TypeScript/React ecosystem.
Familiarity with AI/ML integration patterns, building agent architectures, or prompt engineering.
Experience in healthcare, fintech, or other regulated or high-stakes domains.
Skills & tools
Node.js, Elixir, TypeScript, React, AI/ML integration patterns, agent architectures, prompt engineering.
Practical notes
This is an in-person role based in San Francisco.
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
Roles of this type typically combine deep technical ownership with cross-functional collaboration.
Health tech platforms often integrate clinical workflows with software and AI components.
Agentic systems rely on reliable backend services, observability, and careful data pipeline design.
Teams in regulated domains prioritize reliability, security, and clear communication.
Founding environments expect fast learning, scrappy execution, and strong product instincts.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
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.