The role
We are interested in principal engineers who can shape the technical direction of a complex system or portfolio of systems. You would connect business priorities to architectural consequences, identify risks that individual teams cannot resolve alone and guide decisions that will endure across delivery cycles. This scope differs from Staff Engineer through its wider system horizon and influence on long-term strategy, while still requiring technical credibility and selective hands-on work. This role-specific posting supports ongoing recruitment; assignment details would be discussed if an opportunity arises.
What you would work on
- Develop an evidence-based technical direction for cross-system concerns such as integration boundaries, data ownership, security and resilience.
- Lead high-impact architecture decisions, compare options and sequence changes so teams can make progress without a risky single-step rewrite.
- Partner with senior product, delivery and engineering leaders to connect technical investment to measurable service or business outcomes.
- Resolve disagreements that span teams by making assumptions and trade-offs visible, then enable local owners to execute the agreed approach.
- Sponsor engineering learning through design reviews, incident analysis and mentorship of senior and staff engineers.
Essential experience
- A record of shaping and delivering architecture across multiple teams, major systems or a sustained modernization effort.
- Ability to reason from production evidence about reliability, security, data and cost, and turn strategy into an achievable sequence.
- Influence with technical and non-technical leaders, including clear communication when constraints make an attractive option impractical.
Useful additional experience
- Setting technical strategy across cloud, data and application boundaries in a regulated or high-availability environment.
- Creating decision mechanisms and engineering communities that continue to work when you are not in every review.
What to include in your application
Send your résumé and describe an architectural decision with consequences across teams or years. Explain the alternatives, the evidence you used, how you earned agreement and what the outcome taught you. Include how you kept the long-term direction useful as near-term priorities changed. A sanitized decision record is optional. Please select the Principal Engineer posting so your résumé is linked to this distinct role.