Tech Mahindra Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand about Tech Mahindra: this is a mass-recruitment pipeline, so the game is passing clear gates, not impressing with rare depth.

• They hire thousands of trainable graduates per batch.
• The interviewer is not looking for a star. They are looking for someone they can safely put on a client account in six months.
• Be the reliable, clear, coachable candidate and you pass.
• Be the clever-but-erratic one and you get screened out by a cutoff you never see.

2Getting the call (the part most guides skip)#

For a services company, getting the call is less about referrals and more about being in the right pipeline and registering correctly. I have watched strong candidates miss a drive entirely because they saw the placement notice two hours after the slots closed. The logistics are half the battle here.

Campus route (the easiest path if it exists).

• If Tech Mahindra visits your college, use it.
• Watch your placement cell notices and register on time.
• Meet eligibility: often a minimum aggregate like 60% or 6.0-6.5 CGPA across 10th, 12th, and graduation, and typically no or limited active backlogs.
• Confirm the exact numbers with your placement coordinator before the drive, not after you have been marked ineligible. Specifics vary by batch.

Off-campus route.

• Tech Mahindra runs off-campus drives and posts openings on its careers portal and common job platforms.
• They also hire through pooled graduate-hiring tests.
• Create a profile, keep your resume and marksheets ready as PDFs.
• Apply the moment a drive opens: slots fill within hours, not days.

Test registration.

• For pooled or national tests, you register, pick a slot, and sit a proctored online assessment.
• Register early for a morning slot, when your head is fresh.
• Use a stable laptop and a wired or strong internet connection.
• Read the instructions on allowed materials and proctoring. A dropped connection mid-test is treated as your problem, not theirs.

Referrals.

• An employee referral can help your resume surface for lateral or specific openings.
• For the standard fresher drive, the test result is the main gate.
• Do not count on a referral to carry a weak score.

Resume rules for freshers.

• One page, no exceptions.
• Order: education, then projects, then skills, then internships and certifications.
• Plain single-column formatting an ATS can read: no tables, no sidebars, no photos, no icons.
• Save as PDF with a sensible file name like Firstname_Lastname_Resume.pdf.

Weak vs strong bullets.

• Weak: "Made a website for college."
• Strong, quantified: "Built a student-attendance web app (React + Node + MySQL) used by 3 classes of about 120 students, cutting manual roll-call time by about 70%."
• The difference is not the English. It is the numbers and the ownership.
• Every bullet should answer: what did you build, with what, and what changed because of it.

ATS keywords to mirror from the job post.

• The languages you actually know (Java, Python, C++), SQL and DBMS, data structures, OOP, HTML/CSS/JavaScript, Git, and any cloud or specialization the posting names.
• Only list what you can defend. If you write "Spring Boot," assume you will be asked to explain a controller and dependency injection. If you cannot, that single line just cost you the round.

3The loop at a glance#

The rounds are consistent in shape, even if names and order drift between batches.

Read the table, then read this.

• Exact names and order shift between batches and whether you come through campus, off-campus, or a pooled national test.
• Some drives collapse the technical and HR rounds into one sitting.
• Treat this as the typical shape, not a guarantee.
• Ask your coordinator or recruiter what your specific drive looks like.

4The online test, aptitude and pseudo-code patterns, not problems#

This is the most important gate, and the one that eliminates the most people. It is usually sectional and timed, and for many drives it is adaptive or has section cutoffs.

Quantitative aptitude (reward memorized shortcuts).

• High-frequency topics: percentages, profit and loss, ratio and proportion, averages, time-speed-distance, time and work, simple and compound interest, permutations and combinations, probability, number systems (HCF and LCM, divisibility, remainders), and data interpretation on tables and charts.
• These are standard topics, so drilling them builds real speed.
• Know cold: the net-percentage trick for successive discounts, the "work done per day" setup for time-and-work, and the base-10 divisibility rules.

Logical reasoning (learn the setup once, then automate it).

• Series (number and letter), coding-decoding, blood relations, directions, seating arrangement, syllogisms, puzzles, data sufficiency, and pattern or figure questions.
• Learn the setup method for each type once, then practice until the setup is automatic.
• For seating and puzzles, draw the grid first every single time instead of holding it in your head. That one habit saves you from the silly mistakes that eat a whole section.

Verbal English (do not skip it like everyone else does).

• Reading comprehension, sentence correction, error spotting, synonyms and antonyms, fill in the blanks, and para-jumbles.
• Communication is central at Tech Mahindra, so this section is not optional.
• A below-cutoff verbal score ends your drive just as hard as a weak coding score.

Coding and pseudo-code (two real skills).

• Expect a pseudo-code section (predict the output, find the error, or complete the logic) plus one or two hands-on coding problems in a language of your choice.
• Problems lean easy to lower-medium: string manipulation, arrays, loops, basic recursion, prime, factorial and Fibonacci, pattern printing, searching and sorting basics, and simple math.
• The two skills that matter: reading pseudo-code line by line, and translating a plain-English requirement into working code without over-thinking it.

Here is the shape of the coding questions you should be able to write in your sleep:

# Reverse a string without a built-in reverse
def reverse_str(s):
    result = ""
    for ch in s:
        result = ch + result
    return result

# Check prime, the exact kind of warm-up they ask
def is_prime(n):
    if n < 2:
        return False
    i = 2
    while i * i <= n:
        if n % i == 0:
            return False
        i += 1
    return True

How to practice.

• Do daily timed sets. Fix a block each on quant, logical, verbal, and coding.
• Track time per question, not just accuracy. Accuracy with no speed fails a timed sectional test.
• Write real, compiling solutions for 40-60 easy problems covering strings, arrays, loops, and recursion.
• Dry-run pseudo-code on paper, tracing variable values in a small table. Output-prediction questions are pure tracing discipline.

How to win the test.

• Attempt easy questions first. Bank the sure marks before the hard ones, because every question is worth the same.
• Watch for sectional cutoffs. A strong total will not save you if one section is below the line.
• For coding, read the exact input and output format, handle the obvious edge cases (empty input, single element, zero, negative numbers), and test on the given sample before you submit.
• Keep a calm steady pace. Two minutes stuck on one question can cost five easier ones. When you feel yourself stalling, flag it and move on.

5CS fundamentals, the technical round core#

For freshers there is usually no heavyweight system design. The technical interview probes core computer-science fundamentals plus your own projects. Be ready to explain, not just define. The interviewer can smell a memorized textbook line from across the table, and the follow-up ("okay, give me an example from your own code") is where memorizers fall apart.

OOP.

• The four pillars (encapsulation, abstraction, inheritance, polymorphism), class vs object, overloading vs overriding, abstract class vs interface, and a real example from your own code.
• Be ready to explain overloading vs overriding with a one-line snippet, not just the words. That exact pair is asked constantly.

DBMS and SQL.

• Primary vs foreign key, normalization (1NF to 3NF at a high level), joins (inner, left, right), the ACID properties, and simple query writing.
• Expect to write a SELECT with a WHERE, a JOIN, or a GROUP BY on the spot.
• Practice this one until it is reflex:

-- Second highest salary, the classic fresher SQL question
SELECT MAX(salary) AS second_highest
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

Operating systems.

• Process vs thread.
• Deadlock and its four conditions (mutual exclusion, hold and wait, no preemption, circular wait).
• Basic scheduling ideas like round robin and FCFS.
• Paging and virtual memory at a concept level.

Computer networks.

• OSI vs TCP/IP layers at a high level.
• TCP vs UDP and when you would use each.
• What happens when you type a URL and press enter (DNS lookup, then request, then response).
• Basic HTTP vs HTTPS.
• The URL question is a favorite because it shows how structured your thinking is, so practice walking it start to finish.

Data structures.

• Arrays vs linked lists, stack vs queue, trees and hashing basics, and the time complexity of common operations.
• Know Big-O at a comfortable, explainable level: array index lookup is O(1), linear search is O(n), binary search on a sorted array is O(log n).
• Say why, not just recite the letters.

Your projects (where many freshers win or lose).

• For each project, say in two minutes: the problem, your exact role, the tech stack and why you chose it, one hard bug you fixed and how, and one thing you would improve.
• Interviewers probe your project to see if you built it or just wrote your name on a group submission.
• If you cannot explain a design choice you made, that is a loud signal you did not make it.

6Behavioral and culture fit#

What HR is actually scoring.

• Tech Mahindra's culture is often summed up by its "Rise" philosophy: rising to meet change, growing, and doing right by customers and community.
• Its core values center on good corporate citizenship, integrity, customer focus, and respect for people.
• You do not need to recite these, and reciting them word for word actually sounds rehearsed.
• HR is looking for someone honest, coachable, a team player, and genuinely ready to commit and relocate.
• They have been burned by candidates who accept, train for months, then leave for a startup. Stability signals matter more than you would guess.

Common HR and behavioral prompts.

• Tell me about yourself (keep it to 60-90 seconds: education, one project, one strength, why this role).
• Why Tech Mahindra, and why IT services?
• Are you comfortable relocating and with rotational shifts?
• A time you worked in a team, handled conflict, or faced a deadline.
• Your strengths and one real weakness, with how you are improving it.
• Where do you see yourself in a few years?

Build your stories first.

• Write 4-6 STAR stories (Situation, Task, Action, Result) from college projects, internships, fests, or team events.
• Always land the Result with a number.

One worked STAR example.

• Situation: In my final-year team project, our group of four fell two weeks behind on a library-management app because two members had exam clashes.
• Task: As the de facto coordinator, I had to get us back on schedule without overloading anyone.
• Action: I broke the remaining work into small daily tasks, took on the database and API layer myself, set up a shared tracker, and ran a 15-minute daily sync so blockers surfaced early.
• Result: We submitted two days before the deadline, scored the highest grade in our batch for the project, and the daily-sync habit was adopted by two other groups.

Why that answer lands.

• It is specific, it owns a real decision, and the result has three concrete outcomes.
• "We worked hard and finished it" is not a STAR story, it is a shrug.

How you say it counts as much as what you say.

• Tech Mahindra values communication heavily.
• Clear structure, steady pace, and no filler like "basically" and "you know."
• If you speed up when nervous, practice deliberately slowing down.
• On a client call, a calm clear voice is the product.

7Your prep plan#

Pick the plan that matches the time you actually have left.

4-week plan

• Week 1: Quant fundamentals (percentages, ratios, time-speed-distance, interest) plus daily verbal reading. Start 5 easy coding problems per day.
• Week 2: Logical reasoning (series, puzzles, seating, syllogisms) plus 5 more coding problems per day. Begin CS fundamentals (OOP, DBMS).
• Week 3: Full timed mock tests twice this week. Finish OS and CN fundamentals. Practice SQL queries and pseudo-code output questions.
• Week 4: Two more full mocks, polish all project explanations, write and rehearse 5 STAR stories, and do mock HR and communication rounds out loud with a friend who will interrupt you.

2-week plan

• Days 1-4: Drill the highest-frequency quant and logical topics. 8-10 easy coding problems total.
• Days 5-8: CS fundamentals (OOP, DBMS, OS, CN) and SQL plus pseudo-code practice.
• Days 9-11: Two full timed mock tests. Fix your single weakest section.
• Days 12-14: STAR stories, project explanations, and spoken-English and HR rehearsal.

2-day crash plan

• Day 1: One timed aptitude mock to find weak spots. Revise formula sheets for quant. Skim OOP, DBMS, OS, CN one-liners. Solve 10 easy coding problems.
• Day 2: One coding plus pseudo-code set. Rehearse "tell me about yourself," your top project, and 3 STAR stories out loud. Prep answers on relocation and shifts. Sleep early, because a rested head clears a sectional cutoff better than one more hour of cramming.

8Why people get rejected at Tech Mahindra#

The rejection reasons are predictable, which means they are preventable.

1. Failing a section cutoff. Strong overall but one section (often quant or English) below the line. The single most common reason, and candidates often never learn which section killed them.
2. Weak communication. Nervous, mumbled, or overly memorized answers at a company that prizes clear spoken English for client-facing work.
3. Shaky fundamentals. Can name the OOP pillars but cannot give an example, or cannot write a simple SELECT with a WHERE clause.
4. Cannot defend the resume. Listing skills or projects they cannot explain under light questioning. One undefendable line can sink the whole round.
5. Commitment red flags. Signaling you only want to join until a "better" offer shows up, or refusing relocation and shifts without a real reason.
6. Pace and nerves in the test. Freezing on one hard question and running out of time on the easy ones you would have gotten right.

9The offer, comp and negotiation#

What the number looks like.

• For freshers, Tech Mahindra pays roughly Rs 3.5-7 LPA depending on role and track.
• A standard associate or trainee offer tends to sit in the lower part of that range, around Rs 3.5-4.5 LPA.
• Premium or digital and specialized tracks (sometimes gated by a higher test score or extra rounds) sit higher, toward the Rs 6-7 LPA end.
• The package is usually fixed base plus statutory components (PF, gratuity) and modest allowances.
• Large joining or performance bonuses are uncommon at the entry level, so read the offer as mostly base.

Negotiation tips for this context.

• Freshers have limited leverage on base, especially in campus and pooled batches where bands are standardized across the whole intake. Set your expectations accordingly so you do not sour the relationship over a number that cannot move.
• Aim for the premium or digital track if it is offered. Scoring well enough to qualify for a higher band is the realistic way to raise your number, far more than negotiating after the fact. The lever is your test score, not your charm in the HR call.
• If you have a competing offer or a strong specialization, you can politely ask whether a higher band or role is possible. Be respectful and never bluff, because recruiters in this space talk to each other and a fake competing offer gets found out. For most freshers, accepting promptly and performing well to earn an early revision or an internal move is the stronger play.

Want this turned into a personalized, dated prep schedule that counts down to your exact interview date? Build one and start checking off a little every day. Consistent, honest preparation is what gets freshers through this process.