Key Takeaway
Indonesian technical interviews differ sharply by company tier: Tier 1 firms like GoTo and Traveloka run 4-6 rounds with LeetCode-level algorithms and system design, while Tier 2 and Tier 3 companies prioritize a deployed portfolio, practical skills, and STAR-method behavioral answers. Match your prep depth, timeline, and portfolio focus to your target company's tier rather than over-preparing uniformly.
Technical interviews in Indonesia vary wildly by company tier. A Jakarta startup might hire you after a 45-minute coding screen and one behavioral call. GoTo, Traveloka, and international companies doing APAC hiring might run you through five rounds including system design, behavioral, coding, and a technical presentation. Between these extremes is the majority of the market: mid-sized tech companies and consulting firms that have semi-structured processes with inconsistent preparation. I've been through several interview processes while searching for a part-time role, and I've debriefed enough classmates from their experiences to build a practical prep guide for the Indonesian market specifically.
The Indonesian Technical Interview Landscape
Indonesian tech companies have adopted interview practices from global tech to varying degrees. The interview structure by company tier: Tier 1 (GoTo, Traveloka, Shopee, MNCs): 4–6 rounds, includes algorithmic coding (LeetCode-style), system design, behavioral (STAR method), and sometimes a take-home project. These processes can take 4–6 weeks. Tier 2 (funded startups, mid-market tech companies): 2–4 rounds, often a technical phone screen, a coding test (HackerRank or custom), and one or two interviews. These take 2–3 weeks. Tier 3 (consulting firms, software houses, SME tech teams): 1–3 rounds, often a portfolio review, a practical skill test (build something small), and a culture fit interview. These can move in days.
What LeetCode Preparation Is Actually Necessary
LeetCode preparation is necessary if you're targeting Tier 1 companies. GoTo, Traveloka, and international tech companies operating in Indonesia use algorithmic coding screens. The level required is typically LeetCode Medium — not the hard contest problems, but array manipulation, hash tables, basic graph traversal (BFS/DFS), and string processing. For the vast majority of Indonesian tech companies (Tier 2 and 3), LeetCode preparation is not necessary — they test practical coding ability, not computer science fundamentals under contest conditions. Match your preparation to your target company tier.
System Design: What Indonesian Companies Actually Ask
System design questions in Indonesian tech interviews tend to be more applied than the theoretical 'design Twitter' questions you see on YouTube. Common Indonesian-context system design questions: 'How would you design a QRIS payment processing system?' 'How would you structure a multi-tenant SaaS for Indonesian SMEs?' 'Design a ride-matching system for an archipelago country with unreliable network.' These questions test whether you understand both system design principles and Indonesian-specific constraints (payment regulations, data residency, mobile-first user base, patchy internet connectivity in rural areas). Study standard system design patterns first, then apply them to Indonesian context.
Interview Process by Company Tier (Indonesia 2025)
──────────────────────────────────────────────────────────────────
Tier Companies Rounds Includes Timeline
──────────────────────────────────────────────────────────────────
Tier 1 GoTo, Traveloka, 4–6 Algo (LeetCode Med), 4–6 wk
Shopee, MNCs System design, STAR,
Take-home project
Tier 2 Funded startups 2–4 Technical phone screen, 2–3 wk
Mid-market tech HackerRank / custom,
1–2 interviews
Tier 3 Consulting firms, 1–3 Portfolio review, Days
software houses, Practical skill test,
SME tech teams Culture fit
──────────────────────────────────────────────────────────────────
Prep time allocation:
Tier 1 target: 6–8 weeks (add daily LeetCode for last 3 weeks)
Tier 2 target: 2–3 weeks (focus on portfolio + company research)
Tier 3 target: 3–5 days (deployed projects + clear walkthrough)
──────────────────────────────────────────────────────────────────For interviews at Indonesian companies with an ERP, fintech, or enterprise focus, prepare one strong example of handling complex business logic in code — approval workflows, multi-step financial calculations, role-based access control. These companies often care more about your ability to model business rules correctly than your algorithmic performance. A well-designed TypeScript class representing an Indonesian approval hierarchy impresses more than a binary tree inversion.
The Portfolio Review: What Indonesian Interviewers Actually Look At
For Tier 2 and 3 companies — which represents the majority of Indonesian developer jobs — the most important interview preparation is a strong portfolio of real deployed projects. Indonesian interviewers consistently focus on: can I see it working? (deployed URL, not just GitHub); what problem does it solve? (business context, not just technical features); what was hard about building it? (genuine problem-solving discussion, not just a feature walkthrough); and what would you do differently? (shows maturity and learning orientation). A simple but polished deployed Next.js app you can walk through end-to-end beats a complex undeployed project every time.
Behavioral Questions in Indonesian Context
Indonesian technical interviews increasingly include behavioral questions modeled on Western practices, but the cultural context matters. Questions like 'Tell me about a conflict with a colleague' require framing that's direct enough to be informative but respectful enough to fit Indonesian professional norms. The STAR method (Situation, Task, Action, Result) works well here. Prepare 3–5 stories covering: handling a technical mistake (and how you fixed it), collaborating on a team project, self-directed learning of a new skill, and managing competing priorities. These cover 80% of behavioral questions you'll encounter.
# STAR method template for Indonesian tech interviews
STAR_EXAMPLE = {
"question": "Tell me about a time you handled a technical mistake.",
"S_situation": (
"During a client ERP deployment, a misconfigured "
"Nginx proxy caused 502 errors for 20 minutes in production."
),
"T_task": (
"I was on-call and responsible for resolving it without "
"impacting the client's business day further."
),
"A_action": (
"1. Checked Nginx error logs immediately — found upstream "
" config pointing to wrong port after a Docker restart. "
"2. Fixed the upstream block, tested with curl, reloaded Nginx. "
"3. Added a post-deploy health check to GitHub Actions pipeline "
" to catch this class of error automatically going forward."
),
"R_result": (
"Service restored in 8 minutes. Pipeline check now catches "
"proxy misconfigs before they reach production."
),
}
# Tip: prepare 3–5 stories covering: mistake+fix, teamwork,
# self-directed learning, competing priorities.
Indonesian-Specific Technical Interview Topics
Beyond general coding and system design, several technical areas come up specifically in Indonesian context interviews: Indonesian payment systems (QRIS, virtual accounts, midtrans/xendit integration); BPJS calculation and payroll processing (common at companies building HR software); Indonesian tax handling (PPN, PPh withholding) in billing systems; mobile-first and low-bandwidth optimization (Indonesia has significant mobile traffic with variable connectivity); multi-language support with Bahasa Indonesia (i18n implementation); and data residency compliance (UU PDP, OJK regulations for fintech). Having practical knowledge in any of these areas is a differentiator in relevant interviews.
Indonesian tech companies ghost candidates at notably higher rates than companies in more established tech markets. You can complete 3 rounds of interviews and never receive a response. This is a process maturity issue, not a reflection of your candidacy. To protect yourself: after every interview, ask explicitly 'What's the timeline for a decision and how will I hear back?' Follow up exactly once via email or LinkedIn message 5 business days after the stated timeline. If there's still no response, close the mental loop on that opportunity and move on. Don't hold other offers waiting for a company that's ghosting you.
Preparation Timeline and Resources
A realistic interview preparation timeline for Indonesian mid-market tech companies (2–4 weeks): Week 1 — refresh core programming concepts in your primary language (TypeScript/Java/Python), review data structures you haven't used recently; Week 2 — prepare 2–3 deployed project stories you can discuss in depth, practice talking through your portfolio clearly; Week 3 — study the specific company, their tech stack, and their product domain — prepare Indonesian-context questions; Week 4 — practice mock interviews with classmates or via Pramp/interviewing.io. For Tier 1 companies, double this timeline and add 2–3 weeks of daily LeetCode practice.
- Refresh core programming fundamentals — In week one, review core concepts in your primary language (TypeScript, Java, or Python) and revisit data structures you haven't used recently.
- Prepare deployed project stories — In week two, prepare two to three deployed project stories you can discuss in depth and practice walking through your portfolio clearly.
- Research the company and prepare Indonesian-context questions — In week three, study the specific company, its tech stack, and its product domain, then prepare questions that reflect Indonesian market context.
- Run mock interviews — In week four, practice mock interviews with classmates or through platforms like Pramp or interviewing.io to build stamina before the real interview.
After the Interview: Following Up in Indonesian Professional Culture
Post-interview follow-up in the Indonesian professional context requires balancing persistence with respect for hierarchical communication norms. A thank-you email within 24 hours of each interview round is appropriate and appreciated — it's less common from Indonesian candidates than it should be, which makes it a differentiator. Reference a specific technical discussion from the interview to make it personal. When following up on a pending decision, WhatsApp is sometimes more effective than email for Indonesian hiring teams — if you have the recruiter's number and they've texted you through the process, a polite WhatsApp follow-up is culturally appropriate. LinkedIn message is an alternative if you don't have their number.
Update: I've since graduated from Swiss German University and now work full-time as an AI Forward Deployed Engineer at Commsult Indonesia. This post reflects where I was at the time of writing.