Behavioural interviews at GCCs: stories that work

Behavioural interview questions at GCCs ask you to describe what you actually did in a past situation: "Tell me about a time you disagreed with a senior colleague", "Describe a project that failed". Interviewers use them to predict how you will behave on their team, so the answer that works is one specific, true story told with your own actions at the centre. Five or six prepared stories will cover most of what you are asked.

What do behavioural interviews at GCCs test?

Behavioural interviews at GCCs test whether you can be trusted to own work without close supervision. A Global Capability Centre team builds and runs products for its parent company, often with colleagues in other countries, so interviewers look for people who take responsibility for outcomes, speak up, and work well across functions and time zones.

That emphasis is the main difference from a typical service-company interview, which more often checks whether you will deliver assigned tasks reliably. The contrast in working style is explained in how GCC teams work. Behavioural questions may come in a dedicated round or inside the manager conversation; both are placed in context in the GCC AI interview process.

What behavioural interview questions do GCCs ask?

GCC behavioural interview questions cluster around six themes. The wording changes, but each question maps to one theme, and recognising the theme tells you which story to use.

How do you use STAR without sounding scripted?

Use STAR as a way to organise your notes, not as a script to recite. STAR stands for situation, task, action and result. Answers sound scripted when the candidate memorises sentences; they sound natural when the candidate memorises only the facts and tells the story fresh each time.

Three habits keep STAR natural. First, write each story as six or seven bullet points, never as paragraphs. Second, include one decision point: a moment where you had two options and chose one for a reason. Decision points are what make a story sound lived. Third, end with a result and stop. The interviewer will ask for what they want next.

On results, use a real measure only if you have one. If the outcome was not measured, describe what changed in plain terms: the report that now runs without manual steps, the client call that no longer happens every week. An honest plain outcome is stronger than an invented percentage, and interviewers do ask how you measured it.

What stories do service-company engineers already have?

Service-company engineers already have strong behavioural stories; most simply have not labelled them. Work at companies such as TCS, Infosys, Wipro, Accenture or Cognizant produces exactly the situations that behavioural questions ask about.

• A production incident you helped resolve. Shows ownership and calm under pressure. Include how you found the cause and what you changed so it would not recur.
• A manual task you automated without being asked. Shows initiative. Explain how you noticed the waste and convinced others to adopt the fix.
• A client escalation. Shows stakeholder handling. Describe the client's real concern, which is often different from the stated complaint.
• A time you pushed back on a deadline or a requirement. Shows judgement in disagreement. Explain the evidence you brought and how the conversation ended.
• Onboarding to an unfamiliar codebase or domain. Shows learning. Describe your method, not only the hours.
• Mentoring a new joiner or covering for a lead. Shows leadership without a title.
• A self-driven AI project or certification applied to real work. Shows the motivation behind your move, which matters for an AI role.

The framing matters as much as the event. The same shift from tasks to outcomes that improves your resume, described in rewriting a service-company resume, also improves your stories.

How do you answer questions about ownership and stakeholders?

Answer ownership and stakeholder questions by showing a choice you made, because ownership is visible only when you could have done less. For ownership, pick a story where the easy path was to finish your ticket and move on, and you chose to follow the problem to its cause. Say what you noticed, what you did that was not required, and what happened as a result.

For stakeholder questions, show that you understood the other person's position before acting. A strong answer names what the stakeholder actually needed, how you changed your communication (a shorter update, a demo instead of a document, an earlier warning), and how the relationship stood afterwards. For disagreement questions, the pattern interviewers look for is: you raised the concern with evidence, you listened, and once a decision was made you supported it fully, whichever way it went.

How many stories should you prepare?

Prepare five or six stories, chosen so that together they cover all six themes. Build a small grid: stories down the side, themes across the top, and a mark where a story can serve a theme. Each theme should have at least two possible stories, so you are never forced to repeat one with the same interviewer.

Practise each story aloud three or four times, with a timer, until it runs for about two minutes without notes. Record one attempt and listen for long context and for "we" where "I" is accurate. Then prepare the three follow-ups that nearly always come: what you would do differently, what the hardest part was, and what others on the team thought.

What mistakes cost candidates the behavioural round?

The mistakes that cost candidates the behavioural round are mostly about evidence, not personality.

• Answering in general terms. "I always communicate proactively" is a claim. The question asked for an instance.
• Hiding behind "we". The interviewer cannot hire your team. Say what you did, and credit others for what they did.
• Blaming. Criticising a previous manager, client or employer raises doubts about how you will speak of the next one.
• A failure story with no failure. Choose a real mistake with a real cost, then show what changed.
• Inflating your role. Follow-up questions expose it quickly, and a single doubt colours the whole interview.
• Reciting. A word-perfect answer delivered at speed sounds memorised and invites harder probing.

Behavioural answers feed directly into the manager's decision, which is explained in what the hiring manager round decides. If you are planning the wider move, moving from a service company to a GCC covers the whole path, and the free readiness check and roadmap on The GCC Engineer shows which step to work on first.