Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Apple (Sunnyvale, CA) en dic 2016
Entrevista
Apple reached out to me over LinkedIn a few months back, asking me to consider them for an SRE position with their Maps organization. They moved very quickly at first as I had an offer from Google on the table. Solid two-hour technical phone screen was followed by an invite to the Sunnyvale office. On-site was typical--6 or so interviews plus lunch with the recruiter. Lots of python on the whiteboard, lots of systems architecture and troubleshooting questions, and the same overemphasis on CS dogwhistle questions as Twitter and LinkedIn are known to use for Ops/SRE positions.
Altogether a pretty decent round of interviews and I was very confident in my chances. The hiring manager seemed very stressed about headcount and growing their small team of less than ten engineers to something able to efficiently roll out improvements competitive with Google seemed like a serious challenge. This was the middle of December.
Nothing for the next week or so before everyone disappeared for Christmas. Two other offers came in, but solid radio silence from Apple. In early January when everyone was back, I gave the recruiter a call and he seemed flustered and I think me might have even forgotten about me completely. Either way, he reassured me and said that my case was going in front of the hiring committee that week. Of course, I hear nothing back.
While I will say that I wasn't seeing a great fit with Apple's odd culture and likely wouldn't have taken the offer considering the alternatives, I do feel the recruiter's lack of response is unprofessional at best and makes the company look like it doesn't even care about getting qualified talent into its internet services org at worst.
Don't waste your time.
Preguntas de entrevista [1]
Pregunta 1
1/3 linux internals, 1/3 web services troubleshooting and design, 1/3 data structures and algorithms.
Envié una solicitud electrónica. El proceso duró 2 meses. Acudí a una entrevista en Apple
Entrevista
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.
Preguntas de entrevista [3]
Pregunta 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
Envié una solicitud electrónica. Acudí a una entrevista en Apple (Singapur)
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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