J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Narvar (Vancouver, BC) en oct. 2024
Entretien
The overall interview process was well-organized and structured. It started with a conversation with a tech recruiter, followed by an interview with the hiring manager, then a technical loop consisting of three interviews, and finally, a cultural fit assessment.
Questions d'entretien [2]
Question 1
The coding interview consisted of two LeetCode-style questions, starting with an easy one and progressing to a medium-difficulty question. The 30-minute time frame was sufficient to complete both problems.
J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Narvar
Entretien
Narvar scenario based question in Golang, interview was for 2 hours (1h coding, 1h review).
Panelist (Senior with 5+ in the company, had no idea of what they were doing in the company) didn't have any patience, tried to squeeze 1h interview within 40 minutes, had rigid answers in mind, gave no choice to discuss the solution, expected over engineering for simple problems.
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Narvar en avr. 2022
Entretien
1) Screening call with HR
2) Tech interview: some JavaScript task, no any math theory is required, but task is pretty complex due to time limitation, so you need to be really fast to complete it in time.
3) Discussion with manager, kind of behavioural interview
4) Design interview (white board)
5) One more discussion with manager
Questions d'entretien [1]
Question 1
The most difficult is first tech interview, where you have only 1 hour to complete pretty difficult task. You'll need to work a lot with arrays, aggregate data, re-structure it and use properly to get required info. Also, the description of task is not so simple to understand after first read. You really need spend some time to understand requirements and clarify them with interviewer. I spend about 20min just reading it and discussing with interviewer before I wrote at least one useful line of code.
Second tech interview was pretty straight forward, if you know how to act during design interviews. There were no any requirements, you needed to create requirements yourself for application, that you also choose yourself.
