Table of Contents

How Indian Tech Interviews Are Structured: A Master Overview

The interview process for software engineering roles in India is not uniform across companies. Google’s loop looks nothing like TCS’s. Razorpay’s rounds are designed differently from Infosys’s. Understanding the structure before you start preparing prevents a common mistake: preparing for the wrong kind of interview for the company you are targeting.

At the highest level, Indian tech interviews fall into two distinct philosophies:

Product company interviews (Google, Amazon, Microsoft, Flipkart, Swiggy, Razorpay, PhonePe, CRED, and similar) evaluate deep technical competence, problem-solving under time pressure, system design ability, and behavioural signals tied to engineering values. These interviews have lower pass rates, require longer preparation, and are primarily evaluated by engineers rather than HR.

Service company interviews (TCS, Infosys, Wipro, HCL, Cognizant, and similar) evaluate fundamental aptitude (logical reasoning, quantitative ability, verbal ability), basic programming ability, and HR fit. The bar for technical depth is lower, the volume of hiring is much higher, and campus recruitment accounts for the majority of intake. Lateral hiring at service companies adds a technical component but rarely reaches product company depth.

Complete Software Engineer Interview Roadmap: Company-Wise Preparation Strategy for Google, Amazon, Microsoft, Flipkart, Razorpay, Infosys & TCS with Round-by-Round Breakdown Complete Software Engineer Interview Roadmap — Company-Wise Preparation Strategy for Google, Amazon, Microsoft, Flipkart, Razorpay, Infosys and TCS with Round-by-Round Breakdown

The Standard Product Company Interview Loop

Most product companies in India use a 4-6 round interview structure for SDE-2 and above:

Round 1 - Online Assessment (OA) / Coding Screen: A timed coding assessment on an online platform (HackerRank, HackerEarth, Codility, or a proprietary platform). Typically 60-90 minutes with 2-3 problems ranging from easy to medium-hard difficulty. This is a screening filter - the pass rate varies from 30% to 70% depending on the company’s volume.

Round 2 - Technical Phone Screen: A 45-60 minute video call with a senior engineer. 1-2 coding problems (LeetCode medium difficulty), sometimes with a brief system design or object-oriented design discussion at the SDE-2 level and above. Evaluated on correctness, code quality, time and space complexity analysis, and communication.

Round 3 - Technical Round 1 (DSA Focus): In-depth coding round with 2-3 problems. Expect follow-up questions after your solution: “Can you optimise this further?” “What happens if the input has duplicates?” “What is the time complexity of this approach?” The interviewer is evaluating not just whether you solve the problem but how you think about it.

Round 4 - Technical Round 2 (System Design / LLD): A 45-60 minute system design interview for SDE-2 and above. Design a large-scale system (URL shortener, notification service, ride-sharing backend, etc.) or a detailed low-level design (class design for a parking lot, chess game, or library system). Evaluated on requirements gathering, component design, trade-off discussion, and communication.

Round 5 - Hiring Manager Round: A discussion with the engineering manager or hiring manager. May include technical questions but is predominantly focused on motivation, cultural fit, career goals, past experience and impact, and how you handle ambiguity and conflict. At some companies this is combined with a bar-raiser round.

Round 6 - Bar Raiser / Cross-Functional Round (Amazon and some others): A dedicated round by a trained interviewer who is not part of the hiring team and has no vested interest in the hire. Designed to maintain the bar across the organisation. At Amazon, this person can veto a hire even if all other interviewers are positive.

The Standard Service Company Interview Loop

Service company processes are more standardised:

Stage 1 - Online Assessment / Aptitude Test: Logical reasoning, quantitative aptitude, verbal ability, basic coding (fill-in-the-blank or multi-choice coding questions). Some companies also include an English communication assessment.

Stage 2 - Technical Interview: 30-60 minutes covering fundamentals - data structures, algorithms at a basic level, object-oriented programming concepts, database basics (SQL queries), operating system concepts, and questions about your resume and projects.

Stage 3 - HR Interview: Motivation questions (“Why this company?”), self-introduction, career goals, salary expectations, location preferences, and general communication assessment. This is also the round where offer details are discussed.

Google India Interview: Round-by-Round Preparation Guide

Google’s India offices (Bengaluru and Hyderabad) conduct interviews that are largely identical in structure and difficulty to Google’s global interview process. This is a deliberate standardisation - Google’s “Hiring Committee” model means that a hire at Google India must pass the same quality bar as a hire at Google’s Mountain View headquarters.

What Google Actually Evaluates

Google’s interviewers score candidates on four dimensions after each round:

General Cognitive Ability (GCA): How well do you think through novel problems? Can you break down complexity into tractable subproblems? Do you spot edge cases? Do you consider multiple approaches before choosing one? GCA is evaluated primarily through the coding rounds but also informs how interviewers score the system design and behavioural rounds.

Coding Ability: Can you translate your thinking into clean, correct, efficient code? Code does not need to be perfect but must be clearly readable, logically structured, and free of major bugs. Google interviewers specifically note: good variable names, no unnecessary complexity, clean edge case handling.

System Design (SDE-2 and above): Can you design large, scalable systems? Do you understand distributed systems trade-offs? Can you communicate architectural decisions clearly?

Googleyness: This is Google’s behavioural dimension - evaluated on cultural alignment, intellectual humility, comfort with ambiguity, and collaborative work style. Not a separate round but scored by every interviewer across all rounds.

Round 1 and 2: Coding Rounds

Google’s coding rounds are 45 minutes each, conducted on Google Docs (not a coding environment - no syntax highlighting, no auto-complete, no compiler). This is intentional: Google wants to see how you code in a plain text environment, not how well you use IDE features.

Expected difficulty: LeetCode Medium is the baseline. Expect at least one problem that is harder than a typical medium - a problem that requires combining multiple data structures, applying a non-obvious algorithm, or thinking about time complexity carefully.

Preparation focus:

  • Master the 15 core DSA patterns (two pointers, sliding window, BFS/DFS, dynamic programming, binary search, heap/priority queue, graph algorithms, tree traversals, backtracking, divide and conquer, union-find, monotonic stack, trie, topological sort, bit manipulation)
  • Practise coding without an IDE: write your solution in a plain text editor or on paper before running it
  • Practise narrating your approach: “I’m thinking of a sliding window here because the problem has a contiguous subarray constraint and we want to optimise for O(n) time…”
  • Practise complexity analysis until it is immediate: state the time and space complexity of every solution you write during practice

Common Google coding topics: Graph traversal and shortest paths, tree problems (lowest common ancestor, diameter, serialisation), dynamic programming (2D DP, string DP, interval DP), array and string manipulation, design problems with data structure choices (design Twitter feed, LRU cache implementation).

Round 3: System Design (SDE-2 and above)

Google’s system design round is 45-60 minutes. The problems are typically large-scale consumer products: design YouTube, design Google Maps, design the Autocomplete for Google Search, design Google Drive, design a distributed rate limiter.

Google’s system design evaluation is stricter than most companies on distributed systems depth. Interviewers expect you to discuss: consistent hashing, CAP theorem and its implications for your design, data replication strategies, and the specific failure modes of each component.

The aspects that differentiate strong candidates at Google system design: handling the “celebrity problem” (millions of followers for a single account), designing for geographic distribution (multi-region latency and consistency), discussing specific numbers (not vague “we’ll scale horizontally” but “at 1 billion requests per day we need approximately 12,000 RPS, which a single well-configured server can handle - but for reliability we want at least 3 behind a load balancer”).

Round 4: Behavioural Round (Googleyness and Leadership)

Google’s Googleyness round uses open-ended questions that probe for: intellectual humility (“Tell me about a time you were wrong about a technical decision”), comfort with ambiguity (“Tell me about a project where requirements kept changing mid-development”), collaborative conflict resolution (“Tell me about a time you disagreed with a colleague’s technical approach”), and genuine intellectual curiosity (“What technical problem are you most excited about right now?”).

Prepare 6-8 STAR (Situation, Task, Action, Result) stories drawn from your actual work experience, covering: a technical failure and what you learned, a time you influenced without authority, a time you had to make a decision with incomplete information, a time you mentored someone, your proudest technical achievement, and a situation where you had to push back on a product or management decision.

Google Interview Preparation Timeline

8-10 weeks minimum for a candidate with 3+ years of engineering experience and basic DSA familiarity. Allocate roughly: weeks 1-4 for DSA fundamentals and pattern mastery (LeetCode 100-150 problems), weeks 5-7 for system design study (DDIA + ByteByteGo problems), week 8 for mock interviews and behavioural story preparation.

Amazon India Interview: Leadership Principles + Technical Rounds

Amazon’s interview structure is unique in the product company world because of the equal weight given to Leadership Principles (LP) in every single round, not just the behavioural round. An Amazon interview where a candidate solves all coding problems correctly but fails to demonstrate LP alignment is likely to result in rejection. Understanding and internalising the LP framework is non-negotiable for Amazon preparation.

Amazon’s Leadership Principles

Amazon’s 16 Leadership Principles are not a soft-skills checklist - they are the explicit framework Amazon uses to make every hiring, promotion, and business decision. Every interviewer in an Amazon loop is assigned 1-2 LPs to specifically evaluate. Every behavioural question is tied to a specific LP. Every answer is scored against LP criteria.

The most commonly evaluated LPs in engineering interviews:

Customer Obsession: Do you think about the end user impact of your technical decisions? Can you give examples of times you went beyond the immediate technical task to consider user experience?

Dive Deep: Do you go deep into technical detail when needed? Can you explain the internals of systems you have built? Do you know the numbers (latency, throughput, failure rates) of your production systems?

Bias for Action: Do you make decisions and move forward with incomplete information? Can you give examples of taking calculated risks to ship faster?

Ownership: Do you own problems beyond your immediate role? Do you see issues outside your scope and address them anyway? Do you own your failures and fix them?

Invent and Simplify: Have you found simpler solutions to complex problems? Have you introduced new approaches that others on your team adopted?

Insist on the Highest Standards: Do you maintain quality under pressure? Do you push back on poor technical decisions? Can you give examples of raising quality standards on your team?

The Amazon Interview Loop Structure

Amazon’s standard SDE-2 loop consists of 4-5 rounds (typically conducted in a single day on-site or across back-to-back video calls):

Round 1 - Online Assessment: Two coding problems (45-90 minutes), typically one medium and one medium-hard, on a HackerRank-style platform. Some OAs also include a work simulation component (multi-choice questions about work situations mapped to LP scenarios).

Round 2 - Coding Round 1: 1-2 coding problems + LP questions. The LP questions in coding rounds typically ask about past experiences: “Tell me about a time you had to make a technical decision under time pressure” (Bias for Action), “Describe a time you found a simpler solution to a problem your team had accepted as complex” (Invent and Simplify).

Round 3 - Coding Round 2: 1-2 coding problems + more LP questions targeting different LPs than round 2.

Round 4 - System Design / HLD: At SDE-2 and above. Design a system relevant to Amazon’s domain (order management system, notification platform, product recommendation system, delivery tracking system). Amazon system design expects you to think about distributed systems at the scale Amazon actually operates - global distribution, millions of TPS, extreme availability requirements.

Round 5 - Bar Raiser: The most demanding round for LP evaluation. The Bar Raiser is a trained Amazon interviewer from a different team who has no relationship to the hiring team. They focus heavily on LP depth and consistency across your answers, probing for specificity and authenticity. A common Bar Raiser technique: ask the same LP question multiple times in different ways to check consistency. “Earlier you mentioned Ownership - can you give me another example?” If your examples run dry or become inconsistent, it is a red flag.

Preparing Amazon LP Answers with STAR

For Amazon interviews, each STAR story must include:

  • Specific numbers: Not “we improved performance significantly” but “we reduced p99 latency from 800ms to 150ms”
  • Your specific role: Not “the team built…” but “I designed the caching layer, which was the core of the optimisation”
  • The LP signal: Each story should clearly demonstrate the LP it is meant to address
  • Honest reflection on failures: Amazon interviewers are specifically trained to probe for situations where things went wrong. Stories that have no failure, conflict, or difficulty are viewed with scepticism.

Prepare a minimum of 12-15 distinct STAR stories (2 per LP for the top 6-8 LPs). Stories should not repeat. If an interviewer asks a follow-up on an LP you already answered in a previous round with your best story, you need a different story ready.

Microsoft India Interview: Coding, Design & Hiring Manager Rounds

Microsoft’s India engineering centres (Hyderabad primarily, with Bengaluru growing) conduct interviews that are rigorous but generally considered slightly more collaborative in tone than Google or Amazon. Microsoft interviewers often allow more hints, are more likely to engage in a discussion about trade-offs rather than expecting a candidate to independently produce the optimal solution, and weight coding correctness and technical communication roughly equally.

Microsoft Interview Structure

Round 1 - Phone Screen: 30-45 minutes. 1 coding problem, typically LeetCode medium. May include brief discussion of a project from your resume. This round is often conducted by a recruiter plus a junior engineer and is the lowest bar in the loop.

Round 2 - Coding Round 1: 45-60 minutes. 2 coding problems. Microsoft tends toward tree, graph, and string problems. The interviewer expects you to code a working solution, test it with examples, and discuss time/space complexity. Microsoft interviewers specifically note: do you test your own code? Do you think of edge cases before being prompted?

Round 3 - Coding Round 2: Similar structure. May include an object-oriented design question at SDE-2 level: design a parking lot, design a vending machine, design an elevator controller.

Round 4 - System Design: For SDE-2 and above. Microsoft system design tends to be grounded in practical scalability rather than theoretical distributed systems purity. Common questions: design a URL shortener, design a chat application, design an email client at scale, design a search autocomplete. Microsoft interviewers engage actively in the design discussion - treat it as a collaborative problem-solving session rather than a solo presentation.

Round 5 - Hiring Manager / As-Appropriate Round: The hiring manager round at Microsoft is substantially a cultural fit and motivation discussion. Key questions: “Why Microsoft?”, “What product area are you most excited about?”, “Describe a time you worked with a difficult teammate and how you resolved it”, “Where do you want to be in your career in 5 years?” Microsoft specifically values candidates who have a genuine opinion about their products and technical direction.

Microsoft-Specific Preparation Notes

Microsoft coding rounds tend toward medium-difficulty problems with an emphasis on correctness and clean code over bleeding-edge algorithmic cleverness. Candidates who write clean, well-commented code that handles edge cases reliably perform well, even if they do not find the most theoretically optimal solution.

Microsoft’s behavioural evaluation is less structured than Amazon’s LP framework but assesses: Growth Mindset (Microsoft’s core cultural value - do you learn from failures? Are you open to feedback?), collaboration and empathy, and genuine product passion. Prepare 2-3 examples of receiving critical feedback and acting on it, and 2-3 examples of helping a colleague or team succeed.

Flipkart Interview: SDE-1 and SDE-2 Round Breakdown

Flipkart is one of India’s highest-compensation technology employers and runs a rigorous interview process comparable in difficulty to Amazon for SDE-2 and above. Flipkart interviews are particularly known for strong DSA depth in coding rounds and practical system design problems grounded in e-commerce at Indian scale.

Flipkart Interview Loop

Round 1 - Online Coding Assessment: Hosted on HackerEarth or Flipkart’s proprietary platform. 2-3 problems in 90 minutes. Problems range from medium to hard. Flipkart OAs are known for slightly above-average difficulty compared to peer companies.

Round 2 - Machine Coding Round: Unique to Flipkart (and some other Indian product companies). A 90-minute session where you are given a practical problem - design and implement a working system component in your language of choice. Examples: build a rate limiter, implement an in-memory key-value store, build a basic order management system. The evaluator reviews not just correctness but code structure, naming conventions, extensibility, and test coverage. This round is essentially a working coding exercise rather than an algorithmic puzzle.

Round 3 - Data Structures and Algorithms Round: 2 coding problems with the interviewer, LeetCode medium to hard. Follow-up questions on complexity, alternative approaches, and edge case handling are standard.

Round 4 - System Design (SDE-2 and above): Design problems related to Flipkart’s actual domain: design a product search system, design a flash sale platform (with the specific challenge of handling massive spike traffic during Big Billion Days), design a seller inventory management system, design a recommendation system for product listings.

Round 5 - Hiring Manager Round: Experience, leadership signals, motivation, and team fit.

Flipkart Machine Coding Round Preparation

The machine coding round is the most distinctive element of Flipkart’s process and the round most candidates underestimate. Preparation requires:

  • Practice implementing clean, production-grade code (not just pseudo-code) under time pressure
  • Build familiarity with common design patterns (Strategy, Factory, Observer, Command) and be able to apply them in code spontaneously
  • Practise writing unit tests for your implementations (Flipkart reviewers look for test coverage)
  • LLD problems to practise: implement an ATM, implement a parking lot system, implement a hotel booking system, implement a ride-sharing matching engine at the class level

The machine coding round is one of the most reliable differentiation signals in Flipkart’s process - candidates who can produce clean, well-tested, extensible code in 90 minutes stand out clearly from those who produce working but messy code, or those who run out of time.

Razorpay, PhonePe & Fintech Product Company Interviews

India’s leading fintech product companies - Razorpay, PhonePe, CRED, Groww, Zepto, and Meesho - run interview processes broadly similar to Flipkart in structure, with some important domain-specific emphases.

Common Fintech Interview Emphases

Concurrency and transaction integrity: Fintech systems process payments, where double charges, missed transactions, and data inconsistency have direct financial and regulatory consequences. System design rounds at fintech companies probe specifically for: optimistic vs pessimistic locking, idempotency key design, distributed transaction patterns (Saga, 2PC), and exactly-once processing guarantees.

Security fundamentals: Authentication (JWT, OAuth), authorisation models (RBAC), encryption in transit and at rest, and PCI-DSS awareness (for payment companies) appear more frequently in fintech system design discussions than at consumer tech companies.

Reliability and uptime: Payment rails must function at 99.99% uptime or higher. System design rounds expect candidates to design for failure: what happens when the payment gateway is down? How do you handle partial failures in a distributed transaction? What is your retry strategy? What is your fallback?

Razorpay Interview Loop

Razorpay’s loop for experienced engineers:

Round 1 - Online Assessment: 2 coding problems, medium difficulty, on HackerRank or HackerEarth.

Round 2 - Machine Coding / Take-Home: Razorpay sometimes uses a take-home assignment (2-4 hours) in lieu of a machine coding round. The assignment is a practical problem: build a simplified payment gateway module, build a transaction reconciliation system, build a retry queue with exponential backoff.

Round 3 - Technical Discussion: Deep dive into your take-home submission or a fresh coding problem, followed by design discussion around a payment-related system.

Round 4 - System Design: Design a payment gateway, design a split-bill application at scale, design a subscription billing system.

Round 5 - Culture and Leadership Round: Razorpay specifically values ownership, hustle, and first-principles thinking. Prepare stories that demonstrate taking initiative without being asked, solving problems with limited resources, and end-to-end ownership of features from design to production.

Swiggy, Zomato & Consumer Tech Product Company Interviews

Consumer internet companies (Swiggy, Zomato, Dream11, upGrad, Nykaa, Meesho) tend to run interview processes similar to Flipkart in DSA and system design depth, with particular emphasis on:

Real-time systems: Order tracking, live delivery status, real-time inventory updates, live score feeds for gaming platforms. System design rounds at these companies frequently involve WebSocket-based real-time architectures, event streaming, and geospatial indexing.

Recommendation and personalisation: Consumer platforms invest heavily in recommendation engines (what to order, what to watch, what to buy). System design for recommendation systems - collaborative filtering, content-based filtering, real-time feature serving, A/B testing infrastructure - appears frequently.

Search and discovery: Product search, restaurant search, course search, and category browse are core UX flows. Designing search systems (Elasticsearch-based, with personalisation layers) is a common system design topic.

Swiggy Interview Loop

Round 1 - Online Coding: 2-3 problems, HackerEarth, medium difficulty.

Round 2 - Technical Phone Screen: 1-2 coding problems with a senior engineer. Resume discussion and project deep dive.

Round 3 - DSA Round: 2 coding problems, higher difficulty. Swiggy coding rounds are known for graph and tree problems, and for problems that require combining multiple data structures.

Round 4 - System Design: Design real-time order tracking for a food delivery platform, design a restaurant recommendation system, design the checkout and payment flow for a food ordering app. Real-time and geospatial elements are consistently prominent.

Round 5 - Hiring Manager Round: Culture, motivation, ownership signals.

Infosys Interview: InfyTQ, HackWithInfy & Lateral Hiring

Infosys is one of India’s largest engineering employers, with two distinct hiring pathways: campus recruitment (through InfyTQ platform and HackWithInfy competition) and lateral hiring for experienced candidates.

Campus Hiring: InfyTQ and HackWithInfy

InfyTQ (Infosys Talent Q): A digital learning and assessment platform primarily for engineering students. Clearing the InfyTQ certification exam (covering programming, databases, and data structures) makes students eligible for Infosys System Engineer and Digital roles. The exam consists of multiple-choice questions on programming fundamentals, SQL, and data structures, plus a basic coding section.

HackWithInfy: Infosys’s competitive coding contest for engineering students. Three rounds of progressively harder competitive programming problems. Top performers are offered roles in Infosys’s SP (Specialist Programmer) and DSE (Digital Specialist Engineer) tracks, which offer higher compensation and more technical roles than the standard SE track.

Standard On-Campus Process: Aptitude test (quantitative, logical, verbal) + coding round (2 problems, basic to medium difficulty) + technical interview (30-45 minutes on fundamentals, resume projects, SQL queries, OOP concepts) + HR interview.

Infosys Lateral Hiring

For experienced engineers applying laterally to Infosys:

Online Assessment: 90-minute test covering: reasoning ability, quantitative aptitude, verbal ability, and a coding section (2-3 problems, easy to medium).

Technical Interview (1-2 rounds): Questions covering: programming fundamentals in your stated primary language, data structures and algorithms at a moderate depth (sorting algorithms, BST operations, hash table collisions), OOPS concepts (polymorphism, inheritance, encapsulation, abstraction), database concepts (joins, indexing, normalisation, SQL queries), OS concepts (process vs thread, memory management, deadlock), and a brief review of your current project experience.

HR Interview: Motivation, career goals, relocation willingness, compensation expectations.

Infosys Interview Preparation Focus

For on-campus candidates: focus on aptitude test preparation (quantitative fundamentals: percentages, averages, profit/loss, time-speed-distance, probability), verbal ability (reading comprehension, sentence correction, fill in the blanks), and a basic coding foundation (implement sorting algorithms, write recursive programs, solve simple array and string problems).

For lateral candidates: strengthen fundamentals (OOPS, OS, DBMS, CN), review SQL query writing (especially joins, subqueries, aggregate functions), and prepare 2-3 structured descriptions of your current project and the technologies you used.

TCS Interview: NQT, Digital, Prime & Lateral Rounds

TCS is India’s largest IT employer and runs the most volume-intensive hiring process of any Indian technology company. For campus hiring, TCS uses its National Qualifier Test (NQT) framework with distinct tracks offering different roles and compensation levels.

TCS NQT: The Track System

TCS NQT (National Qualifier Test) - Standard Track: The primary campus hiring process for TCS’s System Engineer role. The NQT consists of: Cognitive Skills section (numerical ability, verbal ability, logical reasoning), Programming Logic section (output prediction, debugging, fill-in-the-blank code questions), Coding section (1-2 problems, easy difficulty). Candidates who qualify the NQT are invited for a Technical Interview and HR Interview.

TCS Digital: A separate track within the NQT for candidates interested in TCS’s digital transformation roles. Requires a higher NQT score plus questions on specific digital technology areas: cloud computing, cybersecurity, agile, DevOps. Compensation is significantly higher than the standard SE track.

TCS Prime: The highest campus track, offering the highest entry-level compensation at TCS. Requires a very high NQT score and strong performance in an additional test focused on advanced programming. Often compared to TCS’s honour program for technically strong candidates.

TCS Ninja / Ignite (for sub-premium colleges): A track specifically for students at colleges that may not qualify for the standard NQT-based process. Slightly more basic test content and leads to the standard SE role.

TCS NQT Preparation

Cognitive section: Quantitative aptitude practice from standard sources (RS Aggarwal, IndiaBIX, Quantitative Aptitude for Competitive Examinations). Focus areas: number systems, percentages, time and work, time-speed-distance, ratios, permutations and combinations, probability. Verbal ability: reading comprehension, fill in the blanks, error identification, sentence completion.

Programming Logic: This section requires familiarity with C, C++, Java, or Python. Understand: output tracing of programs with loops and recursion, identifying errors in code snippets, completing partial code. Practise on Coding Ninjas, GeeksForGeeks, and PrepInsta which have TCS NQT-specific question archives.

Coding Section: 1-2 problems of easy to easy-medium difficulty. TCS coding problems are simpler than product company problems. Typical patterns: string reversal and manipulation, basic sorting and searching, simple mathematical problems (factorial, Fibonacci, prime check), basic pattern printing.

TCS Technical Interview

The TCS technical interview (conducted post-NQT qualification) covers:

  • Self-introduction and project explanation (3-5 minutes) - practise a clear, confident project description
  • OOPS concepts: What is polymorphism? Explain with an example. Difference between overloading and overriding. What is abstraction?
  • Data structures: What is a linked list? How does a hash table work? What is the time complexity of binary search?
  • Database: Write a SQL query to find the second highest salary. Explain INNER JOIN vs LEFT JOIN. What is normalisation?
  • OS fundamentals: What is a process vs a thread? What is deadlock? Explain virtual memory.
  • Language-specific questions based on your resume (Java: explain JVM, garbage collection, collections framework; Python: explain GIL, list vs tuple, generators)

Most TCS technical interviews last 30-45 minutes. The depth is moderate - interviewers are primarily assessing whether the candidate has genuine understanding of fundamentals, not whether they can solve Google-level problems.

Wipro & HCL Interview: Coding + HR Round Breakdown

Wipro and HCL follow broadly similar structures to TCS and Infosys for both campus and lateral hiring. Understanding the differences helps avoid over- or under-preparing.

Wipro NLTH and Elite NLTH

Wipro’s campus hiring program (National Level Talent Hunt, NLTH) uses a tiered structure:

Standard NLTH: Aptitude test (online: reasoning + quantitative + verbal + coding) + technical interview + HR interview. Leads to Project Engineer role.

Elite NLTH: Separate application process with a harder coding test, evaluating medium-level programming problems. Leads to higher-compensation entry-level roles and faster project assignment.

Turbo Hiring: For candidates with very strong competitive programming profiles (ICPC participation, Codeforces Expert+ rating). Leads to Wipro’s highest entry-level compensation tier.

Wipro Technical Interview Focus

Wipro’s technical interview covers the same fundamental areas as TCS and Infosys: OOPS, data structures, DBMS, OS, and a project discussion. Additionally, Wipro interviewers frequently ask:

  • “Write a program to reverse a linked list” (implementation required on paper or in a text editor)
  • “What is the difference between TCP and UDP?” (basic networking)
  • “Explain the software development lifecycle (SDLC)”
  • “What testing approaches have you used?”

HCL Tech Bee and Lateral Process

HCL’s Tech Bee program recruits students after 12th grade into a 15-month B.Tech-equivalent program, which is separate from the standard engineering campus process.

For engineering graduates, HCL conducts a standard process: online aptitude test (similar structure to TCS/Wipro), coding test (1-2 problems, easy-medium), technical interview (fundamentals, resume review), HR interview.

HCL’s lateral hiring technical rounds are slightly more demanding than campus hiring. For lateral candidates with 2-5 years of experience, expect questions on: specific technologies listed on your resume, architecture of your current project, basic system design (no need for Google-level depth), and some deeper OOPS and data structure questions.

The Coding Round Playbook: Patterns, Platforms & Strategy

The coding round is the universal filter across all tiers of the Indian tech interview landscape. Every company, from TCS to Google, has some form of coding evaluation. The difference is difficulty level, not the existence of the evaluation. A systematic approach to coding round preparation produces better results than random problem solving.

The 15 Core Patterns Every Engineer Must Know

Coding interview problems, despite appearing infinitely varied, largely map to one of 15 recurring algorithmic patterns. Recognising the pattern is more than half the work of solving the problem.

1. Two Pointers: Two index variables moving through an array or string, often toward each other. Used for: sorted array pair sum, removing duplicates in-place, palindrome check, container with most water.

2. Sliding Window: A variable-size or fixed-size window moving across an array or string. Used for: maximum sum subarray, longest substring with at most K distinct characters, minimum window substring.

3. Fast and Slow Pointers (Floyd’s Algorithm): Two pointers moving at different speeds. Used for: cycle detection in linked list, finding the middle of a linked list, happy number.

4. Merge Intervals: Sorting intervals by start time, then merging overlapping intervals. Used for: merge intervals, insert interval, meeting rooms.

5. Cyclic Sort: Placing numbers in their correct index position for problems involving ranges 1 to N. Used for: find the missing number, find all duplicates.

6. In-place Reversal of Linked List: Reversing portions of a linked list without extra space. Used for: reverse a linked list, reverse a sub-list, k-group reversal.

7. Tree BFS: Level-order traversal using a queue. Used for: level-order traversal, zigzag traversal, connecting level order next pointers.

8. Tree DFS: Depth-first traversal (preorder, inorder, postorder) using recursion or explicit stack. Used for: path sum, diameter of binary tree, binary tree serialisation.

9. Two Heaps: Maintaining a max-heap and a min-heap simultaneously. Used for: median of a data stream, sliding window median.

10. Subsets / Combinations: Generating all possible subsets or combinations using BFS or backtracking. Used for: subsets, permutations, combination sum, letter combinations.

11. Modified Binary Search: Applying binary search to rotated arrays, matrices, or answer spaces. Used for: search in rotated sorted array, find minimum in rotated sorted array, search in a 2D matrix, koko eating bananas.

12. Bitwise XOR: Exploiting XOR properties for finding missing or unique numbers. Used for: single number, XOR of all elements.

13. Top-K Elements: Using a heap to efficiently find the K largest/smallest/most frequent elements. Used for: K closest points, top K frequent elements, K largest element.

14. K-way Merge: Merging K sorted arrays or lists using a heap. Used for: merge K sorted lists, K smallest pairs.

15. Dynamic Programming: Breaking problems into overlapping subproblems with optimal substructure. Major DP patterns: 0/1 Knapsack, Unbounded Knapsack, Fibonacci-type, Longest Common Subsequence, Palindrome DP, DP on grids, interval DP.

Platform Strategy

LeetCode: The primary preparation platform for product company interviews. Filter problems by company tag to see frequently asked questions at your target company. Solve 150-200 problems for Google/Amazon/Flipkart preparation. Focus on mediums; hard problems are useful but should not dominate practice time.

HackerRank and HackerEarth: The platforms most commonly used for online assessments at Indian companies (Infosys, TCS, HCL, and many product companies). Practice the specific interface: time-constrained problem solving with the requirement to handle multiple test cases and edge cases, not just a single example.

GeeksForGeeks: Excellent for reading explanations of algorithms and data structures, particularly for OOPS, OS, DBMS, and CN fundamentals that service companies test. Also has TCS, Infosys, and Wipro OA question archives.

Codeforces: Competitive programming platform useful for building raw problem-solving speed and mathematical reasoning. Particularly useful for candidates targeting Google and other companies that ask harder algorithmic problems. Aim for a Codeforces rating of 1400+ (Specialist) as a signal that your algorithmic foundations are solid.

During the Coding Round: What Interviewers Are Watching

Beyond correctness, interviewers evaluate your process:

Clarify before coding: Ask about input constraints (can values be negative? Can the array be empty? Is the input sorted?), expected output format, and whether there are multiple valid outputs. A candidate who codes without clarifying looks like they do not think about requirements - a major red flag for production coding.

Think aloud: Your reasoning process is evaluated alongside your code. “I’m considering a brute force O(n²) approach first, and I can see a potential O(n) solution using a hash map - let me think through that…” is much better received than silent coding.

Write clean code: Even under time pressure, use meaningful variable names. maxSumEndingHere is better than mseh. currentSum is better than cs. Clean names signal good coding habits.

Test your code: After completing a solution, walk through it with the example input. Then create a small edge case test: empty array, single element, all negative values, all duplicates. Catching your own bugs during the interview is strongly valued.

Discuss complexity: After solving, always state the time and space complexity unprompted: “This solution is O(n log n) time due to the sorting step, and O(n) space for the hash map.” If the interviewer asks “can you do better?”, it means a more efficient solution exists - try to think about where the bottleneck is.

Behavioural & HR Round Preparation: What Every Company Actually Asks

The HR and behavioural round is often the round engineers prepare least for - which is a strategic error. This round is where candidates who have cleared all technical rounds are sometimes rejected. Understanding the purpose of each question category and preparing structured answers makes the difference.

Universal Behavioural Questions and How to Approach Each

“Tell me about yourself”: This is an invitation to present your professional narrative, not a request for your life history. Structure: current role and what you do (1 sentence), how you got here / most relevant experience (2-3 sentences), what you are looking for (1 sentence). Keep it to 90-120 seconds.

“Why this company?”: Your answer must be specific to the company - not “because it’s a good company” or “for better growth opportunities.” Research the company’s engineering blog, their tech stack, their recent product launches, their stated culture values. “I’ve been following Razorpay’s engineering blog and specifically your post on building their distributed payment router - that’s the kind of distributed systems problem I want to work on at scale” is specific, credible, and demonstrates genuine interest.

“Why are you looking to leave your current role?”: Always answer in terms of what you are moving toward, not what you are running away from. “I’m looking for more ownership of product decisions end-to-end and to work on a larger-scale distributed systems challenge” is good. “My current manager is difficult to work with and there’s no growth” is bad. Even if the latter is true.

“What is your greatest strength?”: Choose a strength that is relevant to the role you are interviewing for, and immediately follow it with a specific example. “I’m particularly strong in performance debugging - I have a good intuition for where latency is accumulating in a system. At [Company], I diagnosed a p99 latency regression in our checkout flow that three other engineers had looked at, traced it to a N+1 query introduced in a recent deploy, and fixed it within two hours.”

“What is your greatest weakness?”: The goal is to demonstrate self-awareness and a growth orientation, not to impress with humility or deflect with false modesty. Choose a genuine area for development, describe what you have done to address it, and show evidence of improvement: “I used to underinvest in documentation, which caused issues during team transitions. After a rough onboarding experience for a new teammate, I started writing architecture decision records for every significant technical decision. My team lead has noted it as a specific improvement in my last two performance reviews.”

“Describe a time you failed”: This is asked in some form at almost every product company. The failure must be real, it must be your own (not “the team failed”), and your reflection must demonstrate genuine learning. What specifically did you do? What was the impact? What did you learn? What do you do differently now?

“Where do you see yourself in 5 years?”: At product companies, the expected answer demonstrates ambition without arrogance and shows that you have thought about your career direction: “I want to be operating as a senior or staff engineer, owning a significant technical domain, and mentoring a small team of engineers. I want to have gone deep in distributed systems and have built at least one system that I can point to as genuinely influencing the company’s technical direction.” At service companies, answers that show commitment to the company and a desire for progression within it are more appropriate.

Company-Specific HR Preparation

Google HR: Focus on intellectual humility, love of learning, and comfort with ambiguity. Have a genuine answer to “What are you reading / learning right now?” prepared.

Amazon HR / Bar Raiser: Every answer must tie back to a Leadership Principle. Even in the HR round, interviewers are scoring LP alignment. Know all 16 LPs cold.

Microsoft HR: Growth mindset and empathy are the core values. Prepare examples of feedback you received and acted on, and examples of helping colleagues succeed.

Flipkart / Swiggy / Indian product companies: Ownership, hustle, and builder mentality. Prepare examples of taking initiative, shipping something end-to-end, and handling ambiguous requirements.

TCS / Infosys / Wipro HR: Loyalty, commitment, and reliability. Interviewers at service companies want to hear that you are committed to joining and staying, that you understand and accept the work environment, and that you have realistic expectations about the initial role. Compensation negotiation happens in this round - research the standard CTC for your track before the interview.

Building a 12-Week Interview Preparation Plan

A structured 12-week plan for a candidate targeting both product companies and service company lateral roles simultaneously. Adjust the time allocation based on your specific target set.

Weeks 1-3: Foundation Building

DSA fundamentals: Review all core data structures (arrays, linked lists, stacks, queues, trees, heaps, graphs, hash tables, tries) and their time/space complexities. Implement each from scratch at least once. Focus on understanding, not memorisation.

Language proficiency: Ensure fluency in your primary language’s standard library functions for string manipulation, sorting, collections, and I/O. Know the time complexity of the standard library operations you use.

LeetCode easy problems: Solve 30-40 easy problems to build baseline confidence and pattern familiarity. Speed matters here - aim to solve easy problems in under 10 minutes.

Mathematics fundamentals (for service company prep): Quantitative aptitude revision: percentages, averages, ratios, number theory basics, basic probability, permutations and combinations.

Weeks 4-7: Core Pattern Mastery

LeetCode mediums by pattern: Work through the 15 patterns in sequence. For each pattern, solve 5-8 medium problems before moving to the next. Track which problems you solved cleanly vs needed hints.

System design introduction: Begin reading Designing Data-Intensive Applications (Chapters 1-5). Watch 3-4 system design walkthroughs on ByteByteGo or NeetCode.

OOPS, DBMS, OS, CN fundamentals: Prepare clear, spoken explanations of the top 20 questions in each area. These are critical for service company interviews and baseline for product company interviews.

Mock OA: Attempt 2-3 timed mock online assessments (90 minutes, 2-3 problems) to simulate the OA experience.

Weeks 8-10: Advanced Depth

LeetCode hard and company-specific: Solve 20-25 hard problems. Focus on DP and graph problems, which are the most commonly high-difficulty topics. Switch from pattern-based practice to company-tagged practice on LeetCode for your top 3 target companies.

System design deep dive: Complete DDIA. Practice 4-6 full system design problems end-to-end (requirements → estimation → HLD → deep dives). Use the walkthroughs from the system design guide as your framework.

Behavioural preparation: Write your 12-15 STAR stories. Record yourself answering 10 behavioural questions and review the recordings. Most people are surprised by filler words, pace issues, and lack of specificity that they do not notice while speaking.

Weeks 11-12: Integration and Mock Interviews

Full mock interviews: Conduct 4-6 complete mock interviews (coding + system design) with a partner or on a mock interview platform (Pramp, interviewing.io, Exponent). Mock interviews are the single best predictor of actual interview performance - candidates who do 6+ mocks before a real interview perform significantly better than those who skip this step.

Review weak areas: Your mock interview feedback will reveal specific weaknesses. Allocate the final 10 days to targeted remediation of the specific areas identified.

Logistics preparation: For virtual interviews, test your camera, microphone, and internet connection. Prepare your environment (clean background, adequate lighting, quiet space). Have a backup device ready. For in-person interviews (now rare but still used by some companies), plan your travel to arrive 15 minutes early.

Adapting the Plan for Different Starting Points

The 12-week plan above assumes a baseline of 3+ years of engineering experience and some prior exposure to DSA concepts. Two common deviations:

Starting from scratch (fresher or early career, very limited DSA): Add a 4-week prefix to the plan focused exclusively on learning the foundational data structures and implementing them. Before solving LeetCode problems, implement: dynamic array, stack, queue, linked list, binary search tree, heap, and hash table from scratch in your primary language. This hands-on implementation builds intuition that makes pattern recognition in problem solving much faster.

Time-compressed preparation (interview in 4-6 weeks): Ruthlessly prioritise. Solve only the top 75 LeetCode problems (NeetCode’s curated list is excellent for this), focus system design preparation on the 5 most common problem types (URL shortener, social media feed, chat application, video streaming, notification system), and prepare 8 STAR stories instead of 15. Accept that your preparation will not be comprehensive and focus on being strong in the highest-probability areas rather than weak across everything.

Tracking Progress During Preparation

A preparation tracker (simple spreadsheet) with the following columns makes the process measurable: problem name, difficulty, pattern, date solved, time taken, solved without hint (yes/no), needs review (yes/no). Review problems marked “needs review” weekly until you can solve them cleanly without reference.

Setting weekly targets (e.g., 15 problems per week + 1 system design problem + review 2 past problems) creates accountability and prevents the common pattern of uneven effort (intensive preparation for 2 weeks, then dropping off). Consistency over the 12 weeks produces better outcomes than uneven intensity with gaps.

The Mindset During Preparation

Preparation for a technical interview is a long process with natural ups and downs. The “I can’t solve any problem” feeling that emerges after a run of difficult problems is normal and does not reflect actual lack of progress - it reflects the recency effect of working on hard problems. Progress in DSA skill is not linear; it has long flat phases where you feel stuck, followed by sudden jumps in clarity. Trusting the process and maintaining consistent daily practice through the flat phases is the discipline that separates candidates who are ready when their interview arrives from those who burn out partway through preparation.

Mock Interview Strategy: How to Practice Effectively

Most candidates practise problems but do not practise interviews. These are different activities. Solving problems on your own, in your own time, without verbalising your thinking, trains a skill that is only partially transferable to the interview environment.

What a Mock Interview Practises That Solo Problem Solving Does Not

Real-time communication under pressure: The anxiety of speaking while thinking is different from thinking alone. Mock interviews force you to manage this dual-task pressure repeatedly until it becomes comfortable.

Handling hints gracefully: In real interviews, interviewers sometimes give hints when you are stuck. Candidates who respond to hints defensively (“I was just about to think of that”) or who wait for hints passively instead of working through confusion lose points on the independence dimension. Mock interviews let you practise receiving hints as collaborative input.

Interviewer signals and body language reading: An interviewer who is making notes, nodding, or asking follow-up questions is signalling that you are on the right track. An interviewer who is silent or slightly frowning may be signalling concern. Learning to read and respond to these signals is a practised skill.

Time management under observation: In solo practice, you can spend 45 minutes on a problem. In an interview, spending 35 minutes on one problem when there are two leaves you with almost no time for the second. Mock interviews force the time discipline that solo practice does not.

Platforms for Mock Interviews

Pramp (peer-to-peer): Free platform that matches you with another engineer for mutual mock interviews. You interview each other. The quality of your interviewer varies, but the experience of being on both sides of the table is valuable.

interviewing.io: Anonymous technical mock interviews with professional engineers from companies including Google, Amazon, and Airbnb. Paid for premium sessions; some free practice with automated mock questions. Interviewer feedback is detailed and actionable.

Exponent: Strong for system design mocks and product management interviews. Paid platform with professional mock interviewers.

Friend and peer network: A committed friend or colleague willing to conduct a genuine mock interview (not a conversational review of your resume) is as valuable as any paid platform. Agree to use a timer, not interrupt except to give hints when genuinely needed, and provide specific written feedback after.

The Right Way to Use Mock Interview Feedback

The feedback from a mock interview is only as valuable as how you use it. After each mock, create a specific action item from each piece of feedback: “I talked too fast when explaining my approach” → practise voice recordings of problem explanations. “I did not discuss time complexity until the interviewer asked” → make a rule to always state complexity immediately after coding the solution without waiting to be prompted. “I froze when the interviewer asked me to optimise my O(n²) solution” → practise optimisation drills: take 10 problems you have already solved at O(n²) and work specifically on how to find the O(n) solution.

Feedback without a specific behavioural change in your next session does not improve performance. The improvement loop is: mock → identify specific gap → targeted practice → next mock.

Recording Yourself

Recording your video and audio during mock interview sessions (with your mock partner’s consent) and watching the recording afterward is one of the most uncomfortable and most effective preparation tools available. Most engineers are unaware of specific verbal habits (saying “um” and “uh” frequently, trailing off at the end of sentences, speaking too quickly when nervous) and non-verbal signals (avoiding eye contact with the camera, fidgeting, expressionless affect during problem reading) that affect how interviewers perceive their communication quality. A single recorded mock session, reviewed with the intent to identify these patterns, often produces more improvement than 5 additional hours of LeetCode practice.

Mid-Tier Product Company Interviews: Persistent, LTIMindtree, Nagarro & Others

Mid-tier product and IT companies sit between the rigour of Tier 1 product companies (Google, Flipkart, Razorpay) and the volume-driven process of large IT services firms. For engineers making the transition from a service company background to a product company environment, these companies are often the most accessible first target and the most strategically valuable stepping stone.

What Makes Mid-Tier Product Companies Different

Companies like Persistent Systems, LTIMindtree, Nagarro, Publicis Sapient, Mphasis, and Coforge have meaningfully increased their technical bar over recent hiring cycles. They are competing for talent with Tier 1 product companies and have responded by building interview processes that are closer to product company standards than to IT services standards, particularly for senior roles.

The key differences from IT services company interviews: coding rounds are genuine problem-solving exercises (not multiple-choice or fill-in-the-blank), system design discussions are present at SDE-2 equivalent levels, and interviewers ask about specific technical decisions in your past projects rather than just confirming that you know definitions.

Persistent Systems Interview Process

Persistent Systems has become one of India’s most aggressively hiring mid-tier companies and runs a process that reflects their aspiration to be recognised as a product engineering company:

Round 1 - Online Assessment: 2 coding problems (medium difficulty), aptitude section (quantitative + logical), and sometimes a written communication assessment.

Round 2 - Technical Interview 1: Live coding on a shared document (1 problem, medium difficulty) + in-depth discussion of your resume project. Interviewers ask: “Walk me through the most technically complex thing you built. What were the alternatives you considered? Why did you make the choices you did?” This depth of project discussion is more product-company-like than IT services.

Round 3 - Technical Interview 2 (Senior roles): System design or architecture discussion relevant to the role you are targeting. For cloud and platform roles, AWS/GCP architecture questions. For Java backend roles, Spring Boot architecture, microservices patterns, and database design.

Round 4 - HR / Management Interview: Standard motivation, salary, and fit discussion.

Nagarro Interview Process

Nagarro’s interview process is notable for emphasising hands-on coding ability over theoretical knowledge:

Round 1 - Online Coding Test: 2-3 problems in 60-90 minutes. Medium difficulty. Nagarro’s OA is known for being practically oriented - problems often simulate real engineering tasks rather than pure algorithmic puzzles.

Round 2 - Technical Discussion: Pair coding exercise on a problem related to web services or API design, followed by a discussion of your work experience and technical decisions.

Round 3 - Cultural and HR Interview: Nagarro specifically emphasises entrepreneurial thinking and self-direction. Prepare examples of taking ownership beyond your defined role and delivering without close supervision.

Publicis Sapient Interview Process

Publicis Sapient’s interview process for engineering roles:

Round 1 - Online Assessment: Logic, quantitative aptitude, English, and a coding section (2 problems).

Round 2 - Technical Interview: DSA problem (medium), followed by a detailed project discussion and questions on web technologies, APIs, databases, and cloud fundamentals.

Round 3 - Communication Assessment: Publicis Sapient, as a consulting-flavoured engineering company, specifically assesses communication quality. A structured communication interview or a presentation-style discussion of a past project is common.

Round 4 - HR Interview: Culture fit, role expectations, and compensation discussion.

Startup and Early-Stage Company Interviews

Interviews at early-stage startups (Seed to Series B) differ meaningfully from interviews at established product companies, and many Indian engineers targeting the startup ecosystem underestimate these differences.

What Startups Actually Evaluate

Early-stage startups have limited engineering resources and need every new hire to contribute substantively and quickly. They evaluate candidates differently from large companies:

Breadth over depth: A startup SDE-2 may be expected to build features across the full stack, manage AWS infrastructure, write CI/CD pipelines, and debug production issues all in the same week. Candidates who have only ever worked on a single narrow backend service may struggle in this environment. Demonstrate breadth of experience and comfort with context-switching.

Ownership mentality: Startup interviewers are evaluating whether you will take problems to completion or escalate every ambiguity upward. They want people who will ship. Prepare stories of shipping in ambiguity, making pragmatic trade-offs under constraints, and owning outcomes end-to-end.

Speed and pragmatism: Startups do not have time for months-long migrations or perfectly designed systems that never ship. Candidates who demonstrate the judgment to know when to build something quickly and when to invest in quality are highly valued.

Product thinking: At startups, every engineer is expected to have an opinion about the product. Interviewers may ask: “How would you improve our onboarding experience?” or “What do you think the most important thing we should build next is?” Having used the product before the interview and having a genuine informed opinion demonstrates the kind of engagement startups want.

Startup Technical Interview Typical Structure

Most early-stage startups run 3-4 interview rounds:

Round 1 - Technical Screen (30-45 minutes): A single coding problem (usually medium difficulty), a brief project discussion, and an assessment of whether you can articulate technical decisions clearly. At early-stage startups, the founder or CTO may be conducting this round themselves.

Round 2 - Take-Home or Pair Programming: Many startups prefer a practical coding exercise over algorithmic puzzles. They may send a take-home assignment (build a small API, fix bugs in an existing codebase, implement a feature in their actual tech stack) or conduct a pair programming session where you work on a real problem together.

Round 3 - Culture and Team Fit: Discussion with 2-3 team members about how you approach work, handle disagreements, and learn from failures. Startup culture fit interviews are less structured than Amazon LP rounds but evaluate a similar set of values: autonomy, ownership, growth orientation.

Round 4 - Founder or CTO Round: For senior roles, often a conversation about the company’s technical direction, your vision for the role, and an informal mutual assessment of fit.

Preparing for Startup Interviews

  • Use the product before the interview. Have specific, informed opinions about what works well and what could be improved.
  • Research the company’s tech stack (often available on their engineering blog or job descriptions) and have examples of your work with those technologies.
  • Prepare for open-ended questions about how you would approach their specific engineering problems - “How would you design our notification system to handle 10x user growth?” - by applying the system design framework.
  • Be genuinely curious about their trajectory, funding, team, and technical roadmap. Founders can tell when a candidate is genuinely interested versus just collecting interview experience.

Compensation Negotiation Starts at the Interview Stage

The interview process and the compensation negotiation are not separate events - the interview stage actively shapes your leverage in the offer negotiation. Understanding this connection helps you make strategic decisions throughout the process.

How Interviewers Score Affects Offer Band

At companies like Google and Amazon, the interview scores submitted by each interviewer directly influence the compensation band offered. A “strong hire” score (typically reserved for candidates who exceed expectations in most rounds) often triggers a higher starting band than a “hire” score. Candidates who perform at the top of the expected range may be extended a higher base salary or a larger RSU grant as part of the initial offer.

This means that performing well is not just about getting the offer - it is about getting a better offer. The marginal benefit of raising your performance from “hire” to “strong hire” in a Google or Amazon loop can be Rs 5-15 lakh in annual total compensation.

Using the Interview Process to Build Rapport

The engineers who interview you are often the same people you will work alongside if you join. The interview is a mutual evaluation. Treating it as a one-way assessment - where you are trying to impress them - misses the dynamic. Ask thoughtful questions about the team, the technical challenges, and the engineering culture.

Good questions to ask during technical rounds: “What is the most technically interesting problem the team has worked on in the last year?” / “What does on-call look like for this team, and how have you reduced incident frequency?” / “What is the biggest technical challenge the team is facing that this hire would help address?”

These questions demonstrate product and engineering maturity, give you genuine information for your decision, and are remembered positively by interviewers writing their feedback. Candidates who ask no questions, or only generic questions (“what is the work-life balance like?”), are sometimes noted negatively in interviewer feedback for appearing disengaged.

The Time-to-Offer Window and Competing Offers

Most product companies will give you 5-14 days to accept or decline an offer before it expires. If you have a competing interview process underway, notify those companies as soon as you have an offer and ask if they can accelerate their process: “I have received an offer from [Company X] with a deadline of [date]. I am still very interested in [your company] and would greatly appreciate knowing if it is possible to complete the process before that date.”

Most companies will attempt to accommodate this if they are genuinely interested in the candidate. This also creates the competitive dynamic that supports better negotiation - a candidate with one competing offer has leverage; a candidate with two or three has significant leverage.

After the Offer: What to Check Before You Sign

Receiving an offer is not the end of the process - it is the beginning of a decision that will affect your career and compensation for years. The due diligence checklist before signing:

Technical Due Diligence

The actual team and role: The team you interview with is not always the team that will eventually make you an offer. Confirm which specific team you are joining, who your manager will be, and what the first 3-6 months of work will look like. A great company with a struggling team or a weak manager produces a worse experience than a slightly lower-tier company with an excellent team.

The tech stack you will actually work on: Job descriptions are sometimes aspirational - they list the tech stack the company wants to build toward, not what you will immediately work on. Ask directly: “In the first 6 months, what will my day-to-day look like? What systems will I primarily work with?”

On-call obligations: Some engineering teams have demanding on-call rotations (every other week, multiple incidents per shift). This is information you are entitled to have before signing. Ask the hiring manager or your interviewing engineer: “What does the on-call rotation look like? How frequently do incidents occur during on-call shifts?”

Compensation Due Diligence

Before accepting, verify in writing: base salary, variable pay (at what target percentage and what typical payout rate), joining bonus and its clawback terms, RSU/ESOP grant (number of units, current value, vesting schedule, cliff date), health insurance coverage, and start date.

If any of these are verbal commitments not yet in the offer letter, ask for a revised offer letter before accepting. “Thank you for confirming that. Could you ensure these terms are reflected in the written offer letter before I sign?” is a completely professional and expected request.

Frequently Asked Questions

Q1: How long does the full interview process take at Google, Amazon, and Flipkart?

Timeline from application to offer varies significantly. Google’s process, from OA to offer letter, typically takes 6-10 weeks due to the Hiring Committee review process that happens after all technical rounds are completed. Amazon is faster at 4-6 weeks for most candidates. Flipkart and Indian product companies are typically 2-4 weeks. Service companies (TCS, Infosys) move fastest - campus hiring is often 1-2 weeks from NQT to offer letter.

Q2: Can I prepare for Google and TCS simultaneously?

Yes, but the preparation has limited overlap at the top end. TCS preparation focuses on aptitude, fundamentals (OOPS, DBMS, OS), and easy coding problems. Google preparation requires deep DSA, system design, and behavioural story preparation at a significantly higher level. A reasonable approach: build the TCS-level foundation in weeks 1-3 (this also covers the fundamentals portion of product company preparation), then add the product company layers in weeks 4-12.

Q3: How many LeetCode problems do I need to solve before applying to product companies?

Quality over quantity. 150-200 well-practised problems (you could re-solve them without a hint) covering all 15 patterns is more valuable than 500 problems where you looked at solutions after 10 minutes of struggling. The goal is pattern recognition fluency, not a problem count milestone.

Q4: Is competitive programming experience required for product company interviews?

Not required, but advantageous. Engineers with Codeforces Expert (1600+) or LeetCode Guardian ratings solve coding problems faster and handle harder problems more consistently. For candidates without competitive programming background, focused LeetCode preparation for 8-12 weeks achieves sufficient readiness for most product company coding rounds.

Q5: What is the failure rate at each stage of a Google interview loop?

Google does not publish this data, but community data suggests: OA pass rate approximately 20-30%; phone screen pass rate approximately 50% of those who clear OA; full loop to offer rate approximately 15-25% of those who enter the full loop. Overall, roughly 1-5% of all applicants receive an offer. This is not discouraging - it means the process is a lottery only for those who are not adequately prepared. Prepared candidates have substantially higher pass rates than these averages.

Q6: Should I disclose competing offers during the interview process?

You are not obligated to disclose competing offers during the interview rounds themselves. Competing offers become useful leverage at the offer negotiation stage. At that point, mentioning “I have an offer from [Company X] at Rs X lakh total comp” is legitimate and expected negotiation practice. Some companies expedite their process if they know you have a competing offer that is time-limited.

Q7: How should I handle a round where I completely failed to solve the problem?

Do not shut down or apologise excessively. Interviewers have seen every level of performance; a single poor round does not automatically disqualify a candidate, particularly if other rounds were strong. If you fail to solve a problem, the most important things to demonstrate are: you understand why your approach failed (if you do), you can engage constructively with hints, and your communication and thought process remained clear even when the algorithm was not working. Companies evaluate the person across the full loop, not individual rounds in isolation.

Q8: Is it appropriate to ask for feedback after a rejection?

Yes, particularly for senior roles at product companies. Most companies will not provide detailed interview feedback due to legal liability concerns, but it is acceptable to politely ask: “I appreciate the opportunity to interview. Would it be possible to receive any feedback on my performance to help with future interviews?” Google and Amazon typically decline to provide specific feedback; some smaller product companies are more forthcoming. Even a general “you performed well technically but we had a stronger candidate” vs “there were technical gaps in the system design round” provides useful signal for future preparation.

Q9: How do I handle back-to-back interview rounds on the same day (on-site loop)?

On-site loops where all 4-5 rounds happen in a single day are physically and mentally demanding. Practical strategies: eat a proper meal before the loop starts; bring water and a snack if breaks are short; prepare a mechanism to mentally reset between rounds (a 5-minute walk during a break, a brief breathing exercise). Most importantly: do not let a poor round affect your performance in subsequent rounds. You do not know how you performed in a round you thought went badly - interviewers often evaluate differently than candidates expect. Stay focused on the next round regardless of how you feel about the previous one.

Q10: How should I approach a problem I partially remember from LeetCode during an interview?

Be transparent. Saying “I think I’ve seen something similar to this before, though I don’t remember the exact solution - let me think through it from first principles” is perfectly acceptable. Interviewers are not penalising you for having a good memory, but they do evaluate your problem-solving process. If you remember the solution perfectly, work through it as you would any solution: explain your approach, discuss complexity, test with examples. Trying to pretend you have not seen a problem and then “solving” it suspiciously fast raises more questions than transparency does.

Q11: What is the difference between a lateral transfer interview within a company and an external interview?

Internal transfers at large companies (Amazon, Microsoft, Google) typically involve fewer rounds than external interviews, since the company already has background on your performance through internal systems. Amazon internal transfers typically involve 2-3 rounds focused on LP alignment for the new team and a brief technical assessment relevant to the new team’s work. Microsoft and Google internal transfers often involve a lightweight technical discussion with the target team’s manager plus one or two team members. The bar is typically lower than external hiring, though this varies by team and situation. One caveat: your internal performance record (calibration scores, promotion history, manager feedback) is visible to the hiring team in ways an external candidate’s history is not - strong internal performers have an advantage that compensates for the lower bar.

Q12: How many companies should I interview with simultaneously?

Enough to create genuine optionality without spreading your preparation and bandwidth too thin. A reasonable number is 5-8 active interview processes simultaneously. More than this becomes logistically difficult (multiple OAs, scheduling across companies, keeping track of each company’s LP framework and cultural nuances) and risks superficial preparation for all of them. Fewer than 3-4 active processes leaves you without competitive leverage at the offer stage. Prioritise your process starts sequentially if possible: if your top target has a 6-week process timeline, begin with 1-2 backup companies first to practice and calibrate, then add your top targets when you feel ready.

Q13: How important is it to know the specific company’s products before the interview?

Critically important for motivation questions in HR and hiring manager rounds; moderately important for technical rounds. In HR rounds, “Why this company?” is almost always asked, and an answer that demonstrates you have actually used the product and have a specific informed perspective on it is far more credible than a generic “I’ve heard great things about the engineering culture.” In system design rounds, familiarity with the company’s product domain helps you ask better clarifying questions and propose relevant design considerations. For Google, use Google’s products deeply - YouTube, Maps, Search - and understand what makes them technically challenging. For Razorpay, understand the payment infrastructure challenges they publicly discuss in their engineering blog.

Q14: What should I do in the 24 hours before an interview?

Do not try to learn new material in the 24 hours before an interview - new information is unlikely to help and may increase anxiety. Instead: review 5-10 problems you have already solved, particularly ones in the patterns you find most challenging; review your STAR stories once (do not over-rehearse; over-rehearsed answers sound robotic); confirm the interview logistics (link, time zone, interviewer name); test your audio and video setup for virtual interviews; prepare 3-4 questions to ask your interviewer; and sleep well. Sleep quality in the 2 nights before the interview is among the strongest predictors of cognitive performance during the interview. Do not sacrifice sleep for last-minute cramming.

Q15: What happens if I accept an offer and then receive a better offer the next day?

Reneging on an accepted offer is a serious professional decision with real consequences. Offer rescindment after acceptance harms your reputation in the industry (particularly since engineering communities are small and well-connected), may disqualify you from future applications at that company, and in some cases (where you have received a large joining bonus) may create a legal liability. That said, if the competing offer represents a genuinely significant improvement that will affect your career trajectory (not just an incremental compensation difference), reneging is sometimes the right personal decision. The ethical minimum: notify the company you are declining as soon as possible - do not wait until your start date. Provide a brief, professional explanation without excessive apology. Some companies will attempt to match; if they cannot or choose not to, accept that gracefully.

Interview preparation for Indian tech companies rewards systematic, structured effort more than it rewards raw intelligence. The patterns are learnable. The LP stories are preparable. The system design vocabulary is buildable. The differentiator between candidates who receive offers and those who do not is almost always consistent preparation depth, communication practice, and honest assessment of weak areas followed by targeted remediation. The companies in this guide all have well-documented hiring processes. Use that documentation, build your preparation systematically, and approach every round as a collaborative problem-solving conversation rather than an adversarial test.

Every rejected application and every failed round is information. Companies reject for reasons that are almost never personal - they reject because a specific set of skills was not demonstrated convincingly in a specific interview window. The engineers who receive offers at Google, Amazon, and Flipkart are not uniformly more talented than those who do not - they are better prepared for that specific evaluation format, on that specific day. Preparation quality is the variable you control; make it your highest leverage investment in your career.

All interview process details, compensation figures, and platform references in this guide are based on community-reported data and publicly available information. Hiring processes evolve; always verify current round structures with the company’s recruiter at the start of your interview process.