Infosys Placement Questions & Preparation Guide

The three fresher tracks

Work out which track you are aiming at before you build a study plan, because the preparation barely overlaps beyond the aptitude basics.

• ✓Systems Engineer (SE) - the volume-hiring track. Cleared through the standard online test: aptitude, reasoning, verbal and pseudocode, then interviews.
• ✓Digital Specialist Engineer (DSE) - a middle track with a harder assessment including real coding, and a higher package.
• ✓Specialist Programmer (SP) - the toughest and highest-paying fresher track, filtered largely on competitive-programming ability, commonly through HackWithInfy.

The online test sections

For the mainstream route the assessment is a familiar set of sections with one unusual member. Section names and timings vary between cycles, so confirm the current structure on the official Infosys careers portal before your slot.

• ✓Quantitative Aptitude - numbers, percentages, ratio, time & work, permutations and probability.
• ✓Logical Reasoning - series, syllogisms, puzzles, data sufficiency and arrangements.
• ✓Verbal Ability - reading comprehension, sentence correction and para jumbles.
• ✓Pseudocode - reading a C-like snippet and predicting its output or completing its logic.
• ✓Coding - two or three problems of increasing difficulty for the DSE and SP tracks.

Pseudocode: the section people underestimate

Pseudocode questions give you a short program in a C-like syntax and ask what it prints. There is no compiler and no partial credit - you have to trace execution by hand. Strong coders often lose marks here precisely because they are used to running code rather than reading it.

The technique is a dry run on paper: draw a small table of variables, step through the loop, and write the value of each variable after every iteration. Do not skim and predict. Almost every wrong answer in this section comes from an off-by-one loop bound, a mis-read post-increment, or a pass-by-reference assumption.

int x = 5, y = 0;
while (x > 0) {
    y = y + x % 3;
    x = x / 2;
}
print(y);

// Dry run:
// x=5: y = 0 + 2 = 2, x = 2
// x=2: y = 2 + 2 = 4, x = 1
// x=1: y = 4 + 1 = 5, x = 0
// Loop ends. Output: 5

• ✓Trace loops line by line with a variable table - never mentally 'jump to the end'.
• ✓Watch the difference between i++ and ++i, and between = and ==.
• ✓Watch loop boundaries: does it run n times or n − 1? Is the condition < or <=?
• ✓Know how arrays are indexed from zero and what an out-of-range access implies in the snippet's logic.
• ✓Practise with recursion snippets - factorial, Fibonacci and string reversal are perennial favourites, and recursion is where hand-tracing pays off most.

HackWithInfy and the Specialist Programmer route

HackWithInfy is Infosys's coding contest for engineering students, and it doubles as the main entry to Specialist Programmer roles. The assessment is coding-first: a small number of problems - typically graded easy, medium and hard - within a long window of around three hours, often with a cutoff on each problem rather than a single total.

The bar here is closer to a competitive-programming round than a campus test. Candidates who clear it generally have real practice with data structures and algorithms: arrays and strings, hashing, sorting with custom comparators, two pointers, greedy reasoning, graph traversal, and dynamic programming. Per-question cutoffs mean partial coverage matters - fully solving the easy and medium problems is usually worth more than a half-finished attempt at the hard one.

• ✓Build the standard toolkit: arrays, strings, hash maps, sorting, two pointers, recursion, DP, and BFS/DFS on graphs and trees.
• ✓Practise with a timer and an editor you will actually use - fluency in your language's standard library saves real minutes.
• ✓Secure the easy and medium problems completely before opening the hard one.
• ✓Always test the edge cases: minimum and maximum sizes, duplicates, negatives, and empty input.

The interviews

After the assessment come technical and HR rounds. For SE roles the technical conversation is moderate and resume-driven; for DSE and SP roles expect live coding, deeper computer-science questions, and follow-ups on complexity and design choices.

One pattern reported repeatedly by SP candidates is worth internalising: the online assessment is harder than the interview. The interview coding tends to sit at easy-to-medium difficulty, with the emphasis on how clearly you think aloud, whether you handle edge cases unprompted, and whether you can discuss object-oriented design, SQL and your own project without hand-waving.

• ✓Prepare one language deeply, including its collections or standard containers.
• ✓Be ready to write working code on a shared editor and explain your approach as you go.
• ✓Revise OOP concepts, DBMS with actual SQL, operating systems and networking basics.
• ✓Know your project end to end: the problem, your specific contribution, the trade-offs, and what you would do differently.
• ✓For HR: why Infosys, relocation and training-location flexibility, and the standard strengths-and-weaknesses set.

A study plan by track