Learn from Infosys campus interview experiences across Systems Engineer (IRT), HackWithInfy / SP, and onsite SP patterns. Composites below pull from GeeksforGeeks 2025-batch reports and common 2025-2026 IRT prep guides; verify your role on the drive mail.
Round-wise process at a glance
Round
Typical format
What clears you
Online assessment
IRT / InfyTQ / HackWithInfy OA (role-specific)
Sectional plus overall cutoff; ≥1 coding solve on many IRT reports
Technical
Projects, SQL, DSA, OOP, OS/DBMS
Clarity + correct approaches
HR
Mobility, training commitment, motivation
Honest fit; HR is not a formality
Technical interview experience 3 - Systems Engineer, IRT campus composite
Technical interview experience 3
Candidate profile: Standard SE track after clearing IRT (composite from 2025-2026 campus reports)
IRT (online)
~180-minute multi-section paper on many campus drives: quant, reasoning, verbal, pseudo-code, 1-2 coding problems
Sectional timing strict - candidates report failing on time management even with partial knowledge
Tip: One full timed mock weekly; log misses by section, not only coding
Technical (30-40 min)
Project: problem → stack → your module → measurable result in two minutes
OOP: inheritance example; overloading vs overriding
DBMS: second-highest salary or join query; normalization to 3NF with a redundancy example
One easy coding warm-up: palindrome or array rotation
Final result: Advanced to HR
HR (15-25 min)
Why Infosys vs other IT offers; willingness to relocate to any development centre
Training agreement comfort; technology flexibility (“we may assign any stack”)
Final result: Selected (typical HR pass-through high after technical clear)
Takeaways
What decided it: SE bar is fundamentals plus one clean coding idea, not HackWithInfy DP depth.
Common fail: Undefendable resume lines or rigid location answers
How to practise: Project deep-dives; OOP/SQL; clear service-location answers
Translate problem statements into binary/bit checks
Dry-run small n before coding
Tip: Speak the invariant you are testing
Grid DFS / BFS
Number of islands template: iterate cells, DFS/BFS on unvisited land, increment count
Clarify 4-direction vs 8-direction connectivity
Result: Matches warship-group style prompts
Tip: Discuss time O(rows*cols) and visited handling
Takeaways
What decided it: Template fluency + verbal clarity beats memorising one GFG article.
Common fail: Undefendable resume lines or rigid location answers
How to practise: Project deep-dives; OOP/SQL; clear service-location answers
HR interview experience
HR interview experience
Candidate profile: SP onsite candidate (fit woven into technical)
Ambition / fit prompts
Career aspirations
Technologies you want to explore
Location preference among Infosys hubs
Why Infosys SP vs other offers
Final result: Combined with technical performance
Takeaways
What decided it: Ambition answers should sound specific (systems, platforms, ML eng) not “anything”.
Common fail: Undefendable resume lines or rigid location answers
How to practise: Project deep-dives; OOP/SQL; clear service-location answers
Sample answers for high-frequency questions
Use these as frames, not scripts.
Technical
Q. 5th highest salary in SQL? A. Discuss ties: DENSE_RANK/ROW_NUMBER over ORDER BY salary DESC filtered to rank 5, or dialect offset approaches. State how ties should count.
Q. Number of warship groups in a grid? A. Islands pattern: for each unvisited 1, run DFS/BFS, mark visited, increment. Confirm adjacency rules. Complexity linear in grid size.
Q. Deadlock handling? A. Conditions (mutual exclusion, hold-and-wait, no preemption, circular wait) → prevention by breaking one → avoidance (Banker’s) → detection and recovery. Keep examples short.
Fit
Q. Technologies you want to explore? A. Pick one stack adjacent to your projects and one stretch area. Tie to how SP work could expose you to them.
These links are research inputs we used to map round structure and recurring questions - not copied page mirrors. We reorganized reports into process tables, outcome notes, and prep takeaways for Infosys.
