The process was easy. Few questions were asked related to test automation, coding questions, test scenarios etc.
Interview went well but still got rejected.
No feedback was provides after multiple times asking the hr
Envié una solicitud electrónica. El proceso duró 2 meses. Acudí a una entrevista en Apple (Austin, TX) en jun 2024
Entrevista
The process took 2 months. Recruiter was super quick in scheduling the interviews. Started ghosting after the onsite. HM Phone call then 5 rounds in virtual onsite. It was a positive experience.
Preguntas de entrevista [1]
Pregunta 1
Coding Round was a variation of sliding window with a hashset. The other rounds were mostly resume based, dive-deep on the technologies used in terms of architecture of open-source test frameworks used, 2 Test Framework Design rounds. Bar Raiser was like Karan Thapar like interviewing.
Solicité el puesto a través de la recomendación de un empleado. Acudí a una entrevista en Apple (Bengaluru) en may 2024
Entrevista
I interviewed at Apple and I feel the interviewer was not patient enough to listen to me completely. In between he was interrupting and asking cross questions. I felt to every question he asked, he wanted the reply which he knows. Even though the code worked, got rejected.
Preguntas de entrevista [1]
Pregunta 1
1. Write a program where input is - "aabbbccaabbbcc" and output should be "a2b3c2a2b3c2"
2. Selenium version u are using and difference between Selenium 3 and Selenium 4
3. Maven and questions on maven
4. Why do we need different types of 2XX series if the developer can make 200 itself to work for different type. ( he was looking for something other than the standard protocols or conventions used)
5. Git fetch vrs Git pull
6. Bare minimum things to in browser before every release to confirm that the application is free from security vulnerability.
7. in postman, what is the difference between access token and refresh token.