Solicité el puesto a través de una agencia de empleo. El proceso duró 5 semanas. Acudí a una entrevista en Apple (Cupertino, CA) en ene 2020
Entrevista
I got my interview through Triplebyte, so the process of getting my on-site interview may be different from others. It consisted of a 30 minute call with a manager to discuss the role and briefly go over my background. My on-site lasted about three hours with seven people, an HR person, a product lead from the team, two team members, the manager I originally had the call with, and finally two more team members. All technical questions were followed up with lots of questions about how I would test the functions.
Preguntas de entrevista [6]
Pregunta 1
What were some personal projects that challenged you? How did they challenge you? How were they architected? (Be ready for lots of follow up on anything you say)
I was also asked how I would approach testing a feature very specific to the team I would be working on, so know the role and think in advance about how you might test features you know they have
Solicité el puesto a través de un captador. Acudí a una entrevista en Apple (Nueva Delhi) en ene 2022
Entrevista
Once your profile gets shortlisted , HR will call you and arrange first round of technical interview R1 for 45 minutes.
There might be 3 to 4 rounds of interview , totally depends on your technology.
Preguntas de entrevista [1]
Pregunta 1
They asked to write few programs like fibonacci series and gmail login page.
API automation
Envié una solicitud electrónica. Acudí a una entrevista en Apple en abr 2021
Entrevista
The initial WebEx interview with the hiring manager went well; she seemed intelligent and conscientious, and asked about my experience. This was followed by a coding interview with one of her test engineers (intelligent with a Masters in CS, but poor communication skills).
Preguntas de entrevista [1]
Pregunta 1
Classic instance of what opponents of coding interviews (which does not include me) object to. The engineneer was looking for me to spot the recursive trick for a string conversion problem, which was by no means obvious, and was by no means obviously correct even after he gave up on me and pointed it out. He ended the programming session after I raised questions about correctness, even though there was time left, without giving me a chance to implement the algorithm he’d suggested. He said that I had shown that I knew how to code it, but obviously meant the opposite: I got a rejection email soon after the interview. (I don’t disagree with the rejection: Apple seemed to be looking for a CS major to output code quickly; I’m a math major who has only written a test harness from scratch three times in my career.)
Most troubling for a testing position, while I was writing doctests† to make sure I had understood his specification, he told me there wasn’t enough time to write tests, or to document my iterative algorithm: I should just start typing code. Somewhat less troublingly (at least for me as an applicant, if not as an Apple customer), the problem would probably have been a test of memory rather than coding ability for a CS major, since it seems to be a topic which would have been covered in class.
___
† doctest is a very cool Python module, which examines the examples you put into a function’s documentation string, and complains if it does not produce the output you specified.