Here’s a typical pattern for the standard fresher (Systems Engineer) role.
Key notes:
The sections are often section-wise timed (you finish one section before moving to next) rather than free navigation.
There may be sectional cut-offs (you must clear each section) rather than just overall score.
Usually no negative marking is explicitly stated in many cases (but check your drive).
For higher-level fresher roles such as Specialist Programmer (SP) or Digital Specialist Engineer (DSE) at Infosys, the pattern is more coding/DSA-heavy. For example:
The test may consist of 3 coding problems in one session (approx 3 hours) covering Data Structures & Algorithms (DSA), Greedy, Dynamic Programming etc.
Languages allowed: C, C++, Java, Python, JavaScript.
Focus is more on programming logic than just aptitude.
The mix: Aptitude + reasoning + verbal + basic programming.
The difficulty: For standard SE role it’s moderate; for SP role it’s high (coding heavy).
Emphasis: Quick speed + accuracy for aptitude & reasoning; clear logic for pseudo-code/coding.
Time-management is important because each section has limited time.
Verbal & communication skills are not just extras—they matter (especially writing/grammar section if present).
Practice quantitative ability: percentages, DI, time & work, number series.
Strengthen logical reasoning: puzzles, arrangements, coding-decoding, syllogisms.
Improve English: practice para jumbles, grammar, reading comprehension, short writing.
Build basic programming logic: loops, arrays, conditional statements, simple algorithms.
For SP/advanced roles: focus on DSA (arrays, strings, trees, graphs), coding in one language, solving problems under time pressure.
Take mock tests that simulate sectional timing and format (e.g., 10 questions in 35 mins, etc).
Practice previous years’ papers for variations and patterns.