Principal Software Engineer
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 platform surface, key dependencies, and the customer outcomes the team owns
- You have identified the two or three most leveraged technical 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
- 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 actively coached on how to apply them
- You own the technical health, scalability, and customer-facing outcomes of a significant platform domain
- You are recognized cross-team for technical judgment, calibration, and the quality of the engineers whose trajectory you've shaped
- You have defined 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
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 platform surface, key dependencies, and the customer outcomes the team owns
- You have identified the two or three most leveraged technical 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
- 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 actively coached on how to apply them
- You own the technical health, scalability, and customer-facing outcomes of a significant platform domain
- You are recognized cross-team for technical judgment, calibration, and the quality of the engineers whose trajectory you've shaped
- You have defined 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
Tech You'll Work With
Arcadia's platform processes petabyte-scale healthcare data through a lakehouse architecture built on open table formats. Apache Spark drives distributed compute; dbt drives transformations; Kafka moves streams; Cassandra/Scylla handles high-throughput storage; OpenSearch / Elasticsearch powers search and indexing — all orchestrated on Kubernetes in AWS, with services spanning TypeScript/Node, Python, Go, and Java/Kotlin (polyglot, by design).
We're actively expanding this entire platform-stack to be AI-native — enabling the creation of custom agents built on Arcadia's data foundation to solve some of healthcare's biggest challenges. Principal Engineers shape the patterns here. Depth in distributed compute, data infrastructure, or platform engineering translates directly.
What You'll GetRequires ownership of cross-team platform initiatives, deep distributed systems and data infrastructure expertise, AI-assisted development experience, mentoring ability, customer orientation, and strong written communication.
Key Responsibilities
- owning initiatives
- mentoring engineers
- defining architecture
Skills & Tools
Apache Spark, dbt, Kafka, Cassandra, Scylla, OpenSearch, Elasticsearch, Kubernetes, AWS, TypeScript, Node, Python, Go, Java, Kotlin
Job Details
- Category: Software Development
- Seniority: Senior Level
- Commitment: Full Time
- Workplace: Remote — United States
- Salary: USD 250,000 – 350,000 / year
- Languages: English
Benefits
- Generous paid time off
About Arcadia
A healthcare technology company that transforms complex data into actionable insights for better care and lower costs. — Industry: Healthcare