Gojek Engineer Interview Questions
& Process

The first step was a remote screening call with the CTO, lasting about 30 minutes. They explained the company, products, and their 5-step hiring process. Then, I got a coding assignment, a parking lot system problem, due within 48 hours. The requirements were clear and straightforward. After that, I had a code-pairing session, which was about an hour long. It felt rushed because we covered introductions, discussed my submitted solution, refactored it, and even extended the original problem. I'm unsure of the goal of this session, and it was a very negative experience. I haven't heard back since then, even after a follow-up email two weeks later. It seems they ghost candidates they're not interested in, which is unprofessional and disrespectful.

So, the whole thing was like a 4-step process. Before starting, they gave me a choice between a 'Regular' track, which takes about 2-4 weeks, or a 'Fast track' that's done in 10 days. I picked Regular 'cause my weekdays are usually packed. First, I had an initial chat with someone from talent acquisition. Then, I got an offline coding assignment. After that, there was a video call with Ajey Gore, who's the group CTO. The last step was a code-pairing session, followed by a technical interview, and then a final interview with Sidu Ponnappa, Head of Data & Engineering. Everything felt super smooth and fair. They seemed to be totally focused on my technical skills, what I can do, and my experience. A lot of the questions and what we talked about felt like stuff you'd actually deal with in a real production setup. They gave honest and direct feedback, which I really appreciate in a company culture – none of that sugar-coated stuff that makes you think you're ready when you're not. In the final interview, they also gave me a heads-up on what to expect if I joined, like the work environment, how fast things move, and how complex the work is, plus what they'd expect from me. The HR folks were really friendly and professional, always on time or letting me know if there were delays, and they followed up well.

The interview process started with a take-home assignment that I had to finish in two days, focusing on things like OOPS, TDD, and GIT. After submitting it, I was invited for face-to-face interviews. The first round involved explaining my assignment code and test cases. Then, I was asked to complete pending test cases and explain them. The problem was extended to include multiple parking areas, and I had to modify the code accordingly. After this, the interview ended, and I was informed by HR that the feedback was negative. I had a feedback session with the same interviewer, who mentioned that my skills didn't match the requirements, specifically regarding TDD adherence, test method naming, and code modification during the extension phase. I felt disappointed because these expectations weren't clearly stated upfront, and I had spent significant time on the assignment and travel.