What the interviewer is checking first
Global capability centres go by several names: captive centre, global in-house centre, technology centre, or simply the company's office in Bengaluru, Kraków, Manila, Guadalajara or Kuala Lumpur. The model is the same wherever it sits. The parent opens a subsidiary in another country, hires there directly, and the work stays in-house rather than being contracted to a vendor.
That distinction is the first thing the interviewer listens for, because candidates moving from services firms often describe the role as "the same work, but for one client". It is not. At a vendor, your output is governed by a statement of work, your manager's success is measured in billable utilisation, and the client can end the engagement. At a captive centre, there is no contract between you and the business. The applications you maintain are the company's own, and the people who use them are your colleagues.
Getting this wrong is not fatal, but it tells the panel you have not thought about where you are applying. Getting it right in one sentence, unprompted, buys you credibility for the rest of the answer.
Why the centre's mandate matters more than its brand
Centres vary enormously. Some began as cost-driven back offices running support and testing, and some still are. Others own whole products, run their own architecture decisions and hire for roles that do not exist at headquarters. Two global capability centres of the same parent company, in different cities, can have very different mandates.
So the specific part of your answer should be about the mandate, not the logo. "I want to work for a large, stable brand" could be said about any of them. "I understand this centre owns the payments platform end to end, including on-call, and that is the kind of ownership I have not had on client projects" is about this one. If you could not find out what the centre owns, say so and make it a question: "What does the team own outright, and what does it build to specifications from headquarters?" That reads as judgement, not ignorance.
Honest motives, by where you are coming from
Your reason for moving should match what the centre can genuinely give you. A few patterns hold up under follow-up questions:
| Coming from | Motive that holds up | Motive that collapses |
|---|
| Services firm | "I want to stay on one system long enough to live with my own design decisions." | "I want to work for a big name." |
| Product startup | "I want depth in a regulated domain, and engineering standards I can learn from." | "I want less pressure." |
| Another captive centre | "This centre owns the product; my current one mostly supports it." | "Better pay," with nothing after it. |
Pay, stability and benefits are legitimate reasons, and pretending otherwise rarely convinces anyone. Say them once, then give the reason about the work. A captive centre is often hiring precisely because it wants people who will stay and accumulate domain knowledge, so stability is a shared interest, not an embarrassing one.
Distance from headquarters is where these answers go wrong
The weak answer treats the centre as headquarters with a different postcode. The strong answer acknowledges the real working conditions of a captive centre: some decisions are made in another time zone, your most senior stakeholders may be eight or more hours away, and a reorganisation at the parent can change your team's scope.
You do not need to be gloomy about this. You need to show you have considered it and have a way of working with it. "I know some product direction comes from headquarters. On my current project I write short decision notes and share them before the overlap window, so I am not waiting a day for an answer" is a mature line. It also previews the collaboration skills the hiring manager will probe later. If you want the behavioural version of that skill, see the headquarters team whose decisions keep landing on yours.
The other mistake is leading with a transfer to the parent's home country. Mobility may exist, and asking about it late in the process is reasonable. Making it your motive tells the panel that this seat is a waiting room, which is the retention risk they are screening for. The general shape of that risk is covered in why this company and why are you leaving.
A sample answer to adapt
"I have spent four years at a services firm, mostly on two-quarter engagements, and I keep handing over systems just as I understand them. What draws me to a capability centre is that the work belongs to the company: I would be on the same platform for years, on call for it, and accountable for how it ages.
From what the recruiter told me, this team owns claims processing outright rather than building to specifications from headquarters, and that is the part I want. I also know some roadmap decisions will be made in another time zone, and I am used to working asynchronously with stakeholders who start their day as I finish mine."
Notice what that answer leaves out. It does not praise the brand, it does not mention relocation, and it does not call the previous employer bad. It names one thing the candidate lacked, one thing this centre owns, and one working condition they have already handled.
The specific noun is the centre's mandate. If your answer would be equally true of any captive centre in the city, it has not answered the question.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).