Security Adoption Engineer

Apples security product adoption team partners with engineering teams across the company to help them move from awareness to active use of Apples internal security tooling. Were looking for a Security Adoption Engineer who operates at scale: someone who can guide hundreds of engineering teams toward adoption while simultaneously working with our product engineering teams to make the experience better for every team that comes after. This is a role where your instinct to eliminate friction is as important as your technical fluency.

Youll be the bridge between Apples security products and the hundreds of internal engineering teams who need them. Your days will look less like deep debugging sessions and more like running a high-velocity portfolio of lightweight engagements simultaneously: an initial discovery call with one team a clear deployment plan for another a follow-up on blockers with a teams you work with are busy. They need someone who shows up prepared asks the right questions cuts through ambiguity and leaves every meeting with a crisp set of next steps they actually want to follow through on. Youll own that experience end-to-end: identifying which teams to prioritize understanding their stack and constraints and packaging what they need to get engagements themselves are only half the job. The other half is using what you learn in the field to make adoption easier for every team that comes next. Every friction point you encounter is a signal. Youll work closely with our product engineering teams to translate that signal into better tooling clearer documentation and smoother onboarding flows with a long-term goal of making the adoption path so well-paved that teams can largely find their own way. The best outcome for this role is one where your direct involvement becomes less necessary over time because the product got the technical side youre fluent enough in server-side systems and DevOps practices to earn credibility in the room. You understand how services are deployed and operated youre comfortable reading and writing a bash script and you know what words like rollout config management and on-call mean from experience not just in theory. That said your primary job isnt to write the integration code; its to make sure the right people understand what they need to do and feel confident doing role sits on a team with a broader mission: building a scalable repeatable motion for security product adoption across Apple. Youll help shape what that motion looks like as we grow it.

Manage a high-volume concurrent portfolio of engagements spanning hundreds of internal engineering teams at various stages of security product discovery conversations to understand each teams architecture current security posture and blockers to product capabilities into clear actionable deployment plans tailored to each teams environment and engagement progress across teams surface recurring patterns identify systemic blockers and escalate where as a credible technical point of contact able to hold a technical conversation with an SRE and then summarize the outcome clearly for a non-technical closely with product engineering to translate field observations into concrete improvements: better UX clearer onboarding and reduced manual steps so every subsequent team has a faster path to work toward making adoption self-service wherever possible treating every manual touchpoint as a candidate for lightweight but accurate documentation of engagement status key decisions and next define and continuously refine the adoption playbook as the portfolio scales.

Experience in a systems administration DevOps site reliability engineering or production services role. You know what it looks like to keep services running at familiarity with server-side environments: Linux/Unix shell scripting (bash) infrastructure tooling (e.g. configuration management deployment pipelines) and version control (Git).nStrong written and verbal communication skills. You can run a meeting write a clear summary and produce a ability to manage multiple workstreams independently without losing track of details or next steps.

Background in a customer-facing technical role such as technical account management or solutions engineering where you were responsible for a teams success not just their working across many teams simultaneously in a consulting enablement or platform team track record of identifying the root cause behind repeated friction and advocating for structural fixes rather than one-off with security concepts relevant to software infrastructure: access control credential management secrets handling or to how large organizations roll out internal tooling at scale what works what gets stuck and instinct for identifying and communicating patterns across a portfolio rather than treating every engagement as a one-off.