Apple is looking for a Software Engineering manager to develop the next generation of Apple DNS infrastructure. You will be responsible for critical systems, such as Apple DNS, that every single Apple team and billions of customer devices depend on! The work for the team (and engineering manager) involves contributing infrastructure code (Go, shell, C…) to handle services and clusters of servers on six continents in various network environments, address production issues and design for the future. You will partner with OS and services teams to deeply integrate our devices with our services. Your team’s work will help improve the performance of Apple Services such as Apple Music, Apple TV, App Store, and many more!
You will be responsible for collaboratively setting direction for how Apple operates DNS infrastructure, collaborating with teams across Apple. You’ll also be responsible for handling relationships with various open source communities we collaborate with. Day to day, you will be working with your developers to set priorities, review code and architecture, and lead production deployments. Your team will be responsible for second tier operational support. You will be required to review performance data and investigate any performance regressions that arise.
We are looking for an engineering manager with a validated experience of deeply understanding a technical system, being responsible for the evolution of its architecture and contributing infrastructure code for it in the service of other teams and systems. The candidate should be able to dig into the failures of said systems and work in a collaborative way toward urgent remediation as well as longer term architectural and procedural changes.
Prior experience with DNS is a requirement. We expect the ideal candidate to over time grow to that level and contribute their unique perspective on the various systems and sub-systems the Apple DNS team is responsible for. The engineering manager filling the position will regularly dive into RFCs and interact with other teams in writing the RFCs.