How to get a job at a GCC in India: a step-by-step plan

The way to get a job in a GCC is to treat the search as a short project with six steps: choose a target role and companies, measure your gap against real job descriptions, build proof, rewrite your resume, get referrals while you apply, and prepare for interviews. A Global Capability Centre hires directly as part of its parent company, so the work happens on company career pages and through people inside those companies, not on a single jobs portal.

What does it take to get a job at a GCC in India?

Getting a job at a GCC in India takes a clear target, evidence that you can do that job, and a route to a human reader. Global Capability Centres are the in-house technology and operations centres of global companies, such as banks, retailers, pharmaceutical firms and energy companies. If the term is new, start with what a GCC is.

The market is large and tilted towards the skills this plan builds:

GCCs in India

2,117

of new GCC roles need AI, data or automation skills

64%

of GCC hiring is for 4 to 10 years of experience

56%

Because there are so many centres, most candidates have heard of only a few and apply to the same famous names. A plan that starts from a company list reaches the rest.

Step 1: Which role and which companies should you target?

Target one role family and a list of twenty to thirty companies, chosen by industry and city. A focused target makes every later step easier: one set of skills to prove, one resume to tailor, one group of people to reach.

For the role, pick the track nearest to what you already do. A backend engineer has a shorter path to an AI backend or GenAI engineering role than to a research role. The overview of AI engineering roles at GCCs describes each track.

For the companies, do not rely on memory. Browse the GCC directory, which lists centres by industry, size and city, and follow the method in the guide on how to build a GCC target company list.

Step 2: How do you find your skill gap?

Find your skill gap by collecting five to ten job descriptions for your target role and marking which requirements you can already prove. The gap is whatever appears in most of the postings and nowhere in your experience.

Sort each requirement into three groups:

• Proven: you have done it and can point to work.
• Partial: you have used it lightly or in a course.
• Missing: you have never done it.

Requirements that repeat across postings are the real ones; items that appear once are usually a single team's wish list. The guide on how to read an AI job description shows how to tell must-haves from extras. Postings ask for more than any one candidate has, so a few missing items should not stop you applying.

Step 3: How do you close the gap and prove it?

Close the gap with focused learning and one project that uses the missing skills together. A certificate says you attended; a project shows you can build.

A sensible order is fundamentals first, then the specialism of your role, then a project. The AI engineer roadmap sets out what to learn and in what sequence. For the project, choose something small that you take all the way: real data, a working system, an evaluation of how well it performs, and a written explanation.

If you already work in a service company, look inside your current job as well. Automation you built, data pipelines you own and internal proofs of concept all count as evidence when described well.

Step 4: How should your resume and LinkedIn change?

Your resume and LinkedIn should change to name the target role at the top and present your experience as outcomes. Do this before applying, because a referral or an application only helps if the document it carries is ready.

The essentials:

• A three-line summary naming the role, your experience and your strongest proof.
• Bullets that say what you built and what changed, not what you were assigned.
• Projects with links and a line on evaluation.
• A LinkedIn headline and skills that match, since recruiters search there.

The AI engineer resume guide for GCC roles covers the full structure.

Step 5: How do you apply and get referrals?

Apply through each company's own career page and, for every serious target, ask someone inside for a referral as well. The two routes work together: the application puts you in the system, and the referral gets a person to look.

Details on each route are in the guide on where to find GCC jobs in India. For referrals, start with how to get a referral at a GCC, which covers whom to ask and what they need from you, then use the wording in referral request messages that get replies.

Step 6: How do you prepare for GCC interviews?

Prepare for GCC interviews by learning the rounds the company typically runs and practising each kind separately. A common shape is a recruiter screen, one or two technical rounds covering coding and the role's fundamentals, a design round for experienced candidates, and a hiring manager conversation. Companies differ, so ask the recruiter what to expect.

The guide to the GCC AI interview process explains what each round tests. Three habits help in all of them:

• Be able to explain every line on your resume, including why you made each technical choice.
• Practise aloud, with a timer, not only on paper.
• Prepare a few short stories about ownership, disagreement and failure for behavioural questions.

How should you organise the search?

Organise the search with a simple tracker and a fixed weekly routine. A job search run from memory loses follow-ups and repeats mistakes.

A tracker needs only a few columns: company, role and link, date applied, referral contact and status, interview stage, and next action with a date. Review it once a week and act on every next action.

A weekly routine that fits around a full-time job:

• Two sessions on skills or the project.
• One session on applications and referral messages for that week's five companies.
• One session of interview practice once applications are going out.

After each rejection or interview, note what was asked and where you were weak, then feed that back into the skill work.

Which mistakes slow a GCC job search?

The mistakes that slow a GCC job search are mostly about order and focus.

• Applying before the resume is ready. The first applications go to your best targets with your weakest document.
• Searching only by job title on one portal. Many centres' roles are easiest to find on their own career pages.
• Learning without building. Months of courses with nothing to show.
• Asking for referrals with no role in mind. The person cannot act on "any opening".
• Chasing every role. Three different resumes for three unrelated tracks, none convincing.
• Stopping at the offer. Notice period and joining date need a plan too.

If you want the plan laid out for you, create a free account on The GCC Engineer. The roadmap follows the same path in five steps, from understanding the market and your gap to upskilling, applying and interviews.