Infosys Interview Experience
Interview Experience
Candidate Information:Status: Final year engineering student (Mechanical)Target Position: Systems Engineer Trainee (For Freshers)Year: 2018Overview of Interview Process:2 ...
Full Details
Candidate Information: Status: Final year engineering student (Mechanical) Target Position: Systems Engineer Trainee (For Freshers) Year: 2018 Overview of Interview Process: 2 Rounds
Round 1 Initial Screening Duration: 1 hour Method: in-person Focus: Quantitative aptitude test Key questions: Common math problems like time speed distance, time and work, arithmetics, logical puzzles like patterns, verbal like grammar and comprehension Obstacles: moderate difficulty questions
Result approx 200/1000 candidates selected for
next round
Round 2 HR Round Duration: 20 odd minutes Method: in-person Focus: One on One technical and HR screening Key questions: Once introduction was done, asked about my work in the projects that I had done. The I was asked to write a common algorithm like Fibonacci Obstacles: nothing much, the interviewer was friendly
Result 90% of candidates got through Post-Selection: Onboarding in Mysore with batch-wise training 3-day induction covering policies, security, and campus orientation Rigorous foundational and domain-specific training (75% pass requirement for theory and practical) Posted to project location; top scorers got preferred locations Gradual responsibility increase through KT sessions and assigned tasks Additional Information: There might be a self paced learning module which might be assigned before joining the company. There will be policy, compliance and technical courses that may be mandatory to complete within a few days after joining or allocation to a project.
About This Question
This is a candidate experience report from a infosys interview for a quant role (new grad level) during the recruiter round reported in 2025.
It covers the following topics: Math .
Difficulty rating: Medium
Topics
More Infosys Interview Questions
About Infosys Interview Reports
This question was reported by a candidate who interviewed at Infosys. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Infosys are the higher-signal extractions to take from this report.
For broader preparation context, the Infosys interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Infosys reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Infosys Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Infosys reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.