Skip to main content

Site Reliability Engineer (SRE) - Elastic Disk

Posted today

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: As a Storage SRE on Apple Cloud’s Elastic Disk team, you will help design, operate, and scale distributed storage systems that underpin critical Apple services. You’ll own delivery of platform features, shape directions, and drive reliability across two sites, impacting hundreds of millions of users. You will work with cross-functional partners to improve reuse, efficiency, and simplicity of our storage stack. This role blends software and systems engineering with on-call responsibility to maintain high availability in a large-scale cloud environment. Compensation / Benefits medical and dental coverage retirement benefits employee stock programs employee stock purchase plan tuition reimbursement relocation support Responsibilities own and deliver platform designs and deliverables with cross-functional buy-in provide technical feedback to colleagues to uphold standards and guidance drive technical standards across a two-site team manage on-call responsibilities and respond to alerts to maintain service availability learn and improve open-source, vendor, and internal tooling for configuration, deployment, logging, and monitoring deploy, monitor, and support new and existing services and stacks shape solutions for large-scale storage challenges across block, object, and file storage layers
Key requirements: 4+ years building, operating, and scaling distributed storage systems in large-scale environments ability to design, author, understand, and release code in Go (preferred) or Java/Python/Rust strong knowledge of Linux storage concepts and systems (LVM, XFS, ext4, S3, Ceph, Gluster, NFS) understanding of Linux internals, networking, and distributed systems experience with provisioning, data migration, backup & recovery, at-scale testing, DR, and capacity planning automation-first mindset ability to give and receive technical feedback collaboration across teams and locations Go (preferred) / Java / Python / Rust Linux storage know-how (LVM, XFS, ext4, S3, Ceph, Gluster, NFS) Linux internals and networking

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this