Infosys Fresher interview: process, rounds and questions

Written by Mentari as typical of this process — not a record of questions Infosys has asked. Each comes with the follow-up a good interviewer asks next and what they listen for in the answer. Scenario details are our framing, chosen to fit Infosys’s sector.

1. 01 Introduce yourself — and then tell me which line of your résumé you are least confident about.

   Follow-up · Let’s start there. Explain it to me as if I will test you on it.

   Listens for · Honesty about the thin spot, and enough knowledge to survive the question that follows.

2. 02 What was your role in the internship project, and what did you ship?

   Follow-up · What would have happened to the project if you had been absent for a month?

   Listens for · A concrete, individual contribution with an outcome; an honest answer about replaceability.

3. 03 Write a query that returns the fifth-highest salary.

   Follow-up · Two employees share the fifth-highest salary. What does your query return, and is that what the question asked?

   Listens for · A deliberate choice between DENSE_RANK and LIMIT/OFFSET, and awareness of ties.

Compiled from 10 candidate reports (2024–2026) and the official hiring page. Where reports differ, the range is shown rather than one number.

SE online assessment — reported 2026 pattern — Reported by a preparation site in May 2026 for the standard SE-style test. 2024 candidates describe additional essay-writing, pattern-solving, code-debugging and gamified components, so expect more than three sections at a given drive. Infosys publishes no pattern.^12,4,5

1. Find out which route your drive is — SE, DSE or SP — before preparing anything else. The two routes test different things; a 2026 SP/DSE candidate was asked event-loop ordering and system design, an SE candidate was asked about Pandas and teamwork.
2. SE: sit timed mixed-section tests with heavy verbal weight, and practise a short essay and code-reading questions. The reported 2026 pattern gives verbal ability 40 of 65 questions; 2024 drives added essay, pattern and debugging tasks.
3. SP/DSE: solve two medium and one hard problem a day, read constraints first, and know a sieve. The 2026 candidate hit a time-limit on a pair-counting problem solved by brute force; the advice from that account is constraints and number theory.
4. Strip the résumé to skills you can be questioned on for ten minutes each. Every account says the technical questions came from the résumé; selected candidates credit fluency in exactly what they listed.
5. Revise OS scheduling and deadlocks, ACID, SOLID, and one SQL ranking query. These recur in the SP/DSE interviews and are the fundamentals SE interviewers reach for when a résumé lists DBMS.
6. Prepare a ten-minute system-design answer for a small system, scaled to the number the interviewer gives. A 2026 SP/DSE interview asked for a ticketing system at about fifty users; the candidate’s advice is to scale the design to the stated load.
7. For the SE interview, rehearse a conversational opening and two teamwork stories. The SE interview is described as informal at first and as assessing behaviour, communication and confidence as much as technicals.

What Infosys says it assesses

• HackWithInfy Round 1 is "a virtual contest designed to test your skills"; Round 2 is "the real coding challenge in a face-to-face contest" for a place at the grand finale and a PPI opportunity²
• Graduate routes named officially: InfyTQ as a learning and engagement platform, Power Programmers as an "exclusive coding unit", HackWithInfy as the coding competition¹

What candidates report being probed on

• Every technology named on the résumé — Java and OOP, exception handling, threads, SQL, HTML/CSS/JavaScript, NumPy and Pandas^11,4
• A live coding problem with a hard variant (XOR-and-prime pair counting; "split array largest sum"; island counting)^7,8,6
• OS scheduling and deadlock handling; ACID and SOLID; JavaScript event-loop ordering^7,6
• Java basics, OOP, DBMS joins and normalisation in a conversational, non-adversarial interview (DSE via HackWithInfy)⁹
• SQL such as the fifth-highest salary; DBMS fundamentals^6,11
• A small system-design question scaled to the load the interviewer states⁷
• Teamwork challenges, strengths and weaknesses, project role, relocation^4,11

Infosys is two different interviews wearing one logo. The SE route is reported as an aptitude-and-verbal test with a steep cut — one 2024 campus drive took 780 students to 103 interviews — followed by a short, friendly conversation that walks the résumé: candidates describe interviewers starting informally, asking about projects and internships, and checking that the skills listed are real. The SP and DSE route is reported as the opposite: a coding assessment, in one 2026 drive a proctored DSA round in a lab, then a long technical interview with a timed coding task, operating-systems and database fundamentals, language internals and a small design question, lasting up to ninety minutes.

What the routes share is that the résumé sets the questions. Across SE and SP accounts the technical part is described as "whatever you listed" — Java if you wrote Java, Pandas if you wrote Pandas, machine learning if you claimed a model — and the candidates who were selected say the advantage was being fluent in exactly those skills rather than in a general syllabus. A fresher who pads the résumé for the SE route creates their own hardest questions.

Where the sources disagree

The official material and the reports describe different things. Infosys’s pages document HackWithInfy in detail and say nothing about the SE, DSE or SP campus processes; the two drive notices we found (a 2025 Systems Engineer Trainee letter and a December 2025 off-campus letter hosted by a university) give eligibility and venues but not the test pattern. The reports disagree with each other mostly by route. SE accounts from late 2024 describe a two-hour assessment with aptitude, verbal, essay, pattern-solving and debugging components and an interview lasting fifteen to forty-five minutes; a preparation site in May 2026 gives a cleaner 65-question, 95-minute, three-section pattern for the same test. SP and DSE accounts from August 2024 and October 2026 describe three coding problems, a face-to-face interview with a hard algorithmic question, and — in 2026 — an added proctored DSA round, which suggests the coding route has become longer. Eligibility figures of 60% / 6.0 CGPA appear consistently for SE in 2025 notices, with 65% cited for some SP/DSE drives; nothing official on infosys.com states either.

4. 04 Given an array and K, count the pairs whose XOR is less than K and whose sum is prime — talk through your approach before coding.

   Follow-up · Your solution is O(n²) with a primality check inside. The array has 10⁵ elements. What do you change first?

   Listens for · Reads constraints before coding; reaches for a sieve and reduces the inner work rather than optimising the primality test.

5. 05 In what order do these print: a synchronous log, a resolved promise’s .then, and a setTimeout with 0 delay?

   Follow-up · Why does the promise beat the timeout even though both are "asynchronous"?

   Listens for · Microtask versus macrotask queues, explained in words rather than recited as an order.

6. 06 Explain a deadlock and the four conditions for it, using a system you have actually built or used.

   Follow-up · Which condition would you break in that system, and what would it cost?

   Listens for · Conditions applied to a real example; a trade-off rather than a definition.

7. 07 Design a ticketing system for a college fest with about fifty concurrent users.

   Follow-up · Now it is fifty thousand, for ten minutes, when registration opens. What breaks first?

   Listens for · A design scaled to the stated load, then the right first casualty — the database write path or the lack of a queue — when the load changes.

8. 08 What is the difference between an abstract class and an interface, in the language you listed?

   Follow-up · Show me where in your project you used one, and whether the other would have been better.

   Listens for · A grounded example; the willingness to say "the other would have been better".

9. 09 Tell me about a disagreement in your project team and how it ended.

   Follow-up · What would the other person say you did wrong?

   Listens for · A real disagreement with a fair account of the other side; not a story where everyone agreed.

10. 10 Are you willing to relocate to any Infosys development centre and to sign the service agreement?

    Follow-up · You mentioned plans for a master’s. How does that fit with a service agreement?

    Listens for · Consistency across answers; a plain yes, or a plain condition.

11. 11 Why Infosys, and why this role rather than a product company?

    Follow-up · What do you know about how an SE is trained and placed in the first year?

    Listens for · Knows about Mysore training and project allocation; a reason that is not "big brand".

Your résumé lists Pandas. Tell me what you actually did with it.

Weak · "I used Pandas for data cleaning and analysis in my project, like reading CSV files and handling missing values, and then I built the model."

Stronger · "The dataset had 40,000 rows with about 12% missing in the income column. I checked whether the missing rows were random — they were mostly from one city — so I did not just fill the mean; I added a flag column and imputed by city median. The model’s accuracy barely moved, but the per-city error dropped, which is what the project was about."

Why the follow-up lands · The interviewer asks "why did the overall accuracy barely move?" The strong answer has the reasoning ready — most rows were unaffected; the weak one has only the words "data cleaning".

Illustrative — yours must be true.

An Infosys drive’s shape depends on the role in the invitation: SE drives are decided by an aptitude-and-verbal test with a steep cut and a short résumé-led interview, SP/DSE drives by coding assessments and a long technical interview. Eligibility in 2025 notices was 60% in Class 10 and 12 and 6.0 CGPA with no active backlogs for SE, higher for some SP/DSE drives; the notice is controlling.

For the SE route, Mentari’s HR-round mock rehearses the short résumé-led interview — projects, the skills listed, teamwork and relocation — for the whole shortlisted batch; for SP/DSE, the software-engineer mock covers fundamentals and project depth aloud. Run Infosys-pattern mocks for a whole batch.

• HR round mock interview for campus placements
• Software engineer mock interview
• TCS interview
• Accenture interview
• Tell Me About Yourself (Freshers) + 3 Follow-ups
• STAR Method Answers That Survive Follow-ups
• All company guides →

1. Graduates — careers — Infosys (official) · official · accessed 2026-10-23 · names InfyTQ, Power Programmers and HackWithInfy; no process
2. HackWithInfy 2026 — Infosys (official) · official · accessed 2026-10-23 · the only official process description: two coding rounds and a grand finale, with a PPI opportunity
3. Infosys off-campus drive 2025 — Systems Engineer Trainee notice — Infosys letter, as circulated by freshersvoice.com · official · accessed 2026-10-23 · eligibility and in-person venues; no test pattern
4. Infosys interview experience 2024 — System Engineer, on-campus — GeeksforGeeks · candidate report, 2024-10 · accessed 2026-10-23 · 780 sat, 103 interviewed; interview the next day
5. Infosys interview experience, on-campus, December 2024 (SE) — Naukri Campus · candidate report, 2024-12 · accessed 2026-10-23 · two-hour assessment; short interview in January 2025
6. Infosys interview experience — Specialist Programmer, on-campus, 2025 batch — GeeksforGeeks · candidate report, 2024-08 · accessed 2026-10-23 · assessment in August; interview at Infosys Noida
7. Infosys SP/DSE off-campus interview experience — fresher, 2026 batch — takeUforward community · candidate report, 2026-10 · accessed 2026-10-23 · three-problem OA, proctored DSA round, 25-minute coding task in interview
8. Infosys interview experience — Power Programmer, IIIT Delhi, April 2024 — Naukri Code360 · candidate report, 2024-04 · accessed 2026-10-23 · older drive: three-hour coding test and a 90-minute interview; cited for the interview-length range
9. Infosys interview experience, June 2025 — Digital Specialist Engineer via HackWithInfy — Naukri Code360 · candidate report, 2025-06 · accessed 2026-10-23 · three-problem online round, 45-minute onsite coding test, technical interview on Java, OOP, DBMS, SQL
10. Infosys interview experience, on-campus, December 2025 (SE) — Naukri Code360 · candidate report, 2025-12 · accessed 2026-10-23 · online assessment, campus interview; fundamentals, project explanation, communication
11. Infosys interview experience for freshers — GeeksforGeeks · candidate report, 2024-05 · accessed 2026-10-23 · older account: separate technical and HR rounds; cited for topics only
12. Infosys recruitment pattern and important topics (May 2026) — FACE Prep · candidate report, 2026-05 · accessed 2026-10-23 · preparation-site compilation; the 65-question, 95-minute SE pattern
13. Infosys eligibility criteria — PrepInsta · candidate report · accessed 2026-10-23 · preparation-site compilation of drive criteria

Verified October 2026 by Sumit Mishra, Mentari founder. Spotted an error, or represent Infosys? Write to [email protected] — we acknowledge within two working days and correct or remove a disputed statement within 72 hours.

Mentari is not affiliated with Infosys. This page is pattern-based, compiled from the public sources listed, and is not insider information. Candidate-reported details are reproduced as patterns only, in our own words.