Gojek Software Engineer Interview Questions
& Process

The interview included a machine coding round where I had to complete a ToDo in a basic iOS app. This tested my knowledge of iOS concepts like Architecture, GCD, memory management, networking calls, UI kit, activity lifecycle, and push notifications. There was also a behavioral round where we discussed challenges faced, recent projects, and the project lifecycle, focusing on how I communicate with peers from contract creation to project delivery and final QA.

Applied through a referral. The process kicked off quickly with a recruiter reaching out the same afternoon I applied. An HR interview was scheduled for the next day, followed by the first of four technical interviews later that week. The technical interviews seemed to operate on an elimination basis, with immediate contact for the next round upon passing, and notification from the recruiter if not. The first technical round was a pair programming exercise where I had to complete existing methods in a master file, using a parking lot problem as the task. My advice for this is to use Test-Driven Development (TDD) and aim for good unit test coverage. I passed this and was informed the next technical interview, scheduled for the following day (Saturday - which I appreciated them doing on a weekend), would focus on past projects. For this second technical interview, I presented a project I had worked on at my current company. The interviewer probed deeply, asking hypothetical 'what if' scenarios about service downtime and justifications for technology choices, including comparisons between specific technologies like RabbitMQ and Kafka. After passing, I was scheduled for the third technical interview an hour later. This round was a system design task, specifically designing a movie ticket booking system. The interviewer was very collaborative, making it feel like a team discussion. I passed this too and had my fourth interview scheduled within the hour. The final interview was with the Engineering Manager (the 'bar raiser') and focused on work culture and culture fit. I received an offer the following Monday. Overall, the interview experience was very positive, with friendly interviewers and a conversational approach.

The interview process was two rounds. The first was a machine coding round where I had to solve a problem similar to LRU cache. The second round was about my current project and potential improvements. I must say the interviewing experience and skills of the interviewers could be better. All my interviews finished early, and the interviewers didn't ask many follow-up questions. It felt like they weren't really trying to assess me properly. Maybe instead of rejecting candidates, the company should focus on improving the interviewers' ability to ask relevant questions and clearly communicate what they expect. If this rejection is for other business reasons, it's a really bad way to treat candidates. My colleagues warned me it's a tough process and often rejects people without good reason, and they were right. I absolutely do not recommend this company. It takes them weeks to conduct just two interviews and then give surprising results.