Infosys Product Manager interviews, as candidates describe them, mix situational product questions, domain depth (insurance, telecom) and sometimes SQL, with processes ranging from a few weeks to longer.
$119K
Avg. Base Comp
$128K
Avg. Total Comp
3-4 rounds
Typical Rounds
2-4 weeks
Process Length
Candidates describe Infosys Product Manager interviews as less generic than the title suggests. The domain you are hired into shapes the questions, so the reports differ a lot from one another.
One candidate was asked about their career path, working with product teams across different businesses, a product they built end to end, real-time scenarios and the full PLM process. A panel in that process also asked how AI influences the project and a direct "why should we give you the job?" question. Another candidate spent about an hour on insurance knowledge, including property insurance and claims, before two case questions, one a product launch scenario. That candidate felt generic frameworks were not enough. A third was asked how they would help new employees work more efficiently, then went through an architecture round on OSS and telecom systems. A fourth, whose listed title was Technical Product Specialist but who described a product manager process, reported a group discussion, an aptitude test and a technical round heavy on SQL. That candidate was also asked to review the team's product on the spot.
Process length varied. Candidates report roughly two weeks in one case and about four weeks in another, and one says a rejection appeared on the portal after a week without feedback. Communication was described as responsive by one candidate and uneven by another. Among the candidates reporting outcomes here, none accepted an offer. Two declined offers and two were not selected.
For preparation, ask the recruiter which business line the role sits in. Then build product stories with clear outcomes and rehearse a launch or improvement case in that domain's terms. Refresh SQL basics in case the technical round leans that way.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Infosys process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Infosys
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Top 3 Users | |
| Size of Joins | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Booking Regression | |
| Hurdles In Data Projects | |
| Fine-Tuning VS RAG | |
| P-value to a Layman | |
| Covariance vs Correlation | |
| Merchant Dashboard Design | |
| Causal Attention Debugging | |
| Ticket Agent Analysis | |
| The Longest Journey | |
| Seller Type Modeling | |
| String Palindromes | |
| Digitizing Student Test Scores | |
| RAG Strict Source Control | |
| Classification and Regression | |
| Safe Streaming Latency | |
| Safe Deployments | |
| Text Editor With OOP | |
| RAG Hallucinations | |
| Scalable Data Pipelines | |
| Addressing Data Quality Issues | |
| Testing Constraints | |
| Azure Kubernetes Infrastructure | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us |
Synthesized from candidate reports. Individual experiences may vary.
One candidate describes a phone screen before the later rounds, with early conversations focused on experience and alignment. Expect to explain your career path and current role concisely, and confirm which business line or domain the role belongs to.
One candidate reports a group discussion and an aptitude test, both described as elimination stages, and another mentions a written assessment on foundational concepts. This may not apply to every role or team, so ask the recruiter whether a screening stage exists before you prepare for one.
Candidates report domain-heavy interviews. One had about an hour of insurance questions followed by two cases, including a product launch. Another had an architecture-focused round on OSS and telecom systems. Prepare to ground any framework in the vertical's real products, customers and problems.
Reports include walking through a product you built and its outcome, the PLM lifecycle, real-time scenarios and AI's influence on the project. One candidate faced a four-person panel in a round. Another was asked SQL fundamentals and to review the team's product on the spot. Which of these you get may depend on the team.
Candidates report a final HR conversation in some processes, with a "why should we hire you" style question in at least one. Feedback timing is mixed. One candidate saw a portal rejection after about a week, and another describes slow feedback cycles.
