Envié una solicitud electrónica. Acudí a una entrevista en Kitman Labs
Entrevista
There are 4 rounds: phone screen, conversation, 3 part panel, and a final behavioral.
The process is really slow but the people are nice. Don’t expect to hear back the next day, or even that week.
Preguntas de entrevista [1]
Pregunta 1
What I like is that the questions are based on real life. If you can do basic enterprise web development you can do this. Fetch data, transpose it, and render it.
Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Kitman Labs en ene 2023
Entrevista
A very lengthy process. Not the most pleasant, could be reduced to make it less tedious by having a simple one stage chat. Also I was rejected for something they already knew from my CV so seemed kind of pointless.
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Kitman Labs (Dublín, Dublín) en ago 2018
Entrevista
The interview consists of two stages:
- Informal Coffee
Met one of the tech lead for a coffee. It was an informal discussion around what you and they do and generally just chatting. This was great, got to dig into details and how they work and what they do and don't like in their codebase.
- On-site interview.
1 - Coding Challenge, it was a sports related use case. It was an interesting challenge, you do some pair programming, thinking out loud and generally talking about your solution.
2 - System Design interview, discussing how you would implement certain features on the front-end, how API would look and what the models may look like.
3 - Meeting with Designers - This may be specific to front-end positions, but there was an exercise where you are given wireframes on a page and you have to discuss them with the designers. Basically digging into what the wireframes are about and questions would you need to ask to figure out their intended use.
The interview went very well, I had the coding challenge done very quickly they give you about 2hrs to do it but you can it in 45 minutes. I was surprised when I got a 'No' they said it was close but they wanted somebody with more product experience. While I think that is a valid reason for no that could have been identified earlier in the interview as they could have spotted that after the first interview or my CV instead of doing a very long interview and getting a no.
Overall the interview was a good experience and I wish the guys best of luck!
Preguntas de entrevista [1]
Pregunta 1
Coding Challenge, System Design/Architecture discussion, design questions.