Infosys Recruitment Process 2026: Online Test, Coding Round and Interview Questions

A warning first. Infosys doesn’t publish a fixed test pattern, and details change between drives and between campus and off-campus hiring. What follows is the pattern candidates and placement sites report for recent drives. Your test invitation and the instructions on screen are the final word.

The three fresher roles

Most freshers join as a Systems Engineer. Stronger coders can be hired straight into the higher-paying digital roles. The pay below is what’s commonly reported for recent batches, not a figure Infosys publishes:

Reported figures for 2026 hiring. They vary by drive and by level.

There are a few ways in: campus placement drives, off-campus registration on the Infosys careers site when a drive opens, and HackWithInfy, Infosys’s coding contest, where strong performers are invited to interview for SP and DSE roles. Whatever the route, the rounds look broadly the same.

Round 1: the online test for Systems Engineer

The SE test is mostly aptitude, with some logic that looks like programming. Candidates report these sections, about 100 minutes in total:

• Reasoning ability: seating arrangements, blood relations, syllogisms, coding-decoding, data sufficiency.
• Mathematical ability: percentages, profit and loss, time and work, probability, permutations, number series.
• Verbal ability: reading comprehension, sentence correction, fill in the blanks, paragraph ordering.
• Pseudocode: read a short piece of code and say what it prints. Loops, recursion and bit operations are favourites.
• Puzzle solving: a few longer logic puzzles that take time to set up.

Sections are timed separately, and sectional cut-offs are commonly reported, so a strong maths score won’t carry a weak verbal one. Read the on-screen instructions for negative marking; reports differ between drives.

Round 1 for SP and DSE: the coding assessment

For the digital roles the test is coding. Recent candidates commonly report three problems in about three hours, in rising difficulty:

• Problem 1, easy to medium: arrays, strings, greedy choices, a little maths. Solve it fully and quickly.
• Problem 2, medium: usually dynamic programming or a greedy idea with sorting, sometimes binary search on the answer.
• Problem 3, hard: harder dynamic programming, graphs (shortest paths, trees, DFS with extra state) or problems that need a clever observation. Solving this one is what tends to separate SP from DSE.

Scoring is by hidden test cases, so partial solutions earn partial marks. A correct brute force on the hard problem still passes the small cases. Always submit something that works on the samples.

Round 2: the technical interview

For SE the interview is usually one round that mixes technical and HR questions. For DSE and SP expect a longer, deeper technical round. What candidates commonly report being asked:

• Your coding test: how you approached each problem and its time complexity.
• Data structures: arrays versus linked lists, stacks and queues, hashing, trees. For SP and DSE, solve a medium problem live: reverse a linked list, detect a cycle, find the longest substring without repeats.
• OOP: the four pillars with real examples, overloading versus overriding, abstract classes versus interfaces.
• DBMS and SQL: keys, joins, normalization, indexes, and a query or two such as the second-highest salary or employees per department.
• Operating systems and networks basics: processes versus threads, deadlock, what happens when you type a URL.
• Your final-year project: what you built, what you did yourself, what broke and how you fixed it.
• Something current: cloud, AI or any technology on your resume. Don’t list what you can’t discuss.

Round 3: HR

Short and mostly about fit: tell me about yourself, why Infosys, your strengths and weaknesses, willingness to relocate and work in shifts, and questions about the training programme and your documents. Have a clear answer to relocation. Hesitation there gets noticed.

A three-week plan

Week 1: aptitude and pseudocode

One timed set a day for each of reasoning, maths and verbal. For pseudocode, trace code by hand on paper, writing down every variable after each line. That habit fixes most mistakes on output questions.

Week 2: coding patterns

Even for SE, basic coding matters in the interview. If you’re aiming for SP or DSE, spend this week on dynamic programming, greedy with sorting, binary search, and graph basics, two problems a day. If you’re stuck for 30 minutes, read the solution and solve it again from scratch the next day.

Week 3: mocks and the interview

Take full timed mocks under exam conditions. In parallel, practise interview answers out loud: your introduction, your project and the core CS questions above. Speaking an answer is a different skill from knowing it. Our four-week tech interview plan has a routine for that, and the TCS coding round guide covers editor traps that apply to Infosys tests too.

Practising the interview with Keeter

The online test is proctored. Don’t use outside help of any kind during it, AI tools included: you can be disqualified, and no offer is worth that. Follow whatever rules Infosys sets for each round.

Where AI helps is the practice before the interview. Keeter, an AI interview assistant, has a mock interview mode that plays the interviewer and asks questions out loud from your resume and the role: your project, OOP, DBMS, a short coding problem. You answer by voice and get feedback after each answer, then a report on your weak areas. The first 5 minutes are free, then it’s ₹4 a minute with no subscription.

Quick answers

Is the Infosys online test hard?

The SE test is moderate, but the time pressure and sectional cut-offs catch people out. The SP and DSE coding test is hard; most people who clear it have practised medium and hard problems for weeks.

Can I get SP or DSE if I’m hired as a Systems Engineer?

Internal upgrades have been reported, but they aren’t guaranteed. If you want a digital role, aim for it in the coding assessment or HackWithInfy.

Which language should I use in the coding round?

The one you know best. C++ and Java are fast; Python is quicker to write but slower to run, so watch loops on large inputs.

How long does Infosys take to send results?

It varies from a few days to several weeks after the interview, and joining dates depend on the batch.