Why this role:

Most engineering roles hand you a slice. A product owner sets the “what,” a manager sets the “how,” and you build your piece inside someone else’s sprint. This is not that role.

We don’t build the product our customers log into — we build the factory that builds it, and the systems that detect the moment anything starts to break. When our tooling works, the entire organization finds and fixes customer problems faster. When it doesn’t, everyone feels it. That is the leverage of this role, and it is why the work sits at the center of how we run reliability.

You’ll be handed real business problems — often ambiguous, sometimes dropped on us overnight — and trusted to solve them end to end: shadow the people living the problem, prototype, write the architecture, socialize it with senior and executive leaders, then build it and operationalize it so the team can run it. You’ll work full-stack, fly independently, and own what you ship. You’ll build things that matter and get used across the entire company.

If optimizing a single bolt to a tenth of a millimeter for the next four months sounds like a good year, this isn’t your role. If you’d rather build the thing that goes to Mars, keep reading.

What you’ll do:

• Translate business into solutions —turn ambiguous business needs into architected, detectable, automatable systems — from whiteboard to prototype to production.

• Extend our agentic AI platform —develop and grow our proprietary, cloud-hosted platform — including locally-hosted models — that powers observability and automated issue detection across the organization.

• Architect at enterprise scale —design 24/7, cross-region-resilient, business-critical tooling used by teams across the company.

• Work across the organization —partner with other principal engineers, support, security, and platform teams to map how systems integrate (CRM / case data, endpoint and security telemetry, cloud infrastructure) and design for the real environment.

• Modernize high-risk pathways —re-architect legacy access and operations pathways into secure, controlled, self-service tooling with the right guardrails built in.

• Multiply the team —mentor and up-level a growing bench of junior and mid-level engineers: decompose big problems, hand off well-scoped pieces, and hold the quality bar so what ships is simple, correct, and aimed at the business need.

• Own it end to end —including light, event-driven on-call for what you build. This is not a rotation — you’re reachable when something you own breaks, which is rare (typically a handful of times a year).

What sets a Principal apart here:

The differentiator in this role is not how much code you can write — with modern AI, strong engineers can produce in any stack. The differentiator is business translation. When a user says “I need direct access to the server to do X,” a Principal hears the business outcome underneath the request and designs a more secure, simpler way to reach it within our security, access, and architecture constraints. You turn “here’s what I want” into “here’s what you actually need” — and you can defend that architecture to a room of engineers and to the executive team in the same afternoon.