Why was I rejected from my JOOR interview?
Let’s say you interview for one of our engineering positions, you feel like you have crushed every little thing, and, yet, … no offer. What happened?
How do we organize our hiring pipeline?
We recognise that applying to any position sucks no matter what, that’s why we are transparent with our processes.
Everything starts with the job description.
We try to include some context about us, our expectations, the future type of work, available locations, and, above all, a comprehensive list of perks, including the compensation range for the position, no mystery, we don’t want you to lose your time.
Once the offer is published, we review internally every applicant looking for potential fits. Surprisingly, many of the candidates can’t qualify for the position: non-viable locations, total lack of experience in the role (not talking about tech stacks), a salad of buzzwords with no rhyme, resumes with lots of typos…
When we find you (😉 a lovely candidate), Naomi will arrange a super brief HR intro screening with you. Don’t be afraid, we ain’t gonna challenge your talent yet, but we need to confirm a few things: a legit interest in the role, you can speak good enough English, and our mutual expectations are aligned. 15mins or less.
99% of people will move quickly from the HR call to the leveling interview. Our goal here is to discover if the candidate can fill our expectations for the role: experience, knowledge, appetite, and, above all, humanity 😅. 30mins.
No kidding, like any other organization, we have our fair share of challenges but we can’t afford to hire a bad teammate regardless of how great (s)he codes.
One or two days after the leveling interview you receive an invite to our final boss… the (remote) onsite.
The onsite
The last stage consists in a series of 3 interviews that we try to run in a row to close our mutual discovery:
- Culture fit: An open talk with 1 or 2 future teammates where they try to answer the question “Would you like to work with this person?” 30mins.
- Technical interview: A longer session with a couple of other people to do some work together. Mostly consists of a few closed technical questions, a brief open design question, and some pairing on a minimalistic exercise. 1hour.
- [Management interview]: Lastly, depending on the role, we will have a last session with one of the managers to close the process. 30mins.
In total a JOOR process for you should no longer than 2h45mins with no take-home assignment 🚀
😴 I crushed it, why no offer?
Maybe you:
- Only talked about frameworks instead of designs decisions.
- Didn’t listen while pairing with your future teammates.
- Coudn’t recognize any mistake from your past.
- Didn’t care about the big picture.
- Navigated the code with no rhyme or reason.
- Copied and pasted until a miracle happens.
- Didn’t show curiosity.
- Didn’t recognize the value of writing and reading.
- Have a gigantic ego. 🙅
or … maybe you actually did a very good job on your interview but somebody else did better.
In the end, the question is not if you are qualified for the role but if you’re the one that, we think, can help us the most.
That’s all folks!
You might be wondering why anybody should care about the hiring philosophy of a mid-sized scale-up.
It’s just a testament of our vision for building the right company, with the right values and, above all, the right people.
Neither you as a candidate nor we as a company are perfect. We may surely lose some incredible candidates along the way 🤷♂. However, if you’re curious, we often have some open positions here👇
