I did the initial coding interview which went well and moved on to the "Growth Path" interview. After that interview, I didn't hear anything back for weeks so I assumed they had ghosted me. But 3 weeks later they contacted me to do a "Life Story" interview and when I checked the interview process tracker, it appears the growth path interview disappeared and got replaced by the life story interview? So it's 3 weeks later and they are essentially asking me to interview for the same round a second time just under a different name. They also didn't have availability for this interview until a few weeks out. I haven't gotten an offer or rejection yet but it seems like the process will take months to get to final rounds.
Overall it makes their interview/recruiting process seem quite unorganized and unprofessional.
Interview questions [1]
Question 1
After reading the careers portal, what's your take on Holding the Tension?
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.
Interview questions [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.
Interview questions [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.