Infosys Interview Guide (2026)

1Snapshot, read this first#

The one thing to understand: the test is the gate, the interview is the handshake.

• Thousands apply to a single drive, and the online assessment thins the pool from tens of thousands to a few hundred interviews.
• The interview after that confirms you, it does not re-eliminate you.
• Clear the test comfortably and hold a calm conversation about your projects and core CS, and an offer is very likely.
• So weight your effort: most of it on the test, the rest on one project you can defend for ten minutes.

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

For freshers, Infosys hires through three doors. Pick the one that fits your situation and go hard at it. Do not spread thin across all three.

On-campus. The easiest path, and the one most freshers get in through.

• Keep your CGPA above the cutoff, usually 6.0 to 6.5, often phrased as 60% across 10th, 12th, and degree with no standing backlogs.
• Backlogs matter more than people think: an active (uncleared) backlog on the day of the drive usually disqualifies you outright, even with a high CGPA.
• Attend the pre-placement talk, register on the college portal before the deadline, and treat the campus drive as your main shot of the year.

Off-campus / InfyTQ. The cleanest off-campus route if your college is not visited.

• InfyTQ is Infosys's free learning and certification platform.
• Clearing the InfyTQ certification exam can directly fast-track you to an interview.
• Register early, finish the Python or Java track plus the DBMS course, and attempt the certification well before your final semester so the result is on your profile when drives open.
• The cert is not just a sticker: the questions mirror the real test, so preparing for it is preparing for the gate.

HackWithInfy. The highest-leverage door in the whole process if you can actually code.

• Infosys's national coding contest for pre-final and final-year engineering students, run in multiple rounds.
• Round 1 is online coding; top scorers advance to further coding rounds and interviews.
• Strong performers get fast-tracked to Specialist Programmer / Power Programmer interviews, the high-pay tracks.
• This is the only door that can move your starting salary from ~3.6 LPA to ~9-11 LPA before you write a single line for the company.
• Treat it like the LeetCode-medium gate it is.

Resume rules. Recruiters skim for about 10 seconds, and the ATS reads it before any human does. Make every line earn its place. Lead with a quantified, outcome-first bullet:

Built a student attendance web app (Flask + MySQL) used by 3 classes of ~120 students; cut manual roll-call time from 10 minutes to under 1 minute per session.

Notice the pattern in that one line:

• What you built, the tech, the scale, and the measurable result. Four facts, one line.
• Avoid vague lines like "worked on a project using latest technologies." They tell the reader nothing and signal you cannot describe your own work.
• No number? Estimate an honest one (users, rows, minutes saved, accuracy) and be ready to back it up.

ATS keywords. Mirror the words Infosys uses in the posting.

• The language you know (Java / Python / C++), SQL, DBMS, Data Structures, OOP, HTML/CSS/JavaScript, Git, and the role name itself (System Engineer, Digital Specialist Engineer).
• One page, clean single-column layout, saved as a PDF, not a Word doc that reflows.
• No photo, no two-column templates, no icons or graphics that break parsers.
• A plain resume that parses beats a pretty one that gets garbled.

3The loop at a glance#

How the rounds actually run:

• For many SE candidates the technical and HR rounds are short and sometimes folded into one 30-minute conversation.
• For DSE and Specialist Programmer, expect a deeper technical round with live coding: the interviewer watches you write, asks for the time complexity, and pushes on edge cases.
• The higher the track, the more the interview looks like a real coding screen and the less it looks like a viva.

4The online test, patterns, not problems#

This is where most candidates are selected or dropped, so spend your prep time here in proportion. The assessment is broadly consistent year to year, though exact sections and weightage vary by role, drive, and testing vendor.

Quantitative Aptitude.

• Topics: percentages, profit and loss, ratios, time-speed-distance, time and work, averages, probability, permutations and combinations, number systems, simple data interpretation.
• Standard aptitude-exam fare, nothing new since 10th grade.
• The challenge is speed. Practice until a typical problem takes under a minute.
• One sum you refuse to abandon can cost you four others.

Logical Reasoning.

• Topics: series completion, blood relations, seating arrangements, syllogisms, coding-decoding, data sufficiency, puzzles.
• Seating arrangements and syllogisms eat the most time, so build a quick diagram habit for both.
• Pattern recognition plus speed is the whole game.

Verbal Ability.

• Topics: reading comprehension, sentence correction, para-jumbles, error spotting, synonyms and antonyms, fill-in-the-blanks.
• Clean grammar and a steady reading pace matter here.
• This section quietly predicts how you will do in the HR round, so do not treat it as filler.

Pseudocode. A signature Infosys section, and the one that surprises people.

• You read short snippets (C-style or language-agnostic) and predict output, trace loops, or say what the code does.
• Topics: arrays, loops, recursion, pointers, operators, operator precedence, basic data structures.
• You do not write code here, you read and reason about it, a different skill from writing code.
• Trace execution line by line on paper with a variable table.
• Watch the usual traps: post-increment versus pre-increment (i++ vs ++i), integer division truncating, off-by-one in loop bounds, and pass-by-reference changing a value you thought was safe.

Hands-on coding (DSE / SP). The higher tracks solve real code in a real editor.

• 1 to 3 programming problems with a compiler and sample test cases.
• Difficulty: easy string and array work at SE/DSE, up to medium algorithmic problems with data structures and some dynamic programming at Specialist Programmer.
• Common themes: string processing, array manipulation, hashing, two pointers, basic recursion, sorting, and simple greedy or DP for the elite track.
• Grading is on hidden test cases, so passing the two visible examples is not enough.
• Read the constraints to guess the intended complexity (n up to 10^5 means your O(n^2) loop will time out).

The 80/20 of what actually shows up in coding:

• Strings: reverse, palindrome check, count vowels, anagram check, first non-repeating character.
• Arrays: max/min, second largest without sorting, find duplicates, move zeros, prefix sums.
• Hashing: frequency count, two-sum, group by key. A HashMap solves a surprising share of these in one pass.
• Two pointers: pair with given sum in a sorted array, remove duplicates in place.
• Recursion/DP (SP only): factorial, Fibonacci with memoization, climbing stairs, coin change, longest common subsequence.

How to win the test. Four habits:

1. Manage time ruthlessly. Each section is timed separately and you usually cannot go back. Do not sink 5 minutes into one question; flag it in your head, pick the best guess, move on.
2. Trace pseudocode on paper. Write variable values at each step in a small table. Do not eyeball it, that is exactly how the traps catch you.
3. For coding, read all constraints first, decide your approach and its complexity before typing, handle edge cases (empty input, single element, duplicates, negative numbers), and test against the given examples before submitting.
4. Attempt everything you can. There is typically no heavy negative marking in the aptitude sections, so do not leave blanks you can reason toward. A reasoned guess beats an empty answer when the penalty is zero.

5CS fundamentals (the technical round core)#

For freshers, the "technical" round is mostly core CS plus your projects. You do not need system design, distributed systems, or anything exotic.

• Explain fundamentals clearly, in your own words.
• No long pause that tells the interviewer you memorized a definition yesterday.
• Cover these four areas and have one example ready for every claim you make.

Object-Oriented Programming (OOP).

• The four pillars: encapsulation, abstraction, inheritance, polymorphism, each with a real example.
• Overloading (same method name, different parameters, resolved at compile time) versus overriding (subclass redefines a parent method, resolved at runtime).
• Abstract class versus interface: a class can implement many interfaces but extend one abstract class, and an interface has no state.
• Why OOP matters for maintainability.
• Be ready to write a small class with a constructor and one method on the spot.

DBMS / SQL.

• Normalization: 1NF, 2NF, 3NF in plain words (remove repeating groups, remove partial dependencies, remove transitive dependencies).
• Primary versus foreign keys.
• Joins (inner, left, right) and what each returns when rows do not match.
• DELETE versus TRUNCATE versus DROP (row-level and rollbackable, fast full wipe, removes the table itself).
• ACID properties, and indexing basics (why an index speeds reads and slows writes).

Expect a live query. "Write SQL to find the second-highest salary" is a classic, so know it cold:

SELECT MAX(salary) AS second_highest
FROM employees
WHERE salary < (SELECT MAX(salary) FROM employees);

• Be ready to also do it with DISTINCT ... ORDER BY salary DESC LIMIT 1 OFFSET 1.
• Be ready to explain which version handles duplicate top salaries correctly.

Operating Systems.

• Process versus thread (separate memory versus shared memory within a process).
• Deadlock: the four Coffman conditions (mutual exclusion, hold and wait, no preemption, circular wait), and that breaking any one prevents it.
• Scheduling basics: FCFS, round-robin and its time quantum, SJF.
• Paging and virtual memory at a conceptual level (why we page, what a page fault is).

Computer Networks.

• OSI versus TCP/IP layers.
• TCP versus UDP (reliable, ordered, connection-based versus fast, connectionless, best-effort) and when you would pick UDP, think video calls and gaming.
• What happens when you type a URL and press enter: DNS resolves the name to an IP, TCP handshake, then an HTTP request and response.
• Basic IP and subnet ideas.

Also expect a small logic or coding question.

• Reversing a string, checking for a palindrome, finding factorial recursively, or FizzBuzz.
• Explain your approach out loud before you touch the keyboard, then write it.
• Interviewers score the thinking as much as the final code.

How to win: know your own resume cold.

• If you list a project, expect "why did you choose this tech? what was the hardest bug? what would you improve?"
• Pick one project you can discuss for ten minutes with full confidence.
• Prepare a one-line summary, the architecture in three sentences, and two honest problems you hit and how you solved them.

6Behavioral & culture fit#

Infosys's culture runs on values it has used for decades, captured in C-LIFE: Client value, Leadership by example, Integrity and transparency, Fairness, and Excellence. The company also emphasizes continuous learning, which is why InfyTQ exists and why new hires go through the Mysore training campus.

In the HR round, show the traits those values imply:

• Willingness to learn.
• Integrity and teamwork.
• Adaptability (relocation and rotational shifts are common at a services company).
• Clear, calm communication.

Typical HR questions:

• "Tell me about yourself."
• "Why Infosys?"
• "Are you comfortable relocating to Mysore, Bangalore, or Pune?"
• "Are you okay with the service agreement / training bond?"
• "Where do you see yourself in 5 years?"
• "Tell me about a time you worked in a team."

On "Why Infosys," do not recite revenue figures. Give one real reason (the structured training, the breadth of client projects, the learning platform) that sounds like you actually looked.

Prepare four short STAR stories (Situation, Task, Action, Result): teamwork, handling a deadline, resolving a conflict, and learning something new fast. Four stories cover almost every HR question you will get.

Worked STAR example, "Tell me about a time you handled a tight deadline":

• Situation: In my final-year project, our 4-person team lost a member two weeks before the submission of a working inventory-management app.
• Task: I had to absorb the database module on top of my own backend work and still ship on time.
• Action: I broke the remaining work into daily targets, paired with a teammate for an hour each evening to review code, and cut two non-essential features to protect the core flow. I set up a shared checklist so nobody duplicated effort.
• Result: We submitted a fully working app one day early, scored 9/10 from our evaluator, and the two features we deferred were added the next week for the demo, so we lost nothing.

Keep answers honest, specific, and under two minutes.

• Infosys rewards calm, clear, real stories over rehearsed buzzwords.
• A slightly imperfect true story beats a polished fake one every time.
• On relocation and shifts, the honest answer that gets you hired is yes. If you genuinely cannot relocate, raise it early rather than discover a conflict after the offer.

A slightly imperfect true story beats a polished fake one, every single round.

7Your prep plan#

4-week plan

• Week 1: Aptitude foundations, percentages, ratios, time-speed-distance, averages, probability. Solve 20 problems daily and track time per problem, aiming under a minute by the end.
• Week 2: Logical reasoning + verbal ability. Add pseudocode tracing (arrays, loops, recursion) with a written variable table each time. Daily timed drills.
• Week 3: CS fundamentals, OOP, DBMS + SQL queries, OS, networks. One topic per day, written notes in your own words, plus five SQL queries hand-written daily.
• Week 4: Full mock tests under timed conditions, polish two projects until you can talk about each for ten minutes, rehearse HR answers out loud, and do at least one mock interview with a friend who will push back.

2-week plan

• Days 1-4: Aptitude + logical reasoning speed drills.
• Days 5-7: Verbal + pseudocode output prediction.
• Days 8-10: CS fundamentals rapid review with SQL and OOP practice.
• Days 11-12: Project deep-dive and HR story prep.
• Days 13-14: Two full mock tests and a mock interview.

2-day crash plan

• Day 1 morning: One timed mock test to find weak sections, then fix your plan around the two that scored lowest.
• Day 1 afternoon: Drill your two weakest aptitude topics + 30 pseudocode snippets with a variable table for each.
• Day 1 evening: Revise OOP pillars, DBMS joins and normalization, TCP vs UDP, and write the second-highest-salary SQL from memory twice.
• Day 2 morning: Rehearse "tell me about yourself," "why Infosys," and two STAR stories out loud and timed.
• Day 2 afternoon: Re-read your resume line by line, prepare two questions to ask the interviewer, then rest and sleep early. A clear head beats one more hour of cramming.

8Why people get rejected at Infosys#

1. Failed the online test: ran out of time on aptitude or could not trace pseudocode. The single biggest cause by a wide margin, most of the pool is cut here before anyone speaks to a human.
2. Weak spoken communication: Infosys places people with clients, so hesitant or unclear English in the HR round is a real blocker, even with good technicals.
3. Cannot explain own projects: listed on the resume but unable to answer basic follow-ups, which reads as copied work and quietly tanks trust for the rest of the round.
4. Shaky fundamentals: blanked on the OOP pillars, basic SQL joins, or process versus thread. The exact things the interviewer expects you to own.
5. Unwillingness to relocate or do rotational shifts: a flat no to Mysore training or night shifts often ends the conversation, because the staffing model depends on flexibility.
6. Overconfidence or memorized answers: scripted responses that fall apart under one genuine follow-up, or talking over the interviewer. Calm and honest reads far better than slick.

9The offer, comp & negotiation#

Infosys fresher pay is largely standardized by track, so there is limited room to haggle on the number itself. The real money is in which track you qualify for, and that is decided by your test and contest performance, not by a conversation at the end.

• System Engineer (SE/SP): roughly Rs 3.6 LPA.
• Digital Specialist Engineer (DSE): roughly Rs 6.25 LPA.
• Specialist Programmer / Power Programmer: roughly Rs 9-11 LPA (through HackWithInfy or the top DSE coding track).

What the package usually includes:

• Base pay, a modest variable or performance component, and standard benefits (PF, insurance).
• A training period at Mysore.
• A service agreement in some cases, which usually asks you to stay a set period or repay a training cost if you leave early, so read that clause before you sign.

Negotiation tips for Infosys's context:

1. Negotiate the track, not the number. The highest-leverage move is qualifying for DSE or Specialist Programmer through strong test and HackWithInfy performance. That is where pay roughly doubles or triples, from ~3.6 LPA to ~6.25 LPA to ~9-11 LPA. No end-of-process ask will ever move you that much.
2. Use competing offers tactfully. If you have another services offer (TCS, Wipro, Accenture, Cognizant), politely ask whether a higher track or role is possible. Be respectful: the band is largely fixed, and pushing hard on a standardized fresher package rarely helps and can sour the start.
3. Clarify in writing. Confirm the role, the full CTC breakup (base versus variable versus retention), the location, the joining date, and any service-agreement terms before accepting, so there are no surprises at onboarding.

Want a plan tailored to your exact test date and target track? Tell me your timeline and I will build you a day-by-day prep schedule from today to interview day.