Software Engineer, Nuna Incorporated

• Bachelor’s degree in computer science or similar field
• Strong engineering skills with the ability to own a feature or system end to end — backend services, APIs, and the code that ties them together
• Experience operating what you build: testing, deployment, and observability
• Comfort with ambiguity within your domain — able to move from a rough problem to a shipped solution
• Clear communication and the ability to work well across product, design, and engineering
• A genuine interest in improving healthcare alongside an interdisciplinary team
• Able to work from our San Francisco office a minimum of 2 days per week

Desirable

• Our products are only as good as the care and science behind them. We are a small team of engineers, designers, product managers, and clinicians who work together to build for both patients and providers
• You will be expected to own real pieces of the product from day one and be responsible for building, shipping, and supporting them in production
• As a software engineer, you own meaningful parts of the product end to end: you design them, build them, ship them, and keep them running
• You'll work in the systems at the heart of the coach — the AI and agent logic, the services behind it, the data it depends on — and you'll make the day-to-day architecture and trade-off calls within your domain
• You'll do this with a high degree of autonomy, and you'll help raise the bar for the engineers around you. Comfort with ambiguity matters here: the work rarely arrives fully specified
• Own meaningful features and services end to end — design, build, ship, and operate them in production
• Contribute to architecture decisions in the systems you work in, including the AI/agent and product systems at the core of the coach
• Write high-quality, well-tested, observable code, and help others do the same through reviews and pairing
• Treat privacy, security, and the responsible handling of health data as part of doing the job well
• Break ambiguous product problems into shippable work, making pragmatic trade-offs to deliver
• Partner with product, design, and the Data org to turn requirements into working software