J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Shopify (Toronto, ON) en juin 2020
Entretien
The process was:
- phone screen with recruiter
- Life Story interview where they talk about your background/experiences
- 1 hour live coding challenge with a developer
- final stage was 2 pair programming interviews and a technical deep dive interview
For all of the coding interviews you can choose to use any programming language.
In the tech deep dive they ask you to explain in depth one of the most complex projects you completed. I found that preparing by drawing a diagram of the project I want to talk about really helped in the tech deep dive.
Overall the process was very smooth and every interviewer was polite and engaged in the interview.
Questions d'entretien [1]
Question 1
Tell us about one of your most challenging projects?
typical interview process, one round with hr. followed by a 75 min coding interview pair programming with one of the engineers. In the coding interview it was encouraged to use ai.
Questions d'entretien [1]
Question 1
create a autocomplete system for search based on a list of search frequencies.
There was a first round with hr followed by a 1hour interview, use of AI was encouraged. Interviewer was not very knowledgeable and I had to discover a solution that she understands
The interview was intense and definitely exceeded my expectations. The technical rounds were particularly challenging, but I felt prepared. One of the system design questions was about creating a webhook delivery system with various complexities, and I was relieved because I had explored that exact topic on PracHub just days before. After tackling some coding problems, I faced some behavioral questions that tested my thought process. Overall, the experience was demanding, but I was thrilled to receive an offer, which I happily accepted.
Questions d'entretien [1]
Question 1
Design a webhook delivery system that retries on failure with exponential backoff. Cover idempotency, ordering guarantees, dead-letter queues, and how you'd handle a downstream consumer that's been offline for hours.