Tokopedia Software Engineer interviews reported by candidates combine an online coding test, technical rounds on algorithms and project depth, a managerial or culture conversation, and an HR stage.
$20K
Avg. Base Comp
$31K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Candidates describe a Tokopedia Software Engineer process that opens with a screen and then moves into technical conversations. Two of the three reports begin with a HackerRank-style assessment. One of them describes three data structures and algorithms questions to be solved briskly. The third candidate, who interviewed for a web platform role, instead started with a mini project submission.
The technical rounds differ by team. One candidate reports two online technical rounds that focused on algorithms and data structures rather than syntax. They describe live coding with easy, medium and hard problems back to back, plus questions on operating systems, networks and building a feature from scratch. A web platform candidate reports questions on JavaScript, CSS, React, security, performance and server-side versus client-side rendering, along with a system design exercise on API and data structure choices.
Another candidate reports that interviewers went deep into their CV and portfolio, asking about the projects they built and why they chose particular technologies. Be ready to explain your own decisions clearly, and to describe how you would handle a half-finished task when an urgent one arrives.
Late stages vary. One candidate reports a managerial round and then an HR round before an offer. Another passed every technical round but was rejected at the final stage without a clear reason. One candidate reports a total of three to four weeks, and another reports feedback between rounds within one to four days.
Synthesized from 4 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 Tokopedia process.
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 Tokopedia
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Delivery Estimate Model | |
| Google Maps Improvement | |
| Search Algorithm Recall | |
| Green Dot | |
| International e-Commerce Warehouse | |
| Uber Eats Customer Experience | |
| Unified Inbox | |
| Underpricing Algorithm | |
| Justify a Neural Network | |
| Processing Large CSV | |
| SFTP Pipeline | |
| Your Strengths and Weaknesses | |
| Game Feature Home | |
| Meta in an Emerging Market | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Top 3 Users | |
| Comments Histogram | |
| Random SQL Sample | |
| Raining in Seattle | |
| Flight Records | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates report a HackerRank challenge, and one describes about three data structures and algorithms questions to be solved briskly. One web platform candidate instead submitted a mini project and heard back by email within a few days. Practice timed array and string problems, and keep any project submission tidy and explainable.
After the first screen, candidates report an HR conversation covering basics, motivation and next steps. One candidate says the call came after passing the HackerRank test. Expect to explain why you want the role and what you know about it, though the exact questions may differ by team.
Candidates report between one and three technical interviews. One describes online rounds on algorithms, live coding of increasing difficulty, operating systems and networks. Another was asked about JavaScript, CSS, React, security, performance and rendering approaches, and one reports a deep dive into their CV and projects. Content likely depends on the team and role.
Some candidates report scenario-based case studies, an API and data structure design exercise, or a managerial round about collaboration and system design. Prepare to explain tradeoffs, how you would build a feature end to end, and how you would prioritize an urgent task that interrupts your current work.
Candidates report a culture and behavioral interview or a final HR round covering background, motivation and team dynamics. Outcomes differ: two candidates report offers, while another passed the technical rounds and was rejected at the final stage without a clear explanation.
