10 AI Prompts Every GCC Recruiter Should Save Right Now
AI tools like Claude and ChatGPT are not going to replace GCC recruiters. They will, however, create a widening gap between recruiters who use them well and those who do not. Here are 10 recruiter AI prompts to put yourself ahead of others. Bookmark them.
The prompts below are not theoretical. Each one has been structured for the specific contexts GCC talent teams face — passive GenAI engineers, product manager competency interviews, comp benchmarking conversations, and more.
Prompt 1: Source a Passive GenAI Engineer
Use case: Writing a cold LinkedIn InMail or email to a senior engineer currently at a product company or GCC who is not actively looking.
Prompt:
You are a senior technical recruiter at [Company Name], a Global Capability Center for [Parent Company / Industry — e.g., a Fortune 500 financial services firm].
Write a personalised LinkedIn InMail to [Candidate Name], a Senior ML Engineer with [X] years of experience currently at [Current Employer]. Their LinkedIn shows expertise in [LLM fine-tuning / RAG pipelines / model deployment — pick what's relevant].
The role I'm hiring for is: [Job Title], focused on [2-sentence summary of what the team is building].
The message should:
- Open with a specific observation about their work or background, not a generic compliment
- Explain why this specific role at a GCC (not a startup or IT services firm) is a meaningful career move for someone at their stage
- Be under 150 words
- End with a low-friction CTA — a 20-minute call, not "please apply"
- Sound like a peer, not a recruiter template
Why this works: Most passive outreach fails because it is either too long or too generic. The constraint on word count forces precision, and asking the AI to "sound like a peer" consistently produces warmer, less corporate copy than open-ended drafting.
Prompt 2: Write a GCC-Specific Job Description That Attracts Product Talent
Use case: Drafting a JD for a Product Manager role that competes with tech product companies, not just other GCCs.
Prompt:
Write a job description for a [Senior Product Manager / Principal PM] role at [GCC Name], the India capability center of [Parent Company], a [industry] company headquartered in [location].
The role sits within the [platform / data / payments / growth] product team and owns [describe the product or problem space in 1–2 sentences].
The JD should:
- Lead with the product problem being solved, not with company boilerplate
- Describe the tech stack and data scale candidly (be specific: "you will work with X data points daily" beats "large-scale data")
- Include a section called "What makes this different from a startup PM role" — address the GCC perception gap directly
- List must-have vs. nice-to-have skills separately
- Avoid hollow phrases like "fast-paced environment", "go-getter", or "passionate"
- Be between 450 and 600 words
Why this works: The biggest conversion problem for GCC PM roles is the perception gap — candidates assume GCC means slow, bureaucratic, or derivative. Asking the AI to address this directly in the JD positions the role honestly and filters for the right mindset.
Prompt 3: Evaluate a Candidate's GitHub Profile Before a Technical Screen
Use case: You have a candidate's GitHub URL and want to form an intelligent view before briefing the hiring manager or designing the technical screen.
Prompt:
I am a recruiter preparing for a technical screening call with a candidate applying for a [Senior Data Engineer / ML Engineer / Platform Engineer] role at a GCC.
Here is a summary of their GitHub activity: [paste 3–5 bullet points describing their repos, stars, languages used, and recent commit activity — you can pull this manually in 5 minutes]
Based on this, help me:
1. Identify 2–3 technical strengths this profile suggests
2. Flag 1–2 areas that are unclear or concerning for the role (e.g., no production-grade repos, limited collaboration activity)
3. Suggest 3 specific technical questions I should ask the hiring manager to verify before the screen
4. Give me 2 questions I can ask the candidate on the call to probe the depth behind the profile
Keep the tone analytical, not evaluative — I am forming hypotheses, not verdicts.
Why this works: Recruiters often feel under-equipped going into technical screens for engineering roles. This prompt does not pretend to make the AI a technical evaluator — it structures your pre-screen thinking so you have sharper hypotheses going in, which makes the conversation more productive.
Prompt 4: Generate Competency-Based Interview Questions for a GCC Product Manager
Use case: Building an interview guide for a PM role at a GCC, where the competencies differ from pure-play startup or IT services PM roles.
Prompt:
Generate a competency-based interview question bank for a [Senior Product Manager] role at a GCC (Global Capability Center) within a [financial services / e-commerce / healthcare] company.
The competencies to cover are:
1. Stakeholder management across geographies (India team + global HQ)
2. Building product roadmaps under organisational constraints
3. Data-driven prioritisation at scale
4. Influencing without authority in a matrixed org
5. Technical fluency — ability to work with engineering teams on architecture decisions
For each competency, provide:
- One STAR-format behavioural question
- One situational / hypothetical question
- Two follow-up probing questions
- What a strong vs. weak answer looks like (brief indicators, not scripts)
Make the questions specific to the GCC operating context — not generic PM interview questions.
Why this works: Generic PM interview banks do not capture GCC-specific challenges like navigating global-local stakeholder tension or building roadmaps when product strategy is set upstream. This prompt produces interview questions that actually differentiate strong GCC PMs from those who will struggle in the model.
Prompt 5: Summarise Panel Interview Feedback Into a Hiring Decision Brief
Use case: You have received feedback from three or four interviewers and need to synthesise it into a structured brief for the hiring manager or HRBP before the debrief call.
Prompt:
You are a recruiting coordinator summarising interview panel feedback for a hiring decision. Below is raw feedback from [3/4] interviewers for the role of [Job Title] at [Company Name].
[Paste raw feedback — bullet points, notes, or short paragraphs from each interviewer]
Synthesise this into a structured hiring decision brief that includes:
1. Overall signal summary (strong hire / hire / borderline / no hire) — inferred from the feedback, not invented
2. Top 3 strengths consistently noted across the panel
3. Top 2 concerns or gaps raised
4. Any conflicting signals between interviewers (flag these clearly — do not resolve them artificially)
5. Recommended discussion points for the debrief call
6. One suggested follow-up question if the team wants to probe a specific gap before deciding
Keep the brief to one page. Be neutral — do not advocate for a hire or reject. Your job is to make the debrief call more efficient.
Why this works: Debrief calls in GCC environments often involve interviewers across time zones. A clean synthesis brief reduces the call time needed and ensures no feedback is quietly dropped. The instruction to flag conflicting signals rather than resolve them is particularly important — that tension is often the most useful signal.
Prompt 6: Write a Compensation Offer Justification Email to a Candidate
Use case: The candidate has a competing offer. You need to write a structured email that contextualises your offer without just matching the number.
Prompt:
Write an email to a candidate, [First Name], who is a [Job Title] with [X] years of experience. They have a competing offer from [type of company — a startup / another GCC / an IT services firm] that is [₹X lakh higher / broadly similar in CTC].
Our offer is: [Fixed: ₹X LPA | Variable: Y% | ESOPs/RSUs: describe if applicable | Other benefits: list key ones]
The email should:
- Acknowledge the competing offer respectfully — no pressure tactics
- Explain the total compensation picture beyond CTC (stability, equity, learning trajectory, scope)
- Address the GCC value proposition specifically — what this role offers that the competing offer does not
- Include a line asking what matters most to them in their decision so we can respond to the real concern
- Be warm, direct, and under 250 words
- Not promise anything that has not been approved
Why this works: Offer-stage communication is where many GCC recruiters lose candidates to startups or product companies. The prompt's instruction to ask what matters most to the candidate is deliberately embedded — it converts a one-way push into a dialogue, which is where GCC offers are actually won or lost.
Prompt 7: Benchmark a Compensation Package Against Market Data
Use case: Before making an offer, you want to frame a market comparison brief for your hiring manager or compensation team.
Prompt:
I am a recruiter preparing a compensation benchmarking summary for a [Job Title] role in [City — Bengaluru / Hyderabad / Pune / Chennai] at a GCC in the [BFSI / tech / healthcare / retail] sector.
The candidate has [X] years of experience with specialisation in [skill area]. Current CTC: ₹[X] LPA. Our offer under consideration: ₹[Y] LPA fixed + [Z]% variable.
Help me structure a 1-page benchmarking brief that:
1. Identifies the relevant comparator segments (GCC peers, Indian product companies, IT services)
2. Lists the data points I should gather from benchmarking tools like Radford / Mercer / internal surveys
3. Frames the offer positioning (P50 / P75 / P90) relative to segment
4. Suggests 2–3 non-cash levers I can use if the fixed component cannot be moved
5. Flags any risk of counter-offer from the current employer based on role and seniority level
Note: I will fill in the actual salary data — you are helping me structure the analysis framework.
This is a good moment to mention: if you want live market data while preparing this brief, GCC Pay Compass is GCC Journal's AI-powered salary comparison tool that lets you benchmark compensation across Global Capability Centers, Indian IT Services, and Product companies using live market data. Use it alongside your internal ranges to triangulate an offer that holds.
Prompt 8: Draft a Rejection Email That Keeps the Relationship Open
Use case: You need to decline a candidate who reached the final round but was not selected — and you want them to consider future roles.
Prompt:
Write a rejection email for a candidate, [First Name], who interviewed for [Job Title] at [Company Name] and reached [Round 2 / Final Round]. The reason for not moving forward is [one of: stronger candidate selected / scope mismatch / team restructure — pick one].
The email should:
- Be personal and specific, not templated — reference one thing from their interview or background
- Explain the decision briefly without being vague ("we went with another direction" is not acceptable)
- Keep the door genuinely open for future roles — only if that is true
- Offer a specific next step if appropriate (e.g., "I'll reach out when we open X role in Q3")
- Be under 150 words
- Leave the candidate feeling respected, not managed
Why this works: According to Nasscom's Talent Landscape Report, India's GCC talent pool is concentrated — particularly in cities like Bengaluru and Hyderabad, where the same senior candidates circulate across a relatively small set of GCCs. A well-written rejection email is a long-term pipeline investment.
Prompt 9: Build a Structured Scorecard for a GCC Engineering Manager Role
Use case: Your hiring panel needs a consistent evaluation framework before interviews begin.
Prompt:
Create a structured interview scorecard for an Engineering Manager role at a GCC. The team this person will manage has [10–15] engineers across [frontend / backend / data / full-stack] disciplines, working on [brief product or platform description].
The scorecard should cover 6 dimensions:
1. Technical depth and credibility
2. Cross-functional and stakeholder communication
3. People management and team development
4. Delivery and execution in an ambiguous environment
5. GCC operating model fluency (global-local alignment, working with HQ)
6. Strategic thinking and roadmap ownership
For each dimension:
- Define what "exceeds expectations", "meets expectations", and "below expectations" looks like
- Suggest 1–2 interview signals to listen for
- Rate on a 1–4 scale with anchor descriptions
Format as a table. Keep descriptions concise — this is a working document for busy interviewers, not a training manual.
Why this works: GCC Engineering Manager hiring is where scorecard consistency matters most. Deloitte's research on GCC talent practices has highlighted that inconsistent evaluation criteria — particularly for leadership roles — is one of the top contributors to early attrition in senior GCC hires. A structured scorecard reduces panel subjectivity and creates a defensible, auditable hiring process.
Prompt 10: Prepare a Candidate for the GCC Culture and Operating Model
Use case: You want to set a shortlisted candidate up for success before their interviews, and help them understand what working in a GCC is genuinely like.
Prompt:
Write a pre-interview preparation email for a candidate, [First Name], who is shortlisted for [Job Title] at [GCC Name], the India center of [Parent Company].
The candidate is currently at [a startup / an IT services company / another GCC] and may have limited exposure to how GCCs operate.
The email should:
- Explain in plain language how GCCs differ from IT services delivery and from standalone product companies
- Set honest expectations about the operating model: global stakeholders, center-of-excellence vs. captive delivery models, career progression
- Share 2–3 practical tips for how to present their experience in the context of what GCC hiring managers actually look for
- Mention 1–2 questions they should ask the panel to demonstrate genuine interest in the GCC model
- Be warm and helpful in tone — this is a recruiter investing in a candidate's success, not a legal disclaimer
- Be under 300 words
Why this works: Candidates who understand the GCC operating model perform better in interviews and accept offers at higher rates. Industry estimates suggest a meaningful portion of GCC offer declines at final stage come from candidates who did not fully understand the role context before the process began. This prompt flips recruiter prep from internal to candidate-facing — a simple but high-leverage shift.
A note on how to use these: paste the prompt into Claude or ChatGPT, fill in every bracketed field with your actual role and company details, and treat the first output as a strong draft — not a final message. The best results come when you add one or two sentences in your own voice after the AI draft.
How to Get the Most Out of These Prompts
Three principles to maximise output quality:
Be specific with context. The more accurately you fill in the bracketed fields — role seniority, company sector, candidate background — the more precisely useful the output. Vague inputs produce generic outputs.
Treat first drafts as 80% done. AI output at its best is a strong first draft. Add your company’s specific tone, a detail you know about the candidate, or a current market observation that the AI cannot have. That last 20% is what makes it land.
Build a prompt library. Save these ten prompts in a shared Notion page or Google Doc for your team. The EY GCC Pulse Survey 2024 found that GCC HR functions are increasingly centralising talent operation toolkits — a shared prompt library is a low-cost, high-impact version of that centralisation.
The Competitive Edge Is Already Being Built
The GCC recruiters who will lead their functions in the next two years are not waiting for their company to deploy an enterprise AI tool. They are building personal operating systems right now — using freely available tools like Claude and ChatGPT with well-crafted prompts to compress the distance between a req opening and a quality slate.
These ten prompts cover the highest-leverage moments in the GCC recruitment lifecycle: sourcing passive technical talent, building evaluation rigour, managing offer-stage conversations, and investing in candidate experience. None of them replace judgment. All of them make judgment faster and better-supported.
Save the prompts. Adapt them to your roles. And then adapt them again when you see what works. That iteration loop — human judgment refining AI output — is the actual skill that separates good recruiters from average ones.