Gojek tech Software Engineer candidates report a mix of online coding tests, live coding, design rounds and a bar raiser. Formats differ between reports, so prepare algorithms, machine coding, design and project discussion.
$49K
Avg. Base Comp
$64K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe Gojek tech's Software Engineer interviews differently, so prepare for more than one format. Two candidates mention a HackerRank assessment with five problems. One describes array-focused problems and felt the test was the main gate. Another solved three of five, with two hitting time limit errors, on topics including queues, heaps and basic data structures. For this stage, practice optimizing for time limits, not just getting a correct answer.
Live rounds vary. One candidate who received an offer describes a CV screen, an online test, a technical interview, a pair-programming session and a bar raiser with the hiring manager. Another offer-holder describes four rounds: a machine coding problem (a parking lot) with the camera on, a past-projects and low-level design conversation, high-level design, and a senior-management bar raiser. That bar raiser included detailed follow-ups on past decisions plus another HLD or LLD question.
Design topics reported include low-level and high-level design rounds and, in a Senior Software Engineer account, a scalable pizza delivery app. That senior candidate also faced complexity-focused pair-programming questions, such as swapping two values without a temporary variable, and did not advance. Behavioral questions mentioned include mentoring, designing a system and driving process improvements.
Timing is uneven. One candidate describes a gap of up to a month before the final round, and the senior candidate describes a process of about two months. Plan to explain your reasoning aloud, keep project examples ready with trade-offs, and expect that the early coding screen may decide whether you continue.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Gojek tech process.
I applied to Gojek for a Software Engineer role and went through their technical interview process. The first round was a HackerRank assessment with five coding problems. I managed to solve three of them completely, but the other two hit time limit exceeded errors — my solutions worked logically but weren't optimized enough to pass within the constraints. The problems felt standard for online coding platforms, similar to what you'd find on LeetCode or HackerRank's own practice sections, covering topics like queues, heaps, and basic data structures.
After that came a second round conducted through what they called Gorilla Communication — essentially a live technical interview. They asked me to solve stack and queue problems on the spot, very much in the LeetCode medium style. The interviewer was straightforward, and the technical bar felt consistent with the first round. I also had a brief conversation with HR at some point where they asked about my previous roles and experience. Overall, the process was fairly standard for tech interviews: filtering through coding challenges, then a live technical round. I didn't move forward, but the experience was clear-cut in terms of what they were testing for.
Prep tip from this candidate
The TLE issues in the HackerRank round suggest focusing heavily on optimization and complexity analysis for data structure problems, especially with queues and heaps. Practice not just solving problems correctly, but solving them efficiently within tight time constraints.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Gojek tech
Precisely ascertain whether the outcomes of an A/B test, executed to assess the impact of a landing page redesign, exhibit statistical significance.
| Question | |
|---|---|
| Employee Salaries | |
| Top 3 Users | |
| Weighted Keys | |
| User Experience Percentage | |
| P-value to a Layman | |
| Distance Traveled | |
| Size of Joins | |
| Daily Retention Summary | |
| Raining in Seattle | |
| Maximum Profit | |
| Download Facts | |
| Sum to N | |
| Bagging vs Boosting | |
| Retailer Data Warehouse | |
| Google Maps Improvement | |
| Type-ahead Search | |
| Type I and II Errors | |
| The Brackets Problem | |
| Third Purchase | |
| Ride-Sharing App Schema | |
| Average Order Value | |
| Groups of Anagrams | |
| Random Weighted Driver | |
| Binary Tree Conversion | |
| Sort Strings | |
| Production Model Monitoring | |
| Justify a Neural Network | |
| Dijkstra implementation | |
| Hurdles In Data Projects |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report applying through LinkedIn or directly and then hearing from a recruiter. One describes a quick callback, another a short HR call that mostly verified resume details, and a senior candidate was asked about salary expectations. Expect experience-focused questions, though the exact content may vary.
Two candidates describe a HackerRank assessment with five coding problems, covering arrays, queues, heaps and basic data structures. One solved three and hit time limit errors on two, and another believed this stage gated progress. Practice efficient solutions under time pressure rather than only correct ones.
Live coding appears in several accounts. Reported formats include a parking lot machine coding problem solved on camera with follow-up test cases, pair-programming sessions, and stack and queue problems at LeetCode medium level. Interviewers may probe complexity, so explain your approach as you build.
One offer-holder reports a past-projects and low-level design round followed by a high-level design round. A senior candidate was asked to design a pizza delivery app that could scale to a large customer base. Prepare to defend trade-offs and explain architecture and scalability choices in your own project examples.
Two offer-holders describe a final bar raiser, one with the hiring manager and one with senior management. One reports deep follow-ups on work decisions plus another HLD or LLD question. Another reports a gap of up to a month before this round.
