Candidatei-me online. O processo levou 1 semana. Fui entrevistado pela Qdrant Solutions (Amsterdã) em set. de 2025
Entrevista
The interview process was not long, a call with the recruiter followed by an interview with the hiring manager, and a take-home challenge,
The process was seamless, but scheduling was somewhat unclear.
The interview with the hiring manager was good,
I took the home challenge and went to the next step, an interview with two engineering managers, which I didn't enjoy.
One of the managers constantly interrupted me while I was talking and always gave me comments like, 'This is not enough,' or 'This thing is missing,' etc.
I haven't heard back from them after the challenge interview.
Perguntas de entrevista [1]
Pergunta 1
The challenge was about designing a DBaaS offering for Qdrant.
I got the challenge description in 2/3 phrases in an email,
with emphasis to not work on that for more than 3/4 hours, and this:
`You do not need to focus on all problem areas; solving 1-2 very well and having a rough idea for the rest is absolutely fine!`
Fui entrevistado pela Qdrant Solutions em abr. de 2024
Entrevista
I was screened by the VP of Engineering and then sent an architecture challenge that asked me to design a dbaas with scalable instances of the Qdrant engine. I spent about 2-3 hours thinking of solutions and drawing out diagrams, then had a video call with one of their Senior Engineers to discuss my approach. It was a fun conversation and seemed to go well. I had my interview at 7am on a Tuesday (time zones) and they said they'd get back to me by the end of the week. Two weeks later, I had to directly email that engineer to ask for an update. They'd gone with someone who was a better fit and failed to update me. Very unprofessional.
Perguntas de entrevista [1]
Pergunta 1
The cloud / dbaas we are building for our Qdrant Neural Search engine. Focusing on the API / Console part is perfectly fine as well.
