5 rounds is insane, and to me it's the mark of a severely dysfunctional company.
Don't even get me started on multiple choice personality tests taken by wannabe psychologists in HR, or the general idiocy that is whiteboard coding.
1 - Uncertain about something about you (I imagine technical aptitude), and want to rule out their concern 2 - There are 2 close candidates
Either way you should confirm that it is the final stage, confirm what they'd need to see to hire you and if you are feeling confident maybe use it to negotiate salary!
Sounds like you are close to getting the job though so I wouldn't dismiss it especially if you have no doubts about the company!
If you don't want the job, don't do the interview.
your questions:
- Should I go for it? Up to you obviously
- Are they reliable? No
- Is it acceptable / worth it? Unknown
- What would you do? Depends on whether I have other irons in the fire. If this was my only option and I still like this option, despite being messed around at this stage, then I would stay in process, so long as I could guarantee that I would not hold resentment, as this will come across on coding challenge and further interactions with team.
Good luck, whatever you decide!
Side note, if this company can’t pick someone after after interviewing candidates 4x, it seems to me they don’t really understand what they want / fungible requirements are endemic to their culture. That may or may not be a desirable feature in this potential employer.
This is a sign of chaotic internal processes, not to mention a culture of disrespect toward candidates’ time.
If you get the job, expect work to be regularly dropped in your lap on a Friday afternoon to prep for a meeting on Monday with higher-ups. This meeting will be canceled.
Expect pervasive overconfidence and excessive process (who does six rounds of interviews unless they think they “only hire the best”?).
And, when you need some additional headcount on your team, expect it to arrive sometime the quarter after next, too late to be of much help.
But yeah if you need the paycheck, what are you gonna do?
This gets them out of their "so many choices" analysis paralysis mode and if they like you enough, into a FOMO mode where they risk losing to to an unnamed competitor. If it doesn't get them into a FOMO mode, then they weren't that into you in the first place and you saved the time waste.
$0.02.
- do you want to work with them?
- do you care, or are you just trying to find anything?
- are you busy? that's a lot of interviews, but maybe you have the time?
- how have the interviews been thus far? interesting and high-bandwidth or a confused waste of time
in general through I would be biased pretty strongly against such a company. either they are small and being fussy or huge and don't really have it together. a company is trying to present their best face to candidates - to the point of being actively misleading. if they can't interview candidates without it turning into a shitshow how together do you think they are in general?
> Should I go for it? Are they reliable, is it acceptable/worth it? What would you do?
Kind of all depends on your situation.
How have the interviews gone, from your perspective? You have been evaluating the company during them, right? (if not, please start, asking your own questions during interviews is _extremely_ important)
At any sane company, them asking for another interview should mean they're serious, they wouldn't want to spend one of their engineer's time otherwise.
I'd probably just do it, but I'd definitely set a limit for myself (communicating that limit may be a mistake). I'd probably also re-ask what the process is from here, what's the next step(s)?
Or maybe they pushed the code you wrote in your previous round to prod and got an issue so now they need you to fix it ;)
Also, as others have pointed out, it's not clear what a "round" means to you. Where I work, we typically have two rounds: Screening (typically 2 meetings), and full panel (6-8 meetings). Before Covid, the full panel round was done in-person in a single day. Now it might be spread out, but it's still one round. Meetings between the candidate and the recruiter don't count as a round.
Personally, if they can't get their interviews right (they forgot to test for something?), I don't trust them to be a good employer.
Alternatively, if you really need the job, then yes you should participate in the interview.
I really wouldn’t overindex on it. Others are saying it’s a bad sign about their internal procedures and culture which, sure yeah it’s not an ideal way to run an interview process. But that might just mean that the HM did it in a previous job and it worked out well, or the recruiting head thinks it’s a good idea, and everything else is fine about the company.
For the sake of an hour of your time and some extra interview practice- just do the interview. If you want, use this thread to guide your questions after you get an offer and figure out whether there are other signs of internal dysfunction. But turning down a job you want because of this one blip in the interview process would strike me as petulant.
Round 1: Screening for strategic fit. Round 2: Paired coding interview (~ 1.5 hrs) Round 3: Detailed interview with co-founder. Round 4: Panel interview with team I was to work with.
It didn't feel insane, in fact the more I interviewed, I pretty much got a detailed picture of what I would do if on that job, and who I would work with. Lots of times you can't get that sort of peek into your prospective workplace.
The thing that made this process bearable was : 1) niceness of people involved 2) Having a fairly limited coding phase....
So as long as these are not all coding phases, it will give you a really good view of the org fit for you.
> Are they reliable
well, depends on the company.
I ended up doing the challenge because I thought it would be a good learning experience and a way to ask questions and learn (even) more about the company.
I was offered the job straight away but turned it down because I felt the company was dysfunctional as many of you suggested, slow to make decisions and slightly chaotic. There were some nice people and unfortunately some (potentially/seemingly) toxic ones.
Can't justify accepting it when the market is so good right now and there so many good options out there. I will keep looking. Thanks once again all of you for your help. I read your comments with great interest.
I would have been honest with them, tell them you didn't expect a 6th, ask them if they think you are close to getting the job, else it will be a waste of effort on your end.
Assuming there are indeed internal doubts, then chances are there's a person in power who is casting those doubts. Could be for example there's a preferred candidate who that person in power already set their eyes on. And the inexperienced hiring manager is not seeing that.
Good luck either way.
Edit: I would probably ask which topics the earlier test missed, and whether it's possible to hop on a call with
I would politely decline but I guess it boils down to how badly you want this job.
They’re looking to test for that specific thing, in my experience when this happens it’s usually pretty easy to pass.
Of course if you’re on the fence yourself I also think it’s reasonable to use this as justification for not taking the role. Plaid had me do 2 separate full day on sites and I rejected them for that reason alone.
We do it in 2 where i work. I guess you could say 3 if you count the hr call asking if your interested and eligible to work in the US.
Glass half-full: you still have not been rejected
If it isn't, don't.
There's an opportunity.
And an opportunity cost.
Maybe it is a test of how you handle last minute changes.
Good luck.