Sakura Health - Founding Engineer
Requirements
• Comfort building across the stack, from data models and backend services to the interfaces staff use and integrations with external systems. • Practical judgment about security, including the additional risks of software that can take actions on a user’s behalf. • Sound product and engineering judgment. You choose simple approaches, adapt as requirements change, and know which safeguards must be in place before shipping. • Sound product and engineering judgment. • Clear communication and a collaborative approach. You document decisions, ask for feedback, and help teammates understand unfamiliar parts of the system. • Clear communication and a collaborative approach. • Willingness to spend regular time onsite at partner clinics and hospitals to understand workflows and support deployments. • Healthcare experience is helpful, not required. Experience with production LLM systems, agent evaluations, browser automation, or sensitive data is a plus. We value evidence of what you have built and operated, including work at an early startup or on your own. • Healthcare experience is helpful, not required. • What success looks like • First 30 days: Learn a practice workflow and the codebase, trace how data moves through the system, and ship a focused improvement with the founders. • First 30 days: • By 90 days: Own a workflow from design through deployment, with evaluations, monitoring, and a measurable improvement in reliability or staff effort.
Responsibilities
• Build and evaluate agents. Develop voice and workflow agents, browser automation, and EHR integrations. Build evaluations around real workflow cases, investigate failures, and improve task completion, latency, and cost. Design clear recovery paths and human review for uncertain actions. • Build and evaluate agents. • Own reliable delivery. Build Python services and APIs, deployment pipelines, and infrastructure as code. Use Docker with Kubernetes or ECS, with monitoring and alerting to diagnose failures and support growing usage. • Own reliable delivery. • Protect sensitive data. Implement encryption, access controls, and audit trails for protected health information and agent actions. Make security decisions explicit and support healthcare compliance requirements. • Protect sensitive data. • Shape the product. Spend time with clinic teams, identify where work stalls, and help the founders prioritize what to build. Ship focused improvements, observe how staff use them, and refine the product based on what works. • Shape the product. • Set the engineering standard. Shape service boundaries, data models, code review, testing, and observability. Leave clear documentation so the next engineer can understand and extend what you build. • Set the engineering standard. • You enjoy turning an unclear customer problem into working software. You can scope a useful first version, explain your tradeoffs, and follow through when something breaks after launch. • 2+ years of professional software engineering experience, including taking a system from an initial idea into production and supporting it as usage grows. • Strong Python backend skills across APIs, data processing, and service reliability. You can investigate a failure and follow it through to a durable fix. • Within 6 to 9 months: Take responsibility for a core part of the product, make it easier to operate and extend, and help new engineers become productive as the team grows. • Within 6 to 9 months: • We will agree on priorities as we learn from deployments. Success means more workflows completed correctly, less manual intervention, and systems the team can confidently operate and extend.
Benefits
• Competitive base salary, with potential equity participation. Compensation, benefits, and any equity component will be discussed during the hiring process, based on your experience and the scope of the role.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT