Flipkart Hiring Process 2026: Rounds, OA & Runway

Quick answer (updated 8 June 2026): Flipkart's fresher SDE hiring in 2026 typically runs an online assessment (DSA plus often a debugging or aptitude section), followed by a machine-coding round, one to two DSA and problem-solving interviews, sometimes a low-level or high-level design round, and an HR round. Flipkart also runs dedicated entry drives like Runway (off-campus for experienced and fresher pools) and GiRL (Girls Wanna Code) for women in tech. The flow below is compiled from 2023 to 2025 candidate reports, not an official document, so confirm your stages with your recruiter and the Flipkart careers portal.

Flipkart's process is distinctive because of its machine-coding round, where you build a small working program, not just solve an algorithm. If you walk in expecting pure LeetCode, the machine-coding round will surprise you. This guide covers the whole process and how to prepare for each stage.

The Flipkart Hiring Funnel

Based on candidate reports for 2023 to 2025 fresher and early-career SDE batches:

Stages and counts are candidate-reported (2023 to 2025) and vary by role, level, and drive. Your recruiter and scheduling email are binding for your loop.

Flipkart Entry Drives: Runway and GiRL

Flipkart runs branded hiring drives in addition to standard openings:

• Runway: an off-campus hiring drive Flipkart has used to source engineers, including those from non-traditional or career-break backgrounds, through a coding-test-led funnel.
• GiRL (Girls Wanna Code): a women-only hiring and mentorship program that has run at large scale, drawing many thousands of applicants in past editions, with a coding contest as the entry filter.

These drives use the same core competencies, DSA and machine-coding, as the standard process, so the prep below applies to all of them. Watch Flipkart's careers portal and verified social channels for live editions and their exact eligibility windows.

The Machine-Coding Round (Flipkart's signature)

This is the round that distinguishes Flipkart. Instead of one algorithmic puzzle, you are given a problem statement (for example, design a Splitwise-style expense splitter, a parking lot, or a snake-and-ladder game) and roughly 90 to 120 minutes to build a working, runnable solution.

What interviewers evaluate, per candidate reports:

• Working code. It must compile and run against the stated scenarios.
• Clean design. Proper classes, separation of concerns, sensible interfaces.
• Extensibility. Could you add a new feature without rewriting everything? SOLID principles matter.
• Edge cases and validation. Handle invalid input gracefully.
• No external frameworks usually. Plain language constructs; an in-memory model is fine.

How to prepare: practise building three to five classic machine-coding problems end to end (parking lot, expense sharing, library management, elevator, snake and ladder) in your strongest language. Time yourself. Focus on modelling entities, writing clean interfaces, and leaving room to extend.

The DSA Interview Rounds

One to two live coding rounds covering arrays and strings, hashing, trees, graphs, recursion, and dynamic programming. Flipkart's bar favours clean, correct solutions with clear complexity analysis.

Approach each problem by clarifying constraints, stating your approach and complexity, coding cleanly, then dry-running on an example. Flipkart interviewers, like most product companies, reward communication and edge-case rigour over speed alone.

The Design Round

For freshers, design is usually low-level design (class modelling for a given scenario) rather than full distributed-systems design. For candidates with some experience, a high-level design discussion (designing a scaled-down service) may appear.

Prepare by learning to:

• Clarify functional and non-functional requirements.
• Identify core entities and their relationships.
• Reason about basic trade-offs (consistency vs availability, memory vs speed).
• Sketch a clean class diagram or component diagram.

See system design interview questions freshers 2026 for the fundamentals.

The HR and Hiring Manager Round

The closing round covers motivation, fit, your projects, and behavioural questions. Common prompts:

• Why Flipkart?
• Walk me through your most significant project.
• Tell me about a time you handled a tight deadline.
• How do you handle disagreement on a team?

Answer with real STAR examples, show genuine interest in Flipkart's scale and e-commerce problems, and be ready to discuss your resume in depth.

Round-by-Round Prep Plan

• OA: drill DSA fundamentals and, if your drive includes it, aptitude and debugging.
• Machine-coding: build three to five classic design problems end to end; practise clean class modelling under a timer.
• DSA interviews: master arrays, strings, hashing, trees, graphs, and DP; narrate while solving.
• Design: learn LLD basics, SOLID, and one or two simple service sketches.
• HR: prepare STAR stories and a crisp "why Flipkart" answer.

5 Mistakes to Avoid in the Flipkart Process

1. Treating machine-coding like LeetCode. It rewards clean design and working software, not one clever algorithm.
2. Writing unstructured code in machine-coding. A single giant function fails; use proper classes and interfaces.
3. Skipping edge cases. Invalid input handling is explicitly evaluated.
4. Coding in silence in DSA rounds. Narrate your approach and complexity.
5. Generic "why Flipkart". Tie your answer to its e-commerce scale and engineering problems.

Eligibility and Key Dates (Reference)

Flipkart hires freshers through campus drives, off-campus openings, and branded drives like Runway and GiRL. The reference criteria below are compiled from candidate reports for 2023 to 2025 cycles and vary by role and drive; the binding eligibility is whatever the specific job notification on the Flipkart careers portal states.

Eligibility figures are candidate-reported references (2023 to 2025), not official cutoffs. Flipkart runs drives, including Runway and GiRL, through the year; watch its careers portal and verified channels for live editions and their exact eligibility windows and dates. The job notification is binding.

How to Approach the Machine-Coding Round Step by Step

The machine-coding round is what makes Flipkart distinctive, and it is where many strong DSA candidates stumble, because it tests a different skill: turning a loose requirement into clean, working, extensible software in roughly 90 to 120 minutes. Spend the first ten to fifteen minutes planning rather than typing. Read the prompt twice, list the core entities (for an expense splitter, that is User, Expense, and the split logic), and decide the operations each must support. Sketch the class responsibilities before writing code, because a clear object model is what the interviewer is really grading.

When you start coding, build the smallest end-to-end slice first: a single expense split equally between two users, before you handle unequal splits or settlements. A working thin slice you can demonstrate beats a half-written perfect design. Then layer in the harder cases (percentage splits, multiple participants), validation (reject an invalid split), and extensibility hooks (a clean way to add a new split type). Narrate your decisions as you go, and reserve the final minutes to run your code against the scenarios in the prompt. Candidates who pass treat this as building a small product, keeping classes focused, methods short, and naming clear.

Avoid over-engineering. You rarely need design patterns for their own sake or a database; an in-memory model with clean interfaces is enough. Use inheritance only for a genuine is-a relationship, prefer composition otherwise, and keep each class doing one thing. If you finish early, the strongest move is to add one well-chosen extension, a new split type, a settlement summary, and explain how your design accommodates it, which directly demonstrates the extensibility Flipkart is testing.

More Sample Questions with Explained Approaches

Question 1: Two Sum (Hashing)

Single-pass complement lookup, a common OA opener.

def two_sum(nums, target):
    seen = {}
    for i, x in enumerate(nums):
        if target - x in seen:
            return [seen[target - x], i]
        seen[x] = i
    return []

Time O(n), space O(n).

Question 2: Merge Intervals

Sort by start, merge overlapping intervals.

def merge(intervals):
    intervals.sort(key=lambda x: x[0])
    out = []
    for s, e in intervals:
        if out and s <= out[-1][1]:
            out[-1][1] = max(out[-1][1], e)
        else:
            out.append([s, e])
    return out

Time O(n log n), space O(n).

Question 3: Machine-Coding, an Expense Splitter (LLD)

Model User, Expense, and a SplitService that records expenses and computes who owes whom. Support equal and unequal splits via a clean split-strategy abstraction so new split types can be added without changing the service. Interviewers score the abstraction, validation, and extensibility.

Question 4: Number of Islands (Graph DFS)

Count connected land components by sinking each on first contact.

def num_islands(grid):
    rows, cols = len(grid), len(grid[0])
    count = 0

    def sink(r, c):
        if 0 <= r < rows and 0 <= c < cols and grid[r][c] == '1':
            grid[r][c] = '0'
            for dr, dc in ((1,0),(-1,0),(0,1),(0,-1)):
                sink(r + dr, c + dc)

    for r in range(rows):
        for c in range(cols):
            if grid[r][c] == '1':
                count += 1
                sink(r, c)
    return count

Time O(rows times cols).

Why Candidates Get Rejected at Flipkart

Candidate reports point to recurring reasons beyond failing the coding round:

• Treating machine-coding like LeetCode. Writing one giant function instead of clean classes fails this signature round.
• Coding in silence in DSA rounds. Failing to narrate your approach and complexity loses signal.
• Skipping edge cases. Invalid input handling is explicitly evaluated in machine-coding.
• Undefendable projects. Listing work you cannot explain in depth backfires.
• Generic "why Flipkart". Tie your motivation to its e-commerce scale and engineering problems.

Preparation Timeline (6 to 8 Weeks)

• Weeks 1 to 2: Foundations. Arrays, strings, hashing, greedy. Solve 30 to 40 problems and narrate aloud.
• Weeks 3 to 4: Core DSA plus machine coding. Trees, graphs, DP, and three small clean-design builds (expense splitter, parking lot, snake and ladder).
• Weeks 5 to 6: Design and projects. LLD practice and a review of resume projects.
• Weeks 7 to 8: Mocks. Timed mock DSA and machine-coding sessions, plus a specific "why Flipkart" answer.

Related Resources

• Flipkart online assessment 2026, the OA pattern and worked solutions before the loop
• Flipkart interview questions 2026, commonly asked questions across rounds
• Flipkart placement papers 2026, solved past-drive papers
• System design interview questions freshers 2026, design fundamentals for the design round
• 7-day coding round crash plan 2026, last-week prep
• Off campus placement guide 2026, the master off-campus guide

FAQs: Flipkart Hiring Process 2026

Q: How many rounds does Flipkart have for freshers?

Candidate reports for 2023 to 2025 describe an OA, a machine-coding round, one to two DSA interviews, sometimes a design round, and an HR round. The exact count varies by role and drive; your recruiter confirms your loop.

Q: What is the Flipkart machine-coding round?

It is a round where you build a small, working, runnable program from a problem statement (such as an expense splitter or parking lot) in roughly 90 to 120 minutes. It evaluates clean object-oriented design, working code, extensibility, and edge-case handling, not a single algorithm.

Q: What are Runway and GiRL at Flipkart?

Runway is an off-campus hiring drive Flipkart has used to source engineers, including from non-traditional backgrounds. GiRL (Girls Wanna Code) is a women-only hiring and mentorship program with a coding contest as its entry filter. Both use the same DSA and machine-coding competencies as the standard process.

Q: How should I prepare for the machine-coding round?

Practise building three to five classic design problems (parking lot, expense sharing, elevator, library, snake and ladder) end to end in your strongest language, under a timer. Focus on clean class modelling, SOLID principles, working code, and graceful handling of invalid input.

Q: Does Flipkart ask system design to freshers?

For freshers, the design component is usually low-level design (class modelling) rather than full distributed-systems design. Candidates with some experience may get a high-level design discussion. Prepare LLD basics and one or two simple service sketches.

Q: What does the Flipkart HR round focus on?

Motivation, fit, your projects, and behavioural questions like handling deadlines and disagreement. Prepare real STAR examples and a specific "why Flipkart" answer tied to its e-commerce scale and engineering challenges.

Q: How long is the Flipkart machine-coding round?

Candidate reports cite roughly 90 to 120 minutes to build a working, runnable solution from a problem statement. The time pressure is real, so practise building classic design problems end to end under a timer beforehand.

Q: Can I use any IDE in the Flipkart machine-coding round?

Candidate reports vary by drive; some allow your own setup and some use a shared environment. Practise in a plain editor in your strongest language so you are not dependent on autocomplete, and confirm the setup with your recruiter.

Q: How long does the Flipkart hiring process take?

It varies by drive and volume. Candidate reports describe an OA, a machine-coding round, one to two DSA interviews, sometimes a design round, and an HR round over a few weeks. Your recruiter gives a timeline once you clear the OA.