By Avinash Jaiswal
I interviewed Gojek when I was in my final year of engineering. Gojek came to the campus and took four rounds of aptitude tests and interviews and based on these, offered their Product Engineer(now Associate Software Engineer) roles. If you aspire to work with Gojek, this blog might help!
The interview experience
The first round: Coding aptitude
To the entire lot who applied, a set of five questions were asked on topics ranging from string manipulation and number theory and even simple dynamic programming. The level of the questions could be rated between medium and medium easy. It was kind of a race against time where you had to do the maximum number of questions in the provided time of about 45 minutes.
Just know that you need to be clear with the basics of how to implement solutions in your language of choice. The languages offered to us were C++ and Java.
The second round: Code pairing round
Every student who made it to this round was provided with a mentor. Every mentor had around five to six students coding under them. A common question about making a game of warships was provided to everyone. The objective was to design the solution in the most efficient manner and make the code as modular as possible.
The evaluation happened in stages. After someone feels that they have designed a solution, they can call their mentor and discuss with them their progress. Talk about the methods they have implemented and others they are thinking to implement. If the mentor feels like it, can also suggest certain improvements or can ask one to implement a feature beyond the ones specified. This, in turn, is a really good sign as the mentor feels that you understand the code and are now testing your OOPs and problem-solving skills. Getting through the round will be heavily based on your implementation skills and OOPs concepts.
The third round: Technical interview round — I
A panel of two/three interviewers asked questions starting with our development experience and journey so far and then going forward with scenario-based problem statements which one has to solve along with them. The students need to make sure they speak their minds while trying to solve the problem and keep the interviewers informed of the approach. The interviewers may then modify the scenario with new state variables or changed conditions and ask one to modify their solutions as well.
This round could be overwhelming at times, but the key is to believe in your basics and break down the problem into small objectives. It’s a good practice to speak out loud about what your approach to the problem is so that the others in the room are aware of it. This makes a great platform for communication and slowly all the tension eases out and you will be solving the problem along with two people by your side, ready to help.
The fourth round: Technical interview round — II
At our campus, everyone who made it to this round was later announced to be selected. In this round too, you will be made to sit opposite two interviewers and answer their questions related to one’s learnings, hobbies, and academics.
It is a relatively easy round. The interviewers aren’t really looking for answers here, but rather trying to know about the skills you have learnt during your college and then dig into these learnings to ascertain the depth of your knowledge.
Disclosure of results
As I already mentioned, everyone who appeared in the final interview was selected from our campus. It was a really happy day because just after everything was over, Gojek folks took all the selected students with them for a grand lunch. Well, it also happened to be my birthday so a cake was also cut to celebrate the day.
Interacting with our interviewers was extremely comfortable. One thing is for sure: Gojek is always on the lookout for individuals who are willing to create impact at scale.
Check out more blogs from our vault here.
Oh, if you'd like to join us, check out open job positions: