Principal Software Engineer-Platforms

Arcadia is dedicated to happier, healthier days for all. We believe that there is a better healthcare world – one powered by data. Our platform transforms complex, diverse data into a unified foundation for health, helping organizations deliver better care, boost revenue, and lower costs. We’re a team of fiercely driven individuals committed to making healthcare more sustainable—and we’re looking for passionate people to help us get there. For more information, visit arcadia.io. Why This Role Is Important to Arcadia Arcadia's platform is the backbone of how partners and customers act on healthcare data at national scale. Principal Engineers are the technical owners of the cross-team initiatives and platform-level outcomes that define what Arcadia's engineering organization is capable of — the engineers others look to when the right answer is structural, not incremental. A Principal Engineer at Arcadia owns the complete vertical slice: requirements through customer validation, design through long-term operation. They raise the floor for the engineers around them through direct coaching, reusable patterns, and the tooling they leave behind. They define how the team adopts AI as a leverage multiplier — not just for their own productivity, but as a standard the team and the org can adopt. What Success Looks Like In 3 months You have deep familiarity with your domain's platf [... source excerpt omitted ...] chnical investments in your area and aligned with Product, Engineering Management, and key partners on a plan You have established working relationships with the Senior Engineers you'll coach and the cross-team peers you'll collaborate with most often In 6 months You are driving a multi-team or platform-level initiative end-to-end — requirements and architecture through implementation, rollout, and observability You are visibly raising the floor on Senior Engineer execution through design reviews, code review, pairing, and direct coaching You have shipped AI-native tooling, workflows, or patterns that other teams in the org have adopted, with at least one peer team activel [... source excerpt omitted ...] efined and operate a measurable bar for how engineers across multiple teams adopt agentic AI-assisted engineering — what good looks like, what to avoid, and how to spread it What You'll Be Doing Owning complete vertical slices of cross-team or platform-level work — including the multi-quarter migrations, deprecations, and architectural pivots that single-team scope can't carry Setting the technical bar for what "right" looks like in your domain — sharpening designs, catching architectural drift (including in AI-generated work), and shaping the patterns the team builds toward Proactively identifying and evaluating platform-level opportunities — new architectures, tools, or c