Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela env zero (Berlim) em nov. de 2024
Entrevista
Pros:
- Thorough technical evaluation process
- Professional interviewers (R&D lead and senior developer)
- Clear communication during the interview stages
Cons:
- Home assignment typically takes 2 weeks but was required within 1 week
- No response to feedback request after rejection
- Time-intensive process (multi-stage interviews + home assignment + live coding) without constructive feedback
Interview process included:
1. Initial interview with R&D lead
2. Technical interview with senior developer
3. Home assignment (1 week timeframe)
4. 1.5-hour live coding session reviewing and extending the assignment
Advice to Management:
Consider providing basic feedback to candidates who have invested significant time in your interview process, especially when explicitly requested. This helps maintain good relationships with the developer community and enhances your employer brand.
Perguntas de entrevista [1]
Pergunta 1
How would you approach reviewing a PR in an open source repository?
Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela env zero (Tel Aviv-Yafo) em out. de 2024
Entrevista
I was interviewed during October 2024.
These were the phase:
1. A conversation with the technical recruiter (the usual conversation)
2. A screening interview with a developer, where you're being asked about technologies in general. I was asked about NodeJS and why it is considered non-blocking although it is single threaded.
3. An interview with a team lead. Most of the interview was about React questions, some SQL vs No-SQL questions, I needed to present an architecture of a project I did and lastly, a coding question. I needed to program a path finder in a matrix, and reach from start point to end point, only through cells which had the value 1 and it can't be done diagonally. I didn't know that the answer was DFS, but passed anyway.
4. An interview with an engineering manager, This time he deep-dived into NodeJS, asking about pros and cons, when we are not going to use it, why is it important to test our code, questions around mongoDB (like when are we going to favor embedding vs referencing and vv). And finally, I needed to design a URL shortener system. The difficult part was asking questions like how would you make money out of it and which LB technology would you use.
I didn't pass the last technical interview, but afaik the next one would be with the CEO.
Perguntas de entrevista [3]
Pergunta 1
I was asked about NodeJS and why it is considered non-blocking although it is single threaded.
Most of the interview was about React questions, some SQL vs No-SQL questions, I needed to present an architecture of a project I did and lastly, a coding question. I needed to program a path finder in a matrix, and reach from start point to end point, only through cells which had the value 1 and it can't be done diagonally. I didn't know that the answer was DFS, but passed anyway.
NodeJS, asking about pros and cons, when we are not going to use it, why is it important to test our code, questions around mongoDB (like when are we going to favor embedding vs referencing and vv). And finally, I needed to design a URL shortener system.
phone interview and zoom. Even if this was quiet early stage of process it wasn't the best experience I had compared to other companies.
good luck to whom ever applies.