Expect questions on SQL versus NoSQL and when to pick each, a simple coding problem like finding the second-largest array element without sorting, and language basics such as exception handling and checked versus unchecked exceptions. Interviewers want textbook-accurate explanations with concrete examples and a correct small program, not competitive-programming depth. The differentiator is whether you can reason about when to use a concept and write clean code without fumbling the basics.
Recruitment process
- Cognitive and technical online assessment
- Coding assessment
- Technical interview on fundamentals and coding
- HR interview on fit and flexibility, then offer
Interview rounds
- Round 1 (60-90 min): cognitive and technical assessment plus coding
- Round 2 (30-45 min): technical round on OOP, DBMS, and a coding problem
- Round 3 (15-30 min): HR round on motivation and mobility
Concept plus when framework
- Explain fundamentals with a concrete example and when you would use them, then write a correct simple program with a stated complexity
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.
