Principal Software Engineer
Blooming Health
United States · Posted October 21, 2026
Just laid off? Start here: a plan for the first weeks
See every open role at Blooming Health
More in All Principal Software Engineer jobs (382) · Healthcare & Hospital Systems · Engineering jobs
Similar jobs
- Senior Software Architect, Security Platform · Keeper Security
- Corporate Vice President - Site Reliability Senior Engineer · New York Life
- Devops Engineer/Full Stack Engineer (GS-13) · U.S. Tax Court
- Software Development Engineer III, MuleSoft · Veeam
- Software Engineer - Customer Facing Applied AI · Addepar
- Sr Software Development Engineer-(Salesforce) · UKG
Engineering jobs in the rankings
Rankings about engineering jobs
- Best cities for software and engineering jobs #1 San Francisco (3,412 openings)
- Best cities for engineering pay after cost of living #1 San Mateo ($216k)
- Most requested AI skills in engineering jobs #1 AI tools in daily work (6.1%)
- AI tools named most often in engineering jobs #1 Claude (1.7%)
- Employers with the most engineering jobs #1 Amazon (2,992 roles)
Pay compared with the market
This listing does not state pay. Across 101 open principal software engineer listings that state pay, the middle half runs $216,000 to $320,000 and the median is $275,000.
Listed pay is what employers advertise, not what people are paid.
Principal Software Engineer salaries by state · Check your own pay
How AI is used in this kind of work
Among software developers, AI is already used for some of the tasks. Measured exposure for software developers: 29% (some).
Share of this job’s tasks that AI is already used for at work, from real usage. It is not a forecast of job loss, and a low number means no use seen yet. Source: Anthropic Economic Index.
Skills this job asks for
Say which you have and which you want to build. We use it to match you to jobs like this one.
About the job
About Blooming Health
Blooming Health is on a mission to transform social care. Our AI-powered platform identifies social needs and barriers by continuously collecting real-time data from member interactions and screenings. It then drives action through empathetic, automated outreach in 55+ languages and dialects, engaging people by voice, SMS, and email and coordinating referrals to the right services at the right time.
The result: improved access to care, higher program participation, and better outcomes across diverse populations. Our platform supports more than 1,000 community organizations across the US, helping millions of members access the support they need to stay healthy. We don’t just offer software—we deliver impact.
About the Role
We’re looking for a deeply technical, ownership-minded Principal Software Engineer to join our Platform team and report directly to the VP of Engineering, Platform. This is a fully remote, US-based role , with a preference for candidates working in EST or CST.
This hands-on role sits at the center of our platform’s next chapter. You’ll own our technical debt roadmap and drive platform modernization alongside our product roadmap. As technical lead for a dedicated platform team, you’ll do much of this work through an agentic software development lifecycle: using and shaping AI coding agents, a multi-agent orchestration harness, and our internal code-intelligence platform.
Our platform consists of Python and Go microservices on Google Cloud, including a real-time agentic voice platform. It handles protected health information for millions of members, so reliability, security, and compliance are essential.
This role is suited to someone who wants startup pace and meaningful ownership, with room to grow into a Principal Software Engineer or Software Architect role.
What You’ll Do
Technical Debt & Platform Modernization: Own the platform technical debt roadmap end to end, from prioritization and sequencing through design, delivery, and measurable outcomes. Lead the convergence of multiple platform generations into a cohesive, well-architected platform using incremental, low-risk migration patterns such as the strangler fig pattern.
Agentic SDLC & Context Engineering: Build and operate an AI-native engineering workflow. Use and evolve our multi-agent orchestration harness and code-intelligence platform to plan, implement, test, and review changes across many services in parallel. Design the context agents depend on, including platform architecture context, skills, runbooks, architecture decision records, and fix or implementation ledgers. Set the guardrails and human review points that make agent output accurate, auditable, and production-ready in a regulated environment.
Architecture & Distributed Systems: Drive architectural decisions across our GCP platform, including Cloud Run services, jobs and worker pools, Pub/Sub event flows, Cloud SQL (Postgres), Redis, BigQuery, and our API gateway. Design for scale, resilience, and cost efficiency across bursty, campaign-driven, and real-time voice workloads. Write clear technical designs and ADRs, and review those of others.
Reliability & Operational Excellence: Define and improve SLOs, observability, and alerting across member-facing workflows. Harden the platform against single points of failure and strengthen infrastructure as code (Terraform), CI/CD, migration safety, and rollback practices.
Security & Compliance by Design: Build security and privacy into every layer, including least-privilege access, network hardening, secrets management, encryption, audit logging, and PHI handling. Partner with security and compliance stakeholders so engineering work supports our HIPAA, SOC 2, and HITRUST commitments.
Engineering Excellence & Technical Leadership: Set the bar for code quality, testing, API design, and documentation. Serve as technical lead for the platform team, mentor engineers, raise the team’s technical judgment, and spread agentic engineering practices across the organization. Lead through influence, clarity, and example.
What Success Looks Like
First 30 days: You understand our platform end to end, have taken ownership of the technical debt roadmap, and have shipped your first meaningful fixes through the agentic workflow.
First 60 days: You’re running several debt and upgrade workstreams in parallel with agents and the platform team. Your ADRs and designs are a reference point for technical decisions.
First 90 days: You’ve delivered measurable improvements in security, reliability, and scalability. The context, skills, and guardrails you’ve built have made our agentic SDLC more reliable and repeatable.
What We’re Looking For
Requirements
Seniority & Scope: 10+ years of software engineering experience, including several years at Staff level or equivalent, leading architecture and technical direction across multiple teams or services.
Distributed Systems Depth: Proven experience designing, building, and operating scalable, reliable distributed systems and microservices in production. Strong instincts around consistency, idempotency, event-driven design, failure modes, back-pressure, and capacity planning.
Cloud Architecture (GCP): Hands-on production experience with Google Cloud, ideally Cloud Run, Pub/Sub, Cloud SQL, IAM, VPC networking, and BigQuery. Deep AWS or Azure experience is welcome if you can show a fast ramp onto GCP.
Python Expertise: Strong, production-grade Python skills, including async services and APIs (for example, FastAPI), testing, and performance tuning. Willingness to work across our Go services.
Agentic SDLC & Context Engineering: Real experience delivering production software with AI coding agents, such as Claude Code or similar tools. You understand context engineering and multi-agent orchestration, and how to make agent output reliable, reviewable, and safe. You have clear opinions on where agents excel and where humans need to stay in the loop.
Healthcare Domain Experience: Experience building software in healthcare or another regulated environment that handles PHI or PII, with a working understanding of HIPAA and how compliance requirements shape architecture.
Engineering Excellence: A track record of raising standards through design reviews, testing strategy, CI/CD, observability, infrastructure as code, and clear documentation.
Ownership & Startup Mindset: Comfort with ambiguity, a bias toward action, and a record of owning outcomes end to end, from design through production. You thrive in a fast-moving, resource-conscious startup.
Communication & Influence: You write clear technical designs, explain trade-offs well, and lead and mentor engineers without formal authority.
Preferred Qualifications
Go: Production experience with Go microservices. Strongly preferred.
Healthcare Interoperability: Experience with EHR integrations (Epic/Cerner, FHIR/HL7) and the payer/provider ecosystem.
Compliance Frameworks: Hands-on contribution to SOC 2, HITRUST, or NIST-aligned control implementation.
Platform Migrations: Experience leading large-scale re-architectures or platform migrations while keeping customers liv