Ho presentato la mia candidatura tramite segnalazione di un dipendente. Ho sostenuto un colloquio presso Shopify
Colloquio
Pair coding.
The question is not an algorithm one but a more real-world question.
Interviewer will ask you to do a brief intro and then he/she will give you his/hers. Then you will be given the question/issue to solve and you can ask questions to clarify it.
Great way to test the candidate how to code in daily work. But only 1 interviewer will be there and he/she will also be in the coding process with you, so I think it could be a little too subjective based on only 1 person's judgement, especially that person might not be working with you on a same team. I think it might be better to have a 3rd person as a pure observer and then the 2 interviewers can have a short discussion after the interview to make it more objective.
Domande di colloquio [1]
Domanda 1
Develop a simple app that do certain stuff by specified inputs/commands.
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.
Domande di colloquio [1]
Domanda 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.
Domande di colloquio [1]
Domanda 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.