Infosys Interview Experience for Java Developer 2 years of Experience
Interview Experience
Candidate Information:Status: Actively seeking opportunitiesExperience: 2+ years in Java + Spring Boot developmentTarget Position: Java Backend DeveloperLocation: Chandiga...
Full Details
Candidate Information: Status: Actively seeking opportunities Experience: 2+ years in Java + Spring Boot development Target Position: Java Backend Developer Location: Chandigarh/NCR, India Interview Date: August 2025 Overview of Interview Process: Initial Screening Duration: ~40 minutes Method: Online (Microsoft Teams) Focus: Background, project discussion, and technical fundamentals Key Questions: Tell me about yourself Overview of recent projects Tech stack and key responsibilities Obstacles: Nothing major; the conversation was smooth and mostly focused on background check.
Technical Round Duration: ~45 minutes Method: Online (Microsoft Teams) Focus: Java, Spring Boot, OOPs, Testing, Docker & Redis (from resume) Key Questions: Introduce yourself Difference between @Controller and @RestController What is inheritance? Explain method overloading and overriding Flow of a Spring Boot project (Controller → Service → Repository) Which server comes with Spring Boot by default? (Answer: Tomcat) Where do we write business logic? What is mapping? (Explained DTO and ModelMapper) Where are dependencies written? (Answer: pom.xml / build.gradle) Purpose of application.properties Questions on testing tools like Mockito How do you test your code/program to ensure correct flow? Questions about Redis and Docker (as mentioned in resume) What is a Repository in Spring Data JPA? Why do we use @Entity? What is an Interface in Java? Obstacles: Some in-depth follow-up questions around Redis and Docker since I had mentioned them in my resume, but overall manageable. Post-Interview Reflections: Company Culture Insights: The interviewer was polite, encouraging, and gave enough time to think before answering. The interaction reflected Infosys’ supportive and professional culture. Work Environment: Conducted virtually over Microsoft Teams, with a smooth process and clear communication. Benefits Highlight: Specific perks or benefits weren’t discussed in this round. Evaluator Feedback: Positive overall. I received a mail for the second round on the next working day, which indicates good performance in the first round. Suggestions for Improvement: Be fully prepared for all technologies mentioned in your resume (like Redis, Docker, Testing tools), since interviewers often pick topics directly from there. Additional Information: Timeline: First round completed in ~45 minutes, result communicated the very next working day. Next Steps: Cleared first round → Proceeding to second round. Closing Note: Overall, the interview was a positive experience. The discussion balanced between Java fundamentals, Spring Boot architecture, and practical tools like Docker/Redis. This experience reinforced that preparation should cover not only core concepts but also any extra tools/technologies highlighted in the resume.
About This Question
This is a candidate experience report from a infosys interview for a backend role (new grad level) during the phone screen round reported in 2025.
It covers the following topics: Stack, Stack Queue .
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.