Security Adoption Engineer

Apple's security product adoption team partners with engineering teams across

the company to help them move from awareness to active use of Apple's internal

security tooling. We're 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.

DESCRIPTION

You'll be the bridge between Apple's 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 third. The

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. You'll own that

experience end-to-end: identifying which teams to prioritize, understanding

their stack and constraints, and packaging what they need to get unblocked. The

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. You'll 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 better. On the technical side,

you're fluent enough in server-side systems and DevOps practices to earn

credibility in the room. You understand how services are deployed and operated,

you're 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 isn't to write the integration code;

it's to make sure the right people understand what they need to do and feel

confident doing it. This role sits on a team with a broader mission: building a

scalable, repeatable motion for security product adoption across Apple. You'll

help shape what that motion looks like as we grow it.

MINIMUM QUALIFICATIONS

Experience in a systems administration, DevOps, site reliability engineering, or

production services role. You know what it looks like to keep services running

at scale. Practical familiarity with server-side environments: Linux/Unix, shell

scripting (bash), infrastructure tooling (e.g., configuration management,

deployment pipelines), and version control (Git). Strong written and verbal

communication skills. You can run a meeting, write a clear summary, and produce

a plan. Demonstrated ability to manage multiple workstreams independently

without losing track of details or next steps.

PREFERRED QUALIFICATIONS

Background in a customer-facing technical role such as technical account

management or solutions engineering, where you were responsible for a team's

success, not just their implementation. Experience working across many teams

simultaneously in a consulting, enablement, or platform team capacity. A track

record of identifying the root cause behind repeated friction and advocating for

structural fixes rather than one-off workarounds. Familiarity with security

concepts relevant to software infrastructure: access control, credential

management, secrets handling, or similar. Exposure to how large organizations

roll out internal tooling at scale, what works, what gets stuck, and why. Strong

instinct for identifying and communicating patterns across a portfolio rather

than treating every engagement as a one-off.