Tech Mahindra Full Stack Fresher Interview 2026: Rounds &

The candidate's round-by-round experience

As posted on GeeksforGeeks, a fresher applying for a Full Stack Developer role at Tech Mahindra went through a process that the candidate later called "one of the most difficult interviews I ever faced." The outcome was a rejection, which makes this account unusually valuable: most published interview experiences are success stories, and a transparent rejection write-up tells you exactly where candidates fall short.

Round 1 was an online coding contest hosted on HackerEarth. It contained two problems rated medium-hard by the candidate's own assessment. The candidate solved only one of the two problems and was still shortlisted for the next round within approximately a week. This is an important signal: partial solving in the coding round did not automatically disqualify this candidate, at least in this particular drive. However, shortlisting criteria can vary by batch and role, so treat this as one data point rather than a rule.

Round 2 was the technical interview, also conducted via HackerEarth. What made this round distinctive was its panel structure. Four different panelists joined the interview, each covering a different technical domain. The candidate moved from one panelist to the next, answering domain-specific questions. The frontend or React panelist was the most thorough, the OOP panelist asked conceptual software-engineering questions, the database panelist posed a single SQL query question, and the backend panelist's questions went entirely unanswered.

The candidate's self-reported performance was candid. When asked to self-rate OOP knowledge, the candidate said 7 out of 10. The OOP panelist then probed class definitions, composition vs association, encapsulation, and inheritance. The database panelist asked one SQL query question that the candidate could not solve. The backend panelist's questions were met with silence from the candidate, who wrote "I couldn't even answer a single question" in the public write-up. The final verdict was REJECTED.

No CTC, package figure, or HR round details were mentioned in the original account. This means the source does not give us salary information for this role, and we will not invent one. If you are looking for Tech Mahindra fresher compensation data, check the official Tech Mahindra careers page or crowd-sourced salary platforms, and always treat those figures as individually reported.

Round breakdown and question taxonomy

The table below consolidates what the candidate reported for each round and panelist domain. Every question listed here is candidate-reported for this one specific Tech Mahindra fresher drive, as posted on GeeksforGeeks.

A few patterns stand out from this breakdown. First, Tech Mahindra treated this full-stack interview as a genuine full-stack evaluation: you cannot coast on frontend alone, because a separate panelist will test backend and database skills. Second, the frontend panelist asked the deepest and broadest set of questions, suggesting React proficiency is weighted heavily for this role. Third, the OOP panelist used a self-rating gambit, asking the candidate to score themselves before probing deeper. This is a common interviewing technique: if you say 8/10, expect harder follow-ups than if you say 5/10.

The prep playbook for a Tech Mahindra full-stack fresher drive

Based on the domains covered in this candidate-reported interview, here is a focused preparation checklist. These are the topics one specific panel tested, so they are a starting point, not a guaranteed syllabus.

React and frontend preparation

The candidate faced the most questions in this area. Prioritize:

• Virtual DOM: what it is, why it exists, how reconciliation works.
• Props vs state: definitions, mutation rules, when to use each.
• useState and useEffect hooks: common patterns, dependency arrays, cleanup functions.
• Class vs functional components: lifecycle methods vs hooks equivalents.
• Higher-order functions in JavaScript: map, filter, reduce, and custom HOFs.
• Context API and useContext: write the pseudo-code, not just the theory.
• Redux fundamentals: actions, reducers, store, and when Redux is preferred over Context.

OOP preparation

The candidate self-rated 7/10 and was then tested on:

• Class definitions and object instantiation.
• Composition vs association: know the difference and give code examples.
• Encapsulation: how it is enforced in Java, Python, or C++.
• Inheritance: single, multiple, multilevel, and the diamond problem.

Be honest in your self-rating. If you say 7/10, the panelist will go deeper than if you say 5/10. Under-rating slightly can work in your favor by setting a lower expectation threshold.

Database preparation

The candidate could not solve the single SQL query question. For a full-stack role, at minimum prepare:

• Joins: inner, left, right, full outer.
• Group by and having clauses.
• Subqueries vs correlated subqueries.
• Window functions if you have time.
• Basic normalization and indexing concepts.

Backend preparation

The candidate answered zero backend questions. This is the starkest failure point in the entire interview. For a full-stack fresher role at Tech Mahindra, prepare at least:

• REST API design: HTTP methods, status codes, idempotency.
• Authentication and authorization basics: JWT, session vs token.
• One backend framework in depth: Express.js, Spring Boot, or Django.
• Middleware concepts and request lifecycle.
• Basic deployment and environment variable handling.

Common mistakes and red flags

• Coasting on frontend alone. This candidate answered most React questions but failed backend entirely and was rejected. A full-stack panel will test all layers, not just the one you are strongest in.
• Over-rating yourself in self-assessment. Saying 7/10 on OOP invited deeper probing. If you are genuinely at 5/10, say 5/10 and steer the conversation toward what you do know well.
• Skipping SQL practice. One SQL query question went unanswered and contributed to the rejection. Even a single unsolved database question can tip the verdict in a tight interview.
• Not preparing pseudo-code tasks. The candidate was asked to write pseudo-code for useContext, not just explain it. Practice writing hook pseudo-code by hand.
• Ignoring the backend panelist entirely. The candidate wrote they could not answer a single backend question. If you apply for a full-stack role with weak backend knowledge, at least prepare foundational REST and API concepts.
• Treating one experience as a universal pattern. This is one candidate's self-reported experience for one drive. Tech Mahindra's process may differ by campus, batch, or role. Always confirm on the official Tech Mahindra careers page.

Real-world data points

All figures below are candidate-reported, as posted on GeeksforGeeks, for this specific Tech Mahindra fresher full-stack drive.

• 2 total rounds, per the candidate's account.
• 2 medium-hard coding problems in Round 1, per the candidate's assessment.
• 1 of 2 coding problems solved by the candidate in Round 1.
• Approximately 1 week between Round 1 and Round 2 shortlisting.
• 4 panelists in the technical interview round, each covering a different domain.
• 1 SQL query question asked by the database panelist, unsolved by the candidate.
• 0 backend questions answered by the candidate.
• Final verdict: REJECTED.
• No CTC or package figure was reported in the source account.

Sources & credits

• https://www.geeksforgeeks.org/tech-mahindra-interview-experience-for-full-stack-developer-fresher/