Solicité el puesto a través de la recomendación de un empleado. El proceso duró 2 semanas. Acudí a una entrevista en Hopper (Montreal, QC) en jun 2018
Entrevista
My interview process went like this:
1. Online coding portion (1h30 time limit)
2. Technical interview via Hangout with live coding (1h)
3. Onsite technical interview with 4 different people with lunch (5h with harder problems)
4. Talk with the CTO via Hangout to discuss expectations and what my role will be (short and long term)
---
The technical part of the process is hard (similar to a Google interview process) but it's understandable because every one seem very passionate and good at what they are doing. I suggest people to review their algorithms and optimization before starting the process (especially if you're starting to have grey hair). I also suggest to code in the language you're the most comfortable with.
Things I really appreciated:
- Tech people are very knowledgeable and so passionate. It feels like they are really proud of the things they are building.
- Different range of personalities, from your typical introvert developer to a very outgoing programmer. It also seem like it was a group of friends working together.
- The CTO has a really amazing vision for the product and it looks like he still codes when he has time.
- The office is a nice blend of modern on top of an older building.
- Seems like people are doing activities outside of the office (run, yoga, climbing...).
Things that could be improved:
- Seems like everyone had the same way of interviewing: ~10m talking about themselves, ~10m asking about what you do or projects, the rest is technical questions followed by any questions if there is time left. Would be nice if it was a bit different for example the first one ask me about school, the second one about my current work, the third one about personal projects... etc
- Maybe show a list of language we can use during the interview. I wasn't really sure so I chose one from the stack used there (even if I didn't use it for a while).
In summary, I really enjoyed the process and it got me to really know the people there.
Preguntas de entrevista [1]
Pregunta 1
Tell me something you're really proud of (technically).
Full day of remote interviews, 4-5 sessions each with data structures programming. One behavioral round with hiring manager towards the end. Process started with a technical screen consisting of an online programming assessment.
Preguntas de entrevista [1]
Pregunta 1
What would your former manager/colleagues say about you.
Envié una solicitud electrónica. Acudí a una entrevista en Hopper
Entrevista
The company seemed really pretentious with them trying so hard to emulate Amazon.
Got rejected after a screening round which was an LLD round. Who screens on the basis of LLD though? The interviewer was not engaged throughout the process and was doing some of his own work. I had to say his name multiple times to bring him back to the conversation.
External recruiter reached out, and afterwards I chatted with a technical recruiter from Hopper. The written communication has been great, polite and timely. The initial chat was going fine until we started talking about the rest of the interview process. The recruiter explained to me that the next step was leetcode style and they used to give 2 days for the challenge to be completed but the women engineers complained that it was too short so they decided to make it a week. I got offended by this specification but still finished the interview as if I wasn’t. Did not continue the process afterwards.
Preguntas de entrevista [1]
Pregunta 1
Which technologies I’ve worked with and my education background