Principal Security Architect

About the role

Knowing those systems well enough to turn requirements into durable, reusable patterns and partnering with engineering teams to get those patterns deployed is the job. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals.

Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond.

Master's Degree in Statistics, Mathematics, Computer Science, Risk Management, Cyber Security, or related field AND 4+ years experience in software development lifecycle, large scale computing, threat modeling, cyber security, or anomaly detection OR Bachelor's Degree in Statistics, Mathematics, Computer Science, Risk Management, Cyber Security, or related field AND 6+ years experience in software development lifecycle, large scale computing, threat modeling, cyber security, or anomaly detection OR equivalent experience.

These requirements include, but are not limited to the following specialized security screenings: You can hold a complex, shifting picture across many moving parts and act on it without rebuilding it from scratch each time. You can decide with incomplete information under real pressure, defend that decision to people who disagree, and change it when the facts change.

You read the code, query the telemetry, and build your own tooling rather than waiting for someone to hand you the answer. 6+ years of hands-on security experience. A corporate or enterprise environment at scale, where controls compete directly with productivity. Multiple assessment disciplines; security architecture, threat modeling, code reviews, offensive and defensive security, detection and response engineering.

Experience with common scripting languages and working knowledge of agentic development tools. A track record of making the secure thing the easy thing for other teams, through paved path. Practical experience working collaboratively across teams and earning trust. Keep a current read on productivity risk, maintaining a running synthesis of where the environment stands and rapidly incorporating signal as it evolves.

Represent the security position in the room, and be prepared to go deep with engineers. Work closely with our engineering partners to build the tools and repeatable patterns that both reveal risk and help close it. Make risk legible to people who do not work in security: what it means, what it costs, and what happens if it waits.

Decide what gets worked on next, making the call when the answer is not obvious and the facts are incomplete, then revisiting it when conditions change. Turn every interaction into updated priorities and those priorities into roadmaps teams can run.