Site Reliability Engineer applicants have rated the interview process at Apple with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 23% positive. To compare, the company-average is 63.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Site Reliability Engineer roles take an average of 65 days to get hired, when considering 13 user submitted interviews for this role. To compare, the hiring process at Apple overall takes an average of 29 days.
Common stages of the interview process at Apple as a Site Reliability Engineer according to 13 Glassdoor interviews include:
One on one interview: 30%
Phone interview: 30%
Presentation: 13%
IQ intelligence test: 10%
Group panel interview: 7%
Skills test: 7%
Other: 3%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 2 weeks. I interviewed at Apple in Mar 2016
Interview
A recruiter contacted me through email.
1) Screening Process (Assignment in Linux was given with a deadline of one week)
2) Phone Interview
-> Resume Discussion
-> Linux command to check how busy is the CPU
-> How to debug a remote server
Next round is Onsite but did not went to the next round.
Interview questions [1]
Question 1
Given an assignment on linux and deadline of one week to complete.
I applied online. The process took 2 months. I interviewed at Apple
Interview
Beware of fake interviews
I was interviewing for a position that I was told was the last headcount for the team. The process was quite long, involving six rounds of onsite interviews. The interviewers seemed a bit unprepared, and the conversations felt more like they were going through the motions rather than genuinely assessing my skills for an open role.
After about a month, I was rejected without any specific feedback. Shortly after, the same recruiter started reaching out to me about other job openings I had not applied for. This made me feel like the initial interview process may have been for a position that was already filled, and my candidacy was used to "pump up the numbers."
I've heard from others that this can be a pattern. If you notice signs like unnecessary interview rounds, repetitive questions, a position being described as the "last headcount," or unprepared interviewers, it's a strong sign the position has already been filled. It might be time to move on to other opportunities.
Interview questions [3]
Question 1
You are given a machine where you have shell access, but the PID limit is exhausted. You need to figure out the root cause using shell builtins
I applied online. I interviewed at Apple (Singapore)
Interview
After sending in the application, I received an email to schedule a call with a developer from the US. Pretty standard Leetcode questions on efficiency and understanding basic logic. The interview included a live coding session and ended pretty quickly.
Interview questions [1]
Question 1
You have a file with N lines. How do you output them equally into M buckets?
HR screen
Hiring manager
Coding screening
Virtual interview loop
1. System Design focus on K8s
2. System Design - Reliability and availability
3. Coding- Leet code Medium
4. System Design - Network stack, Linux