Expect a coding round on medium to hard DSA (arrays, strings, hashmaps, trees, graphs) and a machine-coding or LLD round where you build something like a policy-pricing engine, claims workflow, or notification service with clean, extensible OOP. Because Acko owns the full insurance stack from quote to claim, interviewers ask how you model state machines, handle idempotent events, and keep data consistent across policy and claims services. Code quality, testability, and design clarity carry real weight here.
Recruitment process
- Resume screen: backend or full-stack depth; referrals improve visibility
- Online coding round: medium to hard DSA, roughly 60 to 90 minutes
- Machine coding or low-level design: build a clean system in about 90 minutes
- Technical deep-dive on projects and design and consistency reasoning
- Hiring manager and culture round: ownership, communication, and values fit
Interview rounds
- Coding Round (60 to 90 min): Medium to hard DSA on arrays, strings, hashmaps, trees, and graphs. The main early filter
- Machine Coding or LLD (90 min): Build a working system such as a policy-pricing engine or claims workflow with clean, extensible OOP and edge-case handling
- Technical Deep-Dive (45 to 60 min): Walk through a past project and reason about state machines, idempotent events, and cross-service consistency
- Hiring Manager and Culture (45 min): Ownership stories, collaboration, and alignment with Acko's digital-first culture
Domain-driven LLD framework
- Model the insurance state machine, then clean extensible OOP, then idempotent events and consistency, then tests.
Practice questions
- 01Practise
Reverse a linked list in O(1) extra space. Then explain when you'd use this in production.
Standard - 02Practise
What is the difference between a class and an object? Give an example.
Warm-upTCS Ninja/Digital tracks lean heavily on CS fundamentals: OOP, OS, DBMS, SQL basics. Expect rapid-fire Q's, not deep dives. - 03Practise
Write a SQL query to find the second-highest salary in a department.
Warm-up - 04Practise
What is normalisation in databases? When would you de-normalise?
Warm-up - 05Practise
What's the difference between a stack and a queue? Give a real-world use case for each.
Warm-up - 06Practise
Given a stream of integers, design a data structure that returns the median in O(log n).
Intense - 07Practise
You have a service that's slow only on Tuesdays. Walk me through how you'd debug.
StandardGoogleyness: structured debugging, hypothesis-driven, instrumentation-first. - 08Practise
Here's 200 lines of payment-processing code with several intentional bugs. Find them and explain the production impact of each.
IntenseStripe's signature 'bug bash' round. Off-by-one, race conditions, wrong error handling, edge cases in money math. Communicating impact > finding all bugs. - 09Practise
Explain webhooks vs. polling for a developer who has never built a payment integration. You have 4 sentences.
StandardStripe values writing clarity above almost everything. Length-constrained explanation tests prioritisation of ideas. - 10Practise
Walk me through Razorpay's fraud-detection model. How would you reduce false positives without increasing chargeback losses?
IntenseRazorpay ML rounds tie model decisions to ₹ impact, chargeback cost vs. blocked-good-txn cost. Pure ML answers without business framing fail.
