Principal Security Engineer, MongoDB

• 12+ years of experience in security engineering, software engineering, or a related discipline, including senior individual-contributor or technical-lead experience
• Bachelor's degree in Computer Science, Information Security, or a related field, or equivalent practical experience
• Deep, credible technical expertise in security, plus working depth across compute, network, and storage architecture
• A track record of forming and defending independent technical positions, along with the judgment to know when to stop debating and commit
• Experience influencing without formal authority, including with management and cross-functional partners, in both directions — accelerating and slowing down decisions
• Comfort owning ambiguous, deadline-driven work such as M&A diligence or partner risk reviews, and being accountable for the result even without the full picture upfront
• A genuine interest in mentoring and connecting other senior engineers, without needing a management title to do it
• Don't feel that you meet all of the requirements? We encourage you to apply anyway — studies show strong candidates sometimes rule themselves out prematurely

Desirable

• The Principal Security Engineer will serve as a senior technical anchor for the team
• This is a deep individual-contributor role that will stay hands-on with hard security and architecture problems, form sharp independent opinions, and know how to debate, align, and commit once GSO has made a call
• Key topic areas will include collaborating with our product teams to ensure identity and permission models meet customer needs for our new autonomous agent platform and working with integration security teams to push the envelope on automated detection, reproduction, and remediation of security vulnerabilities via AI
• What we need here is depth, judgment, and the ability to build up the bench of senior technical talent around you
• Maintain real technical depth in security and in MongoDB's product architecture — compute, network, and storage — deep enough to evaluate actual risk rather than apply generic best practice
• Form independent, well-reasoned opinions on security and architecture decisions, and voice them even when they cut against consensus or a leader's default plan
• Push teams to move faster when process or over-engineering is introducing complexity without reducing risk — and push teams to slow down when GTM pressure is outrunning a clear-eyed view of the risk
• Debate hard, then align, then commit: help the org land on the right call, then execute on it
• Seed and grow a working community of senior ICs embedded in security operations, product security, and enterprise security — connecting people, sharing knowledge, and creating the venues (formal or informal) for that to happen
• Lead time-boxed, high-stakes, cross-functional engagements such as M&A security due diligence and partner risk assessments, often with incomplete information and a short runway
• Draw on your own expertise where it applies, and quickly figure out how to close knowledge gaps elsewhere — staying accountable for the outcome either way
• Success in This Role Means
• Leadership trusts your technical judgment on the hardest, most ambiguous calls
• Your willingness to disagree — in either direction, faster or slower — makes decisions better, not just louder
• A real community of senior security talent has formed around you in GSO