СШАLead Corporate Security Engineer
2 нед. назад
165k–220k USD / годСШАLead
Lead Corporate Security Engineer responsible for securing corporate IT environment and collaborating with various teams to maintain security.
О компании
- We're building the world's first creative entertainment platform, where the entire world can feel the joy and fulfillment of making music. Music is for everyone: Our users include everyone from grandmothers creating songs for their loved ones, to Grammy winners using Studio, our power tool, to make the most popular hits in the world.
- Building the future of entertainment requires ambition. The pace is fast, the problems are hard, and the work demands ownership and intensity. For the right people, it’s incredibly rewarding: a chance to shape a new medium, work with a small team that cares deeply about quality, make music, drink too much coffee, and build something that millions of people use to express themselves in ways that were never before possible.
- is the fastest growing consumer entertainment company and the leader in AI music. We are backed by leading investors including Bond Capital, Menlo Ventures, Lightspeed Venture Partners, IVP, Forerunner, Union Square Ventures, Alkeon, Quiet, Matrix Partners, Schroders Capital and, NVentures (venture arm of NVIDIA).
Обязанности
- The Lead Corporate Security Engineer will be our domain expert for securing our Corporate IT environment. You’ll work closely with colleagues in IT, Business Systems, Security, and Engineering to ensure that our corporate systems are implemented and maintained securely. As a senior member of the team, your impact will be split between building your team, enabling others, and doing hands-on work to mature our systems, processes, and behaviors. You'll lead the corporate security domain end to end: identity and access governance, endpoint and vulnerability management, detection and response, third-party integration risk, vendor assessment, and SaaS posture. You'll set the standard, own the roadmap, and be accountable for the outcome. IT Engineering runs the platforms day to day and are your closest partners.
- First 90 days: you've formed your own view of our security posture, built working relationships with the IT engineers the broader Security team, and told us the three things we're wrong about
- First 6 months: a corporate security roadmap exists that IT and the CISO are aligned behind, with the sequencing and the tradeoffs made explicit; the highest-risk items are already moving
- First year: entitlement sprawl and vulnerability backlog are measurably down, detection reflects our real risks, third-party review is fast enough that nobody routes around it, and the standard holds because it's built into tooling and shared judgment rather than into you
Требования
- ~8+ years in corporate/enterprise security or security engineering, including having owned identity, endpoint, or SaaS security as a domain rather than as a set of tickets
- Deep hands-on expertise with a modern IdP and with IGA or access-governance tooling (Lumos, Veza, ConductorOne, Opal, or similar)
- You've designed an entitlement or RBAC model across a large SaaS portfolio and lived with the consequences long enough to know what breaks
- Endpoint security depth in a macOS-primary fleet: MDM-delivered hardening, compliance and device trust, third-party patch and vulnerability management at scale
- Strong command of OAuth, SAML, OIDC, and SCIM, and of the risk model behind third-party integrations
- A track record of setting a security standard that other people applied without you enforcing it — written policy, tooling, defaults, or all three
- Experience influencing engineering and business teams who don't report to you, early enough in their process to change the outcome
- Automation fluency: Python or TypeScript, REST APIs, and a habit of building integrations and internal tooling as a normal part of the job
- Excellent writing and judgment under ambiguity. You can hold a position with an executive and change it when the evidence says to
- A calibrated sense of risk and how to communicate likelihood, impact, and tradeoffs
- Helpful, not required: insider risk or DLP programs, zero-trust network access, SOC 2 or ISO program ownership, just-in-time access patterns or identity-as-code, securing AI agent and non-human identity access, prior experience as the first or second security hire at a fast-growing company.
Другое
- Ownership splits by layer, not by system. IT Engineering owns the run; you own the standard and the direction.
- You set the corporate security roadmap. What we secure, in what order, to what bar with buy-in from leadership and XFN stakeholders
- IT engineering owns platform operations. Our SaaS portfolio is administered and integrated by them. You define what those platforms must enforce
- You raise the bar around you. You make your reasoning explicit so that partners make good security calls without you in the room, and you build the tooling and defaults that make the secure path the default path
- Own the access model at : the RBAC and entitlement design, least-privilege defaults, and the governance layer in Lumos that enforces them
- Set the standard for what access review, certification, and approval should look like here — then build toward it rather than importing someone else's framework
- Drive access lifecycle automation so joiner/mover/leaver is correct by default and exceptions are visible
- Get ahead of non-human identity: service accounts, agents, and automations are a growing share of what holds access at , and we need a model for them before it's urgent
- Own the security standard for our fleet: hardening baseline, compliance signals, device trust, and how endpoint posture feeds access decisions
- Own third-party vulnerability management as a program — coverage, risk-based remediation SLAs, reporting, and the negotiation with teams whose tools are the problem
- Partner with the IT engineer who owns Kandji so the standard becomes deployed policy without degrading how people work
- Own our EDR deployment and maintenance
- Collaborate with Detection and Response on corporate security incidents to closure
- Own how evaluates third-party access: integration and OAuth review for Slack, Google Workspace and the rest of the portfolio, plus vendor security assessment at purchase and renewal
- Define our risk appetite in practice and make it legible enough that others apply it without you
- Turn recurring decisions into policy, scope guidance, and tooling so the review queue shrinks as the company grows
- Build and own the program: the bar for our SaaS applications, the assessment cadence, and the remediation that follows
- Improve tenant-level configuration across the portfolio — SSO and SCIM coverage, MFA and session policy, admin role hygiene, OAuth grant and token management, data sharing defaults
- Work with IT, Security, Engineering, AI Enablement, and Legal to shape how builds and buys
- Influence the scope of what comes next: how our GRC function plugs in, what we automate versus staff, where the next investment goes
- Mentor and raise the technical bar for people around you, including partners who aren't security specialists
- This is an L6 individual contributor role. At , L6 means you shape how a domain operates cross-functionally and set the standard of excellence within it. You identify problems before they become systemic or are named by others. You multiply the efforts and development of the people around you, and you improve the system that produces the work, not just the work itself. You make your principles explicit so others can make good calls independently, and you ensure what you learn travels beyond the immediate team.