Principal Software Engineer

At OnMed our purpose is simple but powerful...to improve the quality of life and sense of well-being in our communities by bringing access to healthcare to everyone, everywhere. Our path to everywhere has already begun, with our innovative Care Station, a small but mighty, Clinic-in-a-Box, bringing #healthcare access anywhere with an outlet to plug it in. Poised to become a key component in America's public health infrastructure, the OnMed Care Station is the only tech-enabled, AI-powered, human-delivered, hybrid care solution that combines the comprehensive experience, trust, and outcomes of a clinic with the rapid scalability of virtual care.

At OnMed, every role, every day is directly impacting the communities we serve. You'll join a high-performing purpose-driven team, innovating to break down the barriers that keep people from the care they need.

This is not just a job... it's a movement to bring access to healthcare where and when people need it most. It's healthcare that shows up.

You think in systems, not tickets. You have shipped and operated user-facing software end to end - browser to API to database to deployment - and carry the scars, and the judgment, that come with it. You can go deep on interface performance, API and data design, and distributed systems, and just as easily step back to explain a tradeoff to a product or clinical stakeholder.

You are as comfortable profiling a slow query or untangling a rendering bottleneck as you are shaping the architecture the next two years of the product will sit on. You have made AI-aided development a real multiplier in your own work as a discipline paired with rigorous design and review. You raise the technical bar for everyone around you, leading by example, and you're energized by the idea of building software that keeps a healthcare device working when someone needs it most.

OnMed is looking for a Principal Software Engineer to serve as the senior-most individual technical contributor across our software stack - the web and device-facing front ends, the services and APIs behind them, the data stores they depend on, and the cloud infrastructure it all runs on. You'll own the architecture that lets features move reliably from idea into production across the Care Station fleet - front-end applications, service and API design, data modeling, deployment automation, observability, and the platform patterns other engineers build on.

This is a hands-on role: you'll write code, review designs, and be the person the team turns to on the hardest technical problems, while mentoring engineers and shaping technical direction without formal management responsibility.

This role reports to the Head of Engineering & AI.

• A clear, scalable architecture that carries product features from prototype to reliable production use across the full stack
• Consistent engineering standards across the full stack as the team and technical surface area grow
• Technical depth on the hardest engineering problems - latency, reliability, data integrity, security, cost - without waiting on outside consultants
• AI-aided development practiced with rigor, so the team ships faster without quietly accumulating design, quality, or security debt

• Serve as the senior-most technical voice on full-stack engineering decisions, partnering closely with the Head of Engineering & AI on strategy and roadmap
• Set the standard for AI-aided and agentic development - establishing the patterns, guardrails, and review practices that let the team move faster without compromising sound design - and drive effective usage habits across the team
• Lead design reviews and architectural decisions for cross-team initiatives, balancing speed, maintainability, and long-term scalability
• Identify technical risk early - in scalability, security, data integrity, or performance - and drive it to resolution

• Design and own the architecture for OnMed's patient-and clinician-facing applications and the services, APIs, and data models behind them
• Set the standards for API and service design - clear boundaries, versioning and backward compatibility, contract documentation, and consistent authentication and authorization patterns as the number of consumers grows
• Drive front-end architecture and performance - component structure, state management, accessibility, and real interaction latency on the…