|
|
|
|
|
|
by deepGem
1118 days ago
|
|
|
Pretty much all my interviews except in Meta. This is in India though.
Meta was the most organized but even that interview went over 2 weeks.
My Walmart interview lasted 2+ months. Round1 week1, round 2 week 3 etc etc. This is for Staff+ level positions. EDIT: Just to state, companies do give enough time to prepare for the interview. I am only talking about the interviewing duration, not the prep time. |
|
|
The culture is so different here in Australia and New Zealand.
I've done a lot of interviewing of candidates over the last 12~ years or so - here are some generalisations based on my experience and that of my peers for tech roles:
- 95% of the time it's 2-3 interviews / meetings. I have seen a single interview be enough when the person is already known to the team and the interview went well confirming and clarifying existing knowledge of the person.
- The first is usually a call with people and culture / the internal recruiter - high level intro and general culture fit. These tend to be between 15-30 minutes. You should usually know if you're being offered another interview by the end of the call - or within a few days at most and have the next (main) interview setup for the next week or two at most.
- Then if the role is for a developer / programmer or design / UX the candidate is usually sent a coding (or design) test which can be done remotely and will usually take 30-120 minutes but this obviously varies depending on the test, role, and persons abilities.
- Second is often a technical and team fit interview with two people in or working closely with the team / department you're hiring for. These are usually around 45-90 minutes. You should usually hear back about this within a day or two, and if another interview is required you would hopefully have that booked in for some time in the next week or two.
- A third is often done if the team/tech lead wasn't in a previous session - or if the interviewers can't agree or get a good feel for the candidate.