at Apple
Location
New York City, United States of America
Compensation
$216k–$325k USD
Type
full time
Posted
4 weeks ago
Market range · company + function + seniority
p25 · target · p75 · n=133
Posted $325k · above the band
Posting health
Aging · 70Tailor your résumé to this role in 30 seconds.
Free account · ATS keyword check · per-job bullet rewrite by Claude.
The Architect will own the technical direction for Apple Pay's distributed systems — driving reliability engineering practices, observability strategy, and scalability architecture across a high-throughput, payment-critical infrastructure. Day to day, this means reviewing designs for resilience gaps, writing code and prototypes to validate architectural decisions, and leading incident reviews and postmortems that drive systemic fixes. The role also involves close collaboration with client, server, devops, and product engineering teams to ensure architecture decisions account for real-world operational constraints at Apple's global scale.
Guide the evolution of Apple Pay's distributed systems with a clear point of view on trade-offs (consistency vs. availability, latency vs. durability, cost vs. redundancy) appropriate to payment-critical infrastructure
Define and drive adoption of reliability engineering practices across the org: SLIs/SLOs/SLAs, error budgets, capacity planning, and failure-mode analysis tailored to systems where correctness and availability directly affect transaction success
Establish the observability and metrics strategy needed to operate payment systems reliably at scale — including latency, traffic, errors, distributed tracing, and alerting that reflects real transaction impact
Partner with teams across Apple Pay to review designs for scalability bottlenecks, points of failure, and resilience gaps
Write code and prototypes where it matters — diving into the codebase to validate designs, unblock teams, or resolve production issues
Lead technical reviews and postmortems for major incidents affecting Apple Pay systems, driving systemic fixes rather than one-off patches
Mentor engineers on distributed systems fundamentals: consensus, replication, partitioning, idempotency, exactly/at-least-once semantics, and trade-offs relevant to payment processing
Collaborate with client, server, devops, and product engineering teams to ensure architecture decisions account for real-world operational constraints (deployment, rollback, multi-region failover, capacity headroom) at Apple's global scale
Proven track record designing and operating distributed systems at scale in high-throughput, low-latency production environments
Deep expertise in distributed systems fundamentals: replication, partitioning/sharding, consensus protocols, eventual vs. strong consistency, idempotency, and failure handling across network partitions
Hands-on experience defining and instrumenting metrics for availability and scalability (e.g., SLOs, error budgets, distributed tracing) and using them to drive concrete engineering decisions
Strong background in the building blocks of scalable systems: load balancing, caching layers, message queues/event streaming, database sharding/replication, service mesh, and rate limiting/backpressure mechanisms
Demonstrated ability to set technical direction across multiple teams without direct management authority, and to communicate trade-offs clearly to both engineers and leadership
Track record of leading incident reviews or reliability programs and turning postmortem findings into durable systemic improvements
Skilled at operating with ambiguity across large, complex system landscapes and driving alignment across multiple teams and stakeholders
Experience with multi-region or globally distributed systems, including failover and disaster recovery design at scale
Prior experience in payments, fraud/risk systems, or other regulated, high-availability financial infrastructure
Contributions to open-source distributed systems projects or published technical writing on the subject
Experience establishing or maturing a devops/reliability practice within an organization
Apple Pay builds and operates the systems that power Apple Pay transactions at global scale, where downtime or a scalability shortfall means a failed payment for a real person at a register or checkout. This Architect role is responsible for setting the technical direction for how Apple Pay's systems achieve reliability, scalability, and availability — not just in design docs, but in the metrics, SLOs, and operational practices that hold them accountable in production. It is a role for someone with strong, well-reasoned opinions about how distributed systems should behave under load, failure, and partial degradation, and who can translate those opinions into concrete architecture, tooling, and team practices across the org.
At Apple, base pay is one part of our total compensation package and is determined within a range. This provides the opportunity to progress as you grow and develop within a role. The base pay range for this role is between $216,200 and $324,800, and your base pay will depend on your skills, qualifications, experience, and location.Apple is an equal opportunity employer that is committed to inclusion and diversity. We seek to promote equal opportunity for all applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, Veteran status, or other legally protected characteristics. Learn more about your EEO rights as an applicant
At Apple, we believe accessibility is a fundamental human right. You’ll find that idea reflected in everything here — in our culture, our benefits and our digital tools. By welcoming as many perspectives as possible, we help you build a career where you feel like you belong.
Learn about accessibility in Apple’s workplace
Learn about reasonable accommodations for job applicants
Apple accepts applications to this posting on an ongoing basis.
More open roles at Apple
Hiring velocity, headcount trend, and every open posting on one page.
Open postings ranked by description similarity — useful if this role isn't quite right.