AI Security Engineer - Red Team
Generate a McCoy IQ challenge in 30 seconds.
See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Key details
Why this role is notable
Apple is standing up a dedicated red team to hunt for security risks inside its AI agents and AI integrations, not just its traditional services, signaling that agentic AI is now a core attack surface it expects to be probed and defended like any other production system.
Job Description
We are the Apple Services Engineering (ASE) Security Red Team. We focus on deep technical security review work of critical ASE services and infrastructure. These security reviews will be scoped and focused on review depth and quality. We are growing our team and looking an AI Security Engineer to lead deep reviews that identify meaningful security improvement opportunities. In this role, you will work closely with the AI platform teams, security engineering, InfoSec, privacy, SRE, detection, and design review teams to keep Apple's services and AI agents secure for our users. You will identify security weaknesses, validate and design detection mechanisms, and provide actionable recommendations to enhance our security posture. You will go beyond simple to find risks and identify obscure and complex risks within AI integrations and deployments. You will collaborate with AI architecture and engineering teams to continuously validate and improve our security controls and detection capabilities, with a strong focus on developing repeatable testing frameworks and metrics-driven security improvements. If you love diving into complex AI systems, and driving the security of that system over time, we want to talk to you!
Audit details(provenance, verification trail, raw fields)
Core fields
apple:200690601-3337Provenance
appleVerification trail
This posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
LLM enrichment
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
