Principal Platform Engineer
Job check
39/100
Medium ghost risk
- Online 49 days, 1.1× the typical 45 days+4
- Re-posted+10
- Posting date refreshed after it first appeared+15
- Re-posted while already open longer than usual+10
- Live on the employer's careers page
About this role
Principal Platform Engineer
Software Platforms
General Overview
AI is collapsing the cost of building software, and Ralliant intends to lead, not follow. We're building a shared platform that reinvents how our operating companies create and ship software, starting with an AI-first approach to developer productivity. From there, the platform grows into shared services that let operating companies bring new software offerings to market and commercialize them more quickly. Operating companies own their products, customers, and roadmaps, while the platform provides the common foundation they build on rather than rebuild.
The title centers on platform engineering, but the work spans four competencies: cloud engineering, DevOps, site reliability engineering, and software engineering . Strong candidates are deep in at least one and capable across all four, and they stay hands-on in the code while helping steward the architecture and standards the platform depends on.
The Principal Platform Engineer is a senior individual contributor who builds and operates the platform's core services while helping steward its architecture and standards. Principals take major capabilities from design through production and ongoing operation, shape the golden paths operating companies adopt, and set the technical bar through engineering, code review, and mentorship. The role reports to the Chief Software Platform Officer and partners closely with the Director of Technical Product Management and engineering teams across the operating companies.
Responsibilities
• Build platform capability hands-on: design and ship core platform services end to end, from architecture through production and ongoing operation, as self-service capabilities that operating-company engineers adopt with minimal friction. • Steward the platform's architecture and standards, shaping the reference architecture, golden paths, and paved roads, and turning engineering standards into executable guidance through the Architecture Council. • Advance AI-first software delivery by building and evolving the templates, pipelines, and golden paths that raise developer throughput, and help extend the platform into shared services that support new software offerings. • Own reliability, security, and cost for the services you build: define SLIs and SLOs, instrument observability, run incident response, and reduce toil through automation, with security and cost designed in from the start. • Set the technical bar and mentor: raise the level of platform and operating-company engineers through hands-on engineering, code review, and mentorship, and help build a connected engineering community across the portfolio.