Principal Software Engineer - Platform

Arcadia is a healthcare technology company that uses data to help organizations deliver better care, boost revenue, and lower costs. The Principal Software Engineer will own and evolve the developer platform across a petabyte-scale lakehouse and Kubernetes applications, building self-service capabilities, improving reliability and delivery, managing migrations and stakeholders, and setting technical direction.

Responsibilities:

• Push quality attributes into the platform, especially as AI increases the volume of changes: test and regression gates, progressive delivery and fast rollback, supply-chain and policy checks in the pipeline, and cost that's visible and attributable to the teams
• Run the platform as a curated internal product: find what slows teams down, pick the few capabilities worth building, publish the roadmap, and measure adoption, delivery speed, stability, and developer satisfaction
• Build software: self-service APIs, templates, and golden paths for CI/CD, environments, and observability, so teams get what they need without waiting on anyone. You write a meaningful share of the code
• Carry the cost of migrations: track usage, automate instead of handing out checklists, push through the final 20%, and sunset
• Manage the platform's stakeholders: say yes with compromises, say no without breaking trust, bring shadow platforms back onto the paved road, and make cost visible to the teams that generate it
• Set the technical direction and evolve the platform, and coach Senior Engineers through design partnership and review

Requirements:

• Both halves of platform engineering: a software engineer's instinct for clean abstractions and APIs, and a systems engineer's depth in cloud, Kubernetes, networking, and IaC
• Reliability you've owned: SLOs, observability, on-call, and incident response
• Customer empathy: you talk to the engineers you serve, tell a real need from a loud request, and retire what nobody uses
• Big, long-running projects you've seen through: migrations pushed past the final 20%, platforms sunset on purpose, and the attention to detail both require
• A clear philosophy on structuring infrastructure and delivery for security, velocity, and reliability, and the stories behind it
• Current, hands-on production coding, the habit of figuring things out (research, spike, deliver), and relentless pragmatism about what's worth building
• Drive to reduce toil for everyone through software
• Ability to initiate and get stuff done org-wide
• Regulated-data experience (HIPAA, PHI, SOC 2 or HITRUST environments)
• A public voice through talks, writing, or open source
• Experience turning an infrastructure or DevOps team into a product-minded platform team
• Experience building platform support that scales: support tiers, office hours, docs, and developer advocacy
• Experience making cloud and CI cost visible and actionable for the teams that generate it