{{Company name}} is hiring a Principal Software Engineer — the most senior individual-contributor role in our engineering organization. Your impact radius is the whole company, not one team: you will own the technical problems nobody else can frame, set architecture direction that dozens of engineers build on for years, and be the person leadership calls when the stakes are highest.

What you'll do

• Own the organization's hardest technical problems — the ones that arrive as a symptom, not a spec, and span multiple teams and quarters.
• Set and communicate long-term architecture direction, and make the irreversible decisions deliberately.
• Lead technical strategy with executives: translate business goals into engineering bets and honest cost estimates.
• Unblock teams by descending into the details — prototyping the risky part, reviewing the critical design, or debugging the incident nobody can crack.
• Multiply senior and staff engineers through mentorship, design review, and deliberate delegation of problems that will grow them.
• Define engineering-wide standards where consistency compounds, and kill process where it does not.
• Represent engineering with customers, partners, or the board when the conversation is deeply technical.

What we're looking for

• {{Years of experience}} years of software engineering, with sustained impact at staff level or above across multiple teams.
• A track record of architecture decisions that aged well at scale — and the scars from at least one that did not.
• Deep expertise in {{Core domain}}, with the breadth to be credible across the whole stack.
• Demonstrated ability to lead through influence: no direct reports, yet whole organizations moved because of you.
• Exceptional written communication — your design documents end debates instead of starting them.
• Judgment under ambiguity: you decide with incomplete information and correct course in the open.
• A history of growing senior engineers into staff-level and beyond.

Nice to have

• Experience guiding an organization through a major re-architecture or scaling inflection.
• Public technical work: talks, writing, standards involvement, or open-source leadership.
• Experience in {{Industry}} or with comparable regulatory and scale constraints.
• Prior experience partnering directly with executive teams on technical due diligence.

Compensation and benefits

• {{Salary range}}
• {{Benefits summary}}
• {{Location / remote policy}}

How to apply

{{Application instructions}} Tell us about a decision only you could have made at the time — what the organization looked like before and after, and how long the effect lasted.