J'ai postulé via un recruteur. Le processus a pris 1 jour. J'ai passé un entretien chez Splunk (San Francisco, CA) en déc. 2016
Entretien
phone interview scheduled in evenings after 8pm. generic, open ended. the interviewer was really unsure of what to ask, it was 8pm so seemed that we were both annoyed at the timing. Not sure why she wanted to interview so late. Didn't seem like the team knew what type of candidate they were looking for. Job description should have said: Jack of all traits. (they wanted a developer who wants to be a scrum master, run manual testcase and automate the testcases)
Questions d'entretien [1]
Question 1
generic, open ended. the interviewer was really unsure of what to ask, it was 8pm so seemed that we were both annoyed at the timing. Not sure why she wanted to interview so late. Didn't seem like the team knew what type of candidate they were looking for. Job description should have said: Jack of all traits. (they wanted a developer who wants to be a scrum master, run manual testcase and automate the testcases)
J'ai postulé en personne. J'ai passé un entretien chez Splunk
Entretien
not too hard. Generally a half day process. Very smart engineers. The actual difficulty depends on the group/team that is hiring. There is no manual QA , test engineers are on par with developers.
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Splunk en mai 2011
Entretien
Recruiter need to be better in communicating appointment time in a better manner. Phone interview last for about an hour. Questions were well rounded from basic to advanced level which included QA methodologies and processes related questions.
