Principal Software Engineer-Platforms
Arcadia · Remote
MeritLog read this listing from Arcadia's Lever job board and last checked it on September 10, 2026.
Source: the employer's Lever job board. Open the original listing for current details.
Job details
- Work model
- Remote
- Salary
- $250,000 - $350,000
- Location
- Remote (USA)
- Occupation
- Software Developers(O*NET 15-1252.00)
Hiring context
How this role compares at Arcadia
Arcadia has 18 live roles in MeritLog’s catalog across 6 job families, and 3 of them are in engineering. 17 of those listings publish a pay range, a disclosure rate of 94%.
This role's posted range of $250,000 - $350,000 sits above 100% of the 15 other Arcadia roles quoted over the same currency and period.
Arcadia concentrates this hiring in:
Counted across the job boards MeritLog tracks, at the time this page was served. Pay comparisons use only listings that publish a complete range in the same currency and period.
Job description
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 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 In 6 months