Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Apple (Raleigh, NC) em fev. de 2023
Entrevista
The interview went well, though unexpectedly, the manager posed advanced L4 architecture questions for an L2 position, focusing heavily on Kubernetes and cloud technologies.
The interview was overall positive, however, the manager unexpectedly asked complex Level 4 architecture questions for a Level 2 position, focusing extensively on Kubernetes and cloud technologies, which seemed beyond the scope for the role.
he role focused heavily on core Python coding skills and data structures, which were assessed through two intensive interviews per day and a series of challenging LeetCode-style questions, rather than following a traditional, infrastructure-focused DevOps interview process.
Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Apple em mai. de 2025
Entrevista
I can talk about my interview experience with Apple fr the role of Infrastructure/DevOps Engineer. I had first received Coderpad link to complete which is a technical assessment revolving around basics of devOps like Kubernetes, docker, AWS, linux, python scripting, ansible etc. Most of the questions were MCGs with three scripting question. Received feedback for the same through mail and they scheduled first round of technical interview on mail itself. No phone calls from any recruiters for the same.
Perguntas de entrevista [1]
Pergunta 1
Technical interview started with interviewer being straightforward asking for my introduction. Without the need to explain what is expected from this interview and introducing himself.
Then went ahead with opening coderpad shell and asked to code two programs of easy difficulty level but was very adamant on writing correct syntaxes for the same. I personally didn’t understand the need to not learn syntaxes in this ever evolving world and time of AI and GPT tools but that’s okay. After that interviewer focused on Linux fundamentals like asking for commands like what is exact command of memory checking, disk partition, etc.
Next, focused on Github commands and wanted pin point answers of everything without having a discussion which was awful. Then focused on Kubernetes and docker and kept playing question-answer instead of having real discussions around the tech side. Can see interviewer disappointment when I didn’t knew answers, syntaxes which tells about company culture. Fortunately, I have my job and there’s no dire need to work alongside such individuals because it was it would be such a nightmare. All in all, felt like I was interviewing for Linux Administrator role in 2015. Laid back interviewer approach in time. No questions on CICD, AWS infrastructure, Terraform on which my main skillset is.
Still I’m glad to have a chance to appear for the interview but it would be fruitful if there would have been discussions and if I had learnt something from this time.
Candidatei-me online. Fui entrevistado pela Apple (Singapura) em fev. de 2025
Entrevista
I attended 5 rounds of interview.
first one introduction round like screening.
Next 4 rounds technical discussion, every round about 45 mins, in that first 30 mins interview, then next 15 mins i got chance to ask questions.