Cursor07/15/2026
Руководитель группы разработки, безопасность агентов и продукта
Salary not specified
Полная занятостьУдалёнка
Responsibilities
- 01Chart the path from supervised agents to trusted autonomous ones: define the security primitives that enable agent autonomy, and lead the team that builds them
- 02Engineer the isolation that makes Cursor safe to run inside customers’ most valuable codebases: tenancy, workspace, secret, and data protections designed for real adversaries
- 03Build the authority infrastructure autonomous agents need: identity, scoped permissions, policy enforcement, and secure tool execution, so an agent can hold real responsibility with verifiable limits and full accountability
- 04Build customer-facing security controls that are understandable, usable, and strong enough for Cursor’s most security-sensitive customers, with crisp success metrics for security outcomes
- 05Hire, coach, and grow a high-performing security engineering team while staying technically close to the work: write and review code where useful, and keep execution fast and technically grounded
Requirements
- 01You’ve led engineering teams shipping production systems with high security, reliability, or platform stakes — and you want a problem space where much of the answer isn’t written down yet
- 02You have strong product and systems judgment: you can reason from user workflows to architecture, threat models, enforcement points, and operational tradeoffs — and you see security as something that enables product capability, not only restricts it
- 03You understand modern application security, authorization, tenancy, identity, secrets, data isolation, and secure-by-default platform design
- 04You have good instincts about AI agents: how they use tools, where authority should come from, how prompt injection and exfiltration show up in practice, and how to build mitigations that hold up against creative adversaries
- 05You’re comfortable operating in ambiguity: you can set strategy where precedent is thin, commit to a direction, and stay close enough to the implementation to know when to change it
- 06You can partner well across product, infrastructure, ML, and customer-facing teams