Infosys Managerial Round Interview Questions 2026: 30 Questions with Sample Answers

This page is for two groups: freshers who have an Infosys "managerial" or "techno-managerial" interview on their schedule, and experienced candidates going through Infosys lateral hiring where a manager round is standard. It explains when the round happens, who runs it, what they are deciding, and gives 30 questions with sample answers for both groups.

At Infosys the managerial round is less predictable than at TCS because it is not always a separate slot. For System Engineer freshers the managerial questions usually arrive in the middle of the HR conversation, without warning. Prepare for them anyway.

How the Infosys managerial round works in 2026

As of September 2026, Infosys's graduate careers page does not describe interview rounds. The picture below comes from 2026 placement-site reporting and candidate experiences.

Freshers (System Engineer). The typical sequence is InfyTQ certification or an off-campus online test, then a technical interview of 30 to 45 minutes, then an HR conversation of 15 to 20 minutes. Placement guides describe the HR conversation as an "HR/managerial round" because it carries the managerial questions: relocation, shifts, conflict, deadlines, other offers. Some campuses run a distinct managerial round of 20 to 30 minutes with a delivery manager.

Specialist and Power Programmer candidates. Panels are stronger and sometimes include a senior technology lead who asks managerial-style scenario questions alongside the design and coding discussion.

Experienced candidates. Infosys lateral hiring usually has a technical round, a managerial round with the hiring manager or delivery manager (30 to 45 minutes) and an HR round. The managerial round may include a technical scenario from the manager's own project, a discussion of your notice period and a check on why you are leaving.

Who interviews. A project or delivery manager, often the person who owns the open position, sometimes with an HR partner.

Context that shapes the questions. Freshers train at the Mysuru campus before allocation, so relocation is asked always. Infosys has historically used a service agreement for freshers; the terms are in the offer letter. Managers know that fresher attrition in the first year is their problem, so commitment questions are direct.

What the Infosys managerial interviewer is testing

• Judgement in ordinary project situations: a slipping deadline, a changed requirement, a silent teammate, a client who is unhappy.
• Flexibility: technology, domain, location, shift. Infosys allocates by business need after training.
• Composure: stress questions and repeated criticism scenarios test whether you stay calm and structured.
• Commitment: offers in hand, higher-studies plans, family constraints, and for laterals, why you are leaving and how fast you can join.
• Communication in business terms: can you describe your project to a client who does not code?

Use STAR (Situation, Task, Action, Result) for every "tell me about a time" question and keep each answer near a minute.

30 Infosys managerial round questions with sample answers

Project situations

1. Your delivery date was moved up by ten days. What do you do?

"Confirm the new date and the minimum scope with my lead first; scope is negotiable, time usually is not. Then list remaining work, mark must-have versus nice-to-have, and give an honest estimate for the must-haves. In my final-year project our review moved up two weeks; we cut the SMS alert feature, delivered the core attendance flow, and shipped the alerts in the next iteration."

2. The client changes a requirement the night before release. What now?

"Assess the size before reacting. Small change: make it, test it, tell my lead. Large change: tell my lead immediately with an estimate and two options, release on time without it or slip a day with it. The decision is the lead's; my job is accurate information quickly."

3. A production bug appears at night and your lead is unreachable. What do you do?

"Check impact first: is data being corrupted or is it cosmetic? If severe, follow the project's escalation path and post on the project channel so there is a record. As a fresher I would not push an unreviewed production change alone unless the runbook says so."

4. You spent a month on a module and it is dropped from scope. How do you react?

"Disappointed for an evening, then practical. I would save the reusable parts, write a short note on what I learned about the domain, and move on. Requirements change; taking it personally does not help anyone."

5. Your team is behind and a colleague suggests skipping testing to catch up. What do you say?

"I would suggest cutting scope instead of cutting testing, because a bug in production costs more time than the tests saved. If the lead still decides to reduce testing, I would ask that we document the untested areas and test them first after release."

6. You are given a task with no clear requirements. How do you start?

"Write down what I think is being asked in five lines and send it to the requester for confirmation before coding. Then build the smallest version, show it early and adjust. In my internship this saved me a week when my understanding of a report format turned out to be wrong."

7. Two seniors give you conflicting instructions. What do you do?

"Politely tell both that I have received different instructions and ask them to align, ideally in one message with both copied. I would not pick one silently. Most of the time they simply did not know the other had spoken to me."

Teamwork and people

8. Tell me about a time you worked in a team with conflict.

STAR. "Situation: in our hackathon team two members disagreed on the database choice and stopped talking. Task: we had 24 hours left. Action: I proposed we pick the one both had used before and decide the other for the next project, and I kept a shared task board so work continued. Result: we finished a working demo and placed third. I learned that a decision made quickly beats a perfect one made late."

9. A teammate is not contributing. What do you do?

"Talk to them privately first; there is usually a reason. In one project a member vanished for two weeks due to family illness; we shifted him to remote-friendly work and I took his module, and we finished on time. If someone simply refuses, I document and escalate to the lead."

10. How do you handle criticism of your work?

"Ask for one specific example, fix it, and show the fix. Repeated criticism usually has a pattern. If it stays vague, I ask for a short one-on-one to understand expectations. I do not argue in front of the team and I do not disengage."

11. Do you prefer working alone or in a team?

"Both, by task. Coding and debugging alone, design and reviews in a team. In an Infosys project most of my day would be team-based and I am fine with that; I also do not need supervision to stay productive."

12. How would you explain your project to a client who does not know programming?

"Your professors spent five minutes a lecture on roll call; our system takes attendance from the classroom camera in ten seconds, and a professor can correct it with one click. That sentence, plus one number from the pilot. Managers want to hear that I can drop the jargon."

13. If your idea is rejected by the team, what do you do?

"Find out why; usually I missed a constraint. Address the concern, and if the team still disagrees, go with the team's decision and let results speak. Ideas that need forcing are usually not worth forcing."

Flexibility and commitment

14. Are you willing to relocate to Mysuru and then to any Infosys location?

"Yes. I know training is at Mysuru and allocation depends on project need; my family and I discussed it before I applied." If you have a hard constraint, say it now with a reason; a no after the offer is worse for you.

15. Are you comfortable with rotational or night shifts?

"Yes. Some client projects run on US or UK hours and I understood that when I applied. I would prefer a development role over pure support, but the shift itself is not a problem."

16. Would you be okay working on a technology different from your project, say mainframe or SAP?

"Yes. My project taught me how to learn a stack, not just one stack. If Infosys trains me in SAP or mainframe I will treat it seriously. I would like to move towards cloud or data work over time, but the first project is Infosys's call."

17. Do you have other offers? Which will you accept?

"I have a Wipro Elite offer. I would choose Infosys for the training and the Specialist Programmer path. I am telling you so you are not surprised later." Candour reads as low risk; hiding an offer that surfaces later reads as high risk.

18. Any plans for higher studies, GATE, CAT or government exams?

"No. I decided in third year to get industry experience first; if I do a master's later it would be part-time." If you are preparing for something, do not lie, but understand the manager will weigh it.

19. Why Infosys, and why should I put you on my project?

"For the structured training and the internal tracks. For your project: my fundamentals are clean, my project is deployed and I can defend it, and I communicate status without being asked. I will not be the best coder on day one; I will be reliable from day one."

Self-awareness and stress

20. What is your biggest weakness as a future team member?

"I used to over-build. I now write the requirement in one line above every task and check against it before adding anything. My project shipped because of that rule."

21. What quality of yours would a manager notice in the first month?

"That I write things down: meeting notes, decisions, open questions. Leads notice when nothing gets lost and clients notice a clean summary after a call."

22. Describe a situation where you would not perform well.

"Long stretches with no feedback. I improve fastest when told what is wrong. I handle pressure and unclear requirements fine, but months of silence would slow me down, so I ask for feedback proactively."

23. How do you stay updated with technology?

Name two real sources and one thing you learned from them recently. "The Infosys Springboard courses and one newsletter on cloud; last month I built a small Lambda function after reading about serverless." Specifics matter; "I read blogs" does not.

24. What does success look like for you in three years at Infosys?

"Being the person on the team trusted with the hard module, one specialisation like cloud or data with Infosys certifications behind it, and having moved from System Engineer to the Specialist track on merit."

For experienced candidates

25. Why are you leaving your current company?

"My current project is in maintenance with no development work coming, and I want to build. Infosys has an opening on a stack I have been learning. I am not leaving because of a person; my manager knows I am interviewing." Never criticise the current employer.

26. What is your notice period? Can you join early?

"Sixty days, and my company allows buyout of the remainder; I can share the policy. Realistically I can join within 45 days of an offer." Have exact numbers; managers plan allocation around them.

27. Tell me about a client escalation you handled.

STAR with numbers. "A monthly report failed at the client's month-end. I acknowledged within fifteen minutes, gave hourly updates, found a null-handling bug, fixed it in three hours, and sent a root-cause note the next day. The client's feedback in the quarterly review mentioned the communication, not the bug."

28. How do you handle a disagreement with your manager on a technical decision?

"State my reasoning once with evidence, then follow the decision. If it later causes an issue, the record shows I raised it, and I still help fix it. I do not repeat the argument or go around them."

29. What is your expected CTC and why?

Give a number with a basis. "My current CTC is 6.5 LPA; I am expecting around 9 based on the role's band and the market for three years of experience in this stack. I am open to discussing the structure." Do not say "as per company norms".

30. Do you have any questions for me?

"What does a typical first project look like for someone in this role?" and "How do you decide when a new joiner is ready for direct client interaction?" Skip salary and leave here; those belong with HR.

Mistakes that get candidates rejected in the Infosys managerial round

• Saying no to relocation or shifts, or a yes that sounds reluctant.
• Every story blames someone else. The manager notices the pattern.
• Contradicting HR. Offers, gaps, family location: one version only. Panels compare notes.
• Answering scenario questions with heroics. "I would work all night" is not judgement; a plan is.
• Losing composure on a stress question. The panel is grading the reaction, not the answer.
• STAR stories not on the resume. If your leadership story is nowhere on your CV, expect a follow-up you cannot answer.
• Asking about salary or leave in the managerial round.

How to practise the Infosys managerial round

Managerial questions reward composure and a bank of your own stories, and neither comes from reading. In MockMate Practice, attach your resume and paste the Infosys role text, choose a managerial or behavioural round, and run a ten-minute adaptive session in the browser. The interviewer persona pushes on weak stories and adds follow-up pressure the way a delivery manager does. The report shows every answer, your response timing, recurring weaknesses and a recommended next practice. Eligible accounts get three free Practice starts of up to ten minutes each. Use MockMate Live assistance only in interviews or meetings where the organisation or interviewer permits it; when permission is unclear, which is the case for Infosys selection rounds, stay with Practice.

Plan: write six STAR stories (deadline, conflict, failure, leadership, learning something new, doing work you disliked), run one Practice round, rewrite the two weakest stories from the report, and run it again. The technical and HR rounds are covered on the Infosys hub; company-mapped sessions are at /mock-interview.