El proceso tomó 4 semanas. Acudí a una entrevista en Glassdoor (San Francisco, CA)
Entrevista
I had 2 phone interviews. After that I was invited Onsite and one more phone interview after that.
Onsite was a good experience. All the interviewers were well prepared and the interviews were interactive. Then I got the feedback that I was not prepared for the senior role. OK. So they consider me for the SDET role, and ask me to interview once more with the hiring manager.
This interview was chaotic, lots of open ended vague testing questions. The interviewer did not provide proper answers to my clarifying questions. I tried but it was like talking to a wall. It was sadistic. It was unfortunate because the other 8ish hours I spent interviewing with them were positive and interactive.
Overall, if you interview for this position, you can expect a positive experience. But be prepared for an unprepared/unwilling interviewer and take control of the situation.
Me postulé en línea. Acudí a una entrevista en Glassdoor (Mill Valley, CA) en abr 2017
Entrevista
The recruiter was very responsive throughout the process and kept updating me each step of the way. This made interviewing for Glassdoor very engaging. Interview rounds- 1 HR round, 2 technical rounds and then onsite.
The HR round was mostly behavioral and experience based. In technical interviews, Coding and testing strategies were focused on. Onsite comprised of 5 rounds in total. 4 technical rounds with senior testers, engineers, managers, architect panel etc and 1 process related interview with product. I was able to meet the entire team; right from product management to the director. This gave me a glimpse of the transparency and visibility in the organization.
Overall, I had a very good experience. I was able to meet the team and get a good understanding about the expectations of the role and the work culture at Glassdoor.
Preguntas de entrevista [1]
Pregunta 1
NDA
Helpful Notes:
Go though data structures, algorithms and collections.
The technical interviews will mainly focus on testing strategies and coding skills. You might be asked to write up test cases for multiple services. Be sure to cover all negative cases, edge cases, happy path scenarios and dependencies. It will help if you practice enumerating test cases for websites, algorithms and functions.
For coding questions, I think they are looking to see if you come up with the strategy. They might ask you to implement the solution in a different way. If you can give them a fair idea about your analysis on how to address the solution, I think that should be sufficient.
Be prepared for database queries. Joins and normalization in specific.
Apart from that, you can expect process related questions related to bug tracking, metrics, CI/CD, release management etc.
Automation and REST services questions were also part of the mix (If you work with technologies like Selenium, they will ask you specific questions related to it).