J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Gopuff (Redwood City, CA) en déc. 2021
Entretien
I was contacted by a Recruiter after I applied on LinkedIn.
She said she'd call me the following day at 10 AM.
I never got a call from her, after she scheduled me for a call.
This is simply unacceptable. Please have the courtesy to cancel or reschedule a call if you don't have time.
How are you going to compete with Amazon, if you can't even stick to your word and call people back?
Is this how GoPuff treats prospective employees? How are they treated once aboard?
Do they schedule meetings with employees, and then ghost at the last minute, with no follow up?
Be better, GoPuff.
Also, might want to consider a name change. You sound like a vaping company.
Questions d'entretien [1]
Question 1
Do you know how to schedule a call, and then show up?
I had an incredibly positive experience with the interview process. It was remarkably smooth, which I found really impressive. The recruiter played a huge role in making it such a great experience for me. She was incredibly responsive, always available to answer my questions and clarify any doubts. What stood out the most was how she guided me through each step of the process.
J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Gopuff (Boston, MA) en août 2023
Entretien
I applied to their Search and Discovery role and their recruiter reached out to me. The recruiter was actually very knowledgable and knew a lot about the team. I had a call with the recruiter, then the hiring manager (there were actually some technical questions related to data structures here), and two interviews. The two interviews was one with one of their engineers, which was a leetcode type question. The other was with an engineer related to system design.
The system design one we were stuck talking about one aspect regarding how to get an accurate count of the item when users checkout. We actually never got to the API portion or how to partition the data, etc. That was a bit strange given that it is suppose to be related to system design. I think a specific answer was targetted. Overall, I would say I had a positive experience.
Questions d'entretien [1]
Question 1
1. How do you count the number of squares in a grid where each index does or does not have a wall in the top, left, bottom, or right side?
2. How would you design an API or database for a list of go puff products? (This is the part they say I was not well versed at)
J'ai passé un entretien chez Gopuff (New York, NY)
Entretien
Overall pretty standard process. The recruiter was responsive and did good prep for each stage. Most of the interviewers were prepared and knowledgeable. One interviewer was not prepared, didn't understand the question, nor the very basic algorithm I applied, and was standoffish and surly the whole time. I quickly implemented my solution after asking clarification questions. They told me multiple times that my algorithm shouldn't work despite demonstrating with numerous test cases that it did, explaining my implementation and giving the correct time and space complexity. They flat-out told me to make changes to my solution to what they thought would work and I humored them to show that their changes wouldn't pass the numerous test cases I had set up. This was barely a medium leetcode question as well. The interviewer said not to worry and that I did well at the end. I later got rejected in favor of someone who got slightly higher technical marks than me. The process overall was soured by this interviewer, who was going to be on my team. Even if I had been moved to an offer round, there were significant concerns that I would need to have addressed before I would consider joining this team. Again, most people I interacted with varied from pleasant to great, with this one notable exception. I don't want to dissuade others from applying as I think Gopuff could be a great place to work, just relaying my experience.
Questions d'entretien [1]
Question 1
One coding challenge was making a data structure with O(1) lookup with a provided key plus history of each value for each key given a particular timestamp (integer-based).