# The hiring manager round: what they are deciding

Updated: 2026-11-13. https://thegccengineer.com/guides/hiring-manager-round

**Quick answer:** The hiring manager interview decides whether the manager wants you on the team: whether you can do this specific job, whether you will take ownership, whether you will work well with the people already there, and whether your reasons for moving make sense. Prepare a clear account of your current work, an honest reason for the switch, two or three ownership stories, and thoughtful questions about the team's work.

The hiring manager interview decides one thing: whether the person who will be responsible for your work wants you on the team. Technical rounds show that you could do the job; the manager judges whether you will do it well in this particular team, with ownership, and for reasons that will keep you there. It is a real evaluation, and candidates who treat it as a formality are regularly surprised by the outcome.

## What is the hiring manager deciding?

The hiring manager is deciding four things, and almost every question in the round maps to one of them. Knowing which one a question serves tells you what a useful answer contains.

| What the manager is deciding | How it shows up in the round | What helps |
| --- | --- | --- |
| Can this person do this specific job? | "Walk me through your most relevant project." | A project close to the team's work, explained end to end |
| Will this person take ownership? | "Tell me about a time something went wrong." | A story where you followed a problem past your own task |
| Will this person work well with us? | "How do you handle disagreement with a colleague?" | Evidence that you listen, argue with data and then commit |
| Will this person stay and grow? | "Why this role? Why now?" | A specific, believable reason for moving |

*The four decisions behind a hiring manager round.*

A manager at a Global Capability Centre is also thinking about risk. A hire who needs constant direction, or who leaves within a year, costs the manager far more than an empty seat does. Much of the round is the manager lowering that risk, which is why consistency between your resume, your earlier rounds and your answers here matters so much.

## What questions does a hiring manager ask?

A hiring manager asks about your work, your motives and your judgement, usually in a conversational style. Representative questions include:

- "Tell me about yourself and what you are working on now."
- "Which of your projects is closest to what this team does, and what was your part in it?"
- "Why do you want to leave your current company?"
- "Why an AI role, and why this one?"
- "What would you want to learn in your first six months here?"
- "Tell me about a decision you made that you would now make differently."
- "How would you approach a problem like the one this team is working on?"

For "tell me about yourself", give a two-minute answer in three parts: what you do now, the one or two pieces of work most relevant to this role, and why you are here. For story-based questions, use the approach in [behavioural interviews at GCCs](https://thegccengineer.com/guides/behavioural-interview-gcc). For the project walkthrough, expect follow-ups similar to those in the depth round described in the [GCC AI interview process](https://thegccengineer.com/guides/gcc-ai-interview-process).

## How do you explain why you are switching jobs?

Explain your switch as a move towards something specific, supported by something you have already done about it. A good reason has three parts: what you want more of, the evidence that you mean it, and why this role provides it.

For an engineer moving from a service company, an honest version sounds like this: you have spent several years delivering work for clients and have learned to ship under constraints; you want to own a product over a longer period and work on AI systems in depth; you have already started, through a project, a course applied at work, or an internal AI assignment; and this team's work is the kind of problem you want to keep working on. Nothing in that account criticises your employer.

**Answering: 'Why do you want to leave your current company?'**

**Weak answer**

- 'There is no growth and the work is boring'
- Complains about the manager, client or appraisal
- 'I want to work on AI' with nothing done about it
- Could be said to any company

**Strong answer**

- Names what the current job taught you
- States what you want more of: ownership, depth in AI
- Points to a project or work you have already done towards it
- Links the reason to this team's actual work

If pay is part of your reason, that is normal, and managers know it. Do not lead with it. A manager who hears only money assumes you will leave for the next higher offer. The wider argument for the move, and how to make it credible, is covered in [moving from a service company to a GCC](https://thegccengineer.com/guides/service-company-to-gcc) and, for the technical side, in [moving from software engineer to AI engineer](https://thegccengineer.com/guides/software-engineer-to-ai-engineer).

## How do you talk about moving into AI without much AI experience?

Talk about a move into AI by being exact about what you have done and what you have not. Managers hire career changers regularly; what they reject is inflation. Separate your experience into three groups: production engineering you have done at work, AI work you have done at work, however small, and AI work you have done on your own.

Then make the case for transfer. Production engineering habits, such as testing, monitoring, handling bad data and working with stakeholders, are a large part of what AI teams need. Follow with one self-built project you can explain in depth, including how you evaluated it. The projects that hold up to a manager's questions are described in [AI portfolio projects](https://thegccengineer.com/guides/ai-portfolio-projects). If the manager asks about a gap, name it and say what you are doing about it. A specific, honest gap is far less worrying than a vague claim of expertise.

## What questions should you ask the hiring manager?

Ask the hiring manager questions that help you decide whether to join and show that you think about the work. Your questions are part of the evaluation: they show what you care about. Three or four are enough.

- "What would you want the person in this role to have delivered after six months?"
- "What is the team working on now, and what is the hardest open problem?"
- "How is the work divided between this team and teams in other locations? Who sets the roadmap?"
- "How do you measure whether a model or feature is successful once it is live?"
- "How does the team review work: design reviews, code reviews, experiment reviews?"
- "What does growth look like for an engineer who does well here?"

The question about roadmap ownership is especially useful at a GCC, because teams differ in how much they decide locally. The background is in [how GCC teams work](https://thegccengineer.com/guides/how-gcc-teams-work). Avoid questions whose answers are on the company website, and leave leave policy, benefits and pay for the recruiter.

## How should you prepare for the hiring manager round?

Prepare for the hiring manager round by researching the team, then rehearsing a small number of answers aloud.

**Preparing for the hiring manager round**

1. **Reread the job description**: Underline the two or three problems the team is hiring to solve. Your examples should point at them.
2. **Research the company and the centre**: What the parent company does, and what its India centre works on. The companies directory is a starting point.
3. **Choose your closest project**: Prepare a five-minute walkthrough: problem, your part, decisions, result, what you would change.
4. **Write your reason for moving**: Three sentences: what you want more of, what you have done about it, why this role.
5. **Prepare three ownership stories**: One success, one failure, one disagreement. Two minutes each.
6. **Prepare four questions**: About the work, success measures, how the team operates and growth.

You can look up a company's industry, size and cities in the [GCC directory](https://thegccengineer.com/companies) before the conversation. Keep your answers consistent with what you said in earlier rounds; managers read the other interviewers' notes.

## What are the red flags hiring managers notice?

Hiring managers notice a short list of red flags, and most are avoidable.

- **Criticising a past employer or manager.** The manager imagines being described the same way.
- **No questions.** Having nothing to ask reads as low interest.
- **A generic reason for applying.** If your answer would fit any company, it persuades none.
- **Claiming a team's work as your own.** Follow-up questions expose it.
- **Inconsistency.** Different notice periods, dates or project details in different rounds raise doubts about everything else.
- **Asking only about pay, remote work and leave.** These are fair questions, for the recruiter.

After the round, the practical questions begin: your notice period, the offer and any counter-offer. Those are covered in [notice periods, counter-offers and choosing between offers](https://thegccengineer.com/guides/notice-period-and-offers).

## Key takeaways

- The hiring manager round is a real evaluation and can overturn strong technical rounds.
- The manager is deciding on capability for this job, ownership, team fit and motivation.
- Explain your switch as a move towards something specific, without criticising your employer.
- Your questions are scored too: ask about the work, success measures and how the team operates.
- Leave pay negotiation for the recruiter unless the manager raises it.

## Frequently asked questions

### Is the hiring manager round the final round?

Often, but not always. In many loops the hiring manager conversation comes last, after the technical rounds. Some companies place it earlier as a filter, and senior hires may meet a director or a counterpart from the parent company afterwards. The recruiter can tell you where the manager conversation sits and whether anything follows it.

### Can you be rejected in the hiring manager round after clearing the technical rounds?

Yes. The manager usually has the strongest voice in the decision, and technical rounds only establish that you could do the job. Common reasons for a late rejection are vague motivation, weak ownership examples, a mismatch between what you want and what the role offers, or doubts raised by how you spoke about previous colleagues.

### Does the hiring manager ask technical questions?

Usually some, at a higher level than the depth rounds. Expect to walk through one project end to end, explain a design decision and its trade-offs, and say how you would approach a problem the team actually has. The manager is checking judgement and communication more than recall, so clear explanations matter more than detail.

### Should you discuss salary with the hiring manager?

Generally no, unless the manager brings it up. Compensation is normally handled by the recruiter, and raising it with the manager can shift the conversation away from the work. If the manager asks about expectations, say you are happy to discuss details with the recruiter and that the role and team are your first concern.

### How should you follow up after the hiring manager round?

Send a short thank-you note through the recruiter the same day or the next, mentioning one specific thing from the conversation that increased your interest. Then wait for the timeline the recruiter gave you. If it passes, one polite check-in is reasonable. Repeated messages do not speed up a decision.