Resume format · IT services
Resume for Capgemini: tailoring to the posting you are applying to
We hold no verified details about Capgemini's process, so this page does not describe it. It is for a different situation that many applicants share: you found a specific posting and want your resume to answer it honestly.
- Last reviewed
- October 2026
- Reading time
- 4 min
In short
- We could not verify Capgemini's current process or systems. Follow the posting and the company's careers page.
- Tailoring is reordering and renaming true things. It is never adding skills you lack.
- Map each must-have in the posting to a line on your resume. Leave out what you cannot prove.
- Keep one master resume and make a tailored copy for each posting. The facts never change between copies.
What we know, and what we do not
Tailoring is reordering, not rewriting the truth
A March 2025 survey by Resume Now of US respondents reported that 78% of hiring managers said personalised details signal genuine fit, and that unpersonalised AI-written resumes were more likely to be rejected. It is a vendor survey from another market, so read it as direction. The direction matches what Indian recruiters describe: a resume that clearly answers the posting beats one that answers nothing in particular.
Tailoring does not mean adding a skill the posting names. It means moving the most relevant true thing to the top, using the posting's name for a skill you really have, and putting the matching job title in the summary.
A six-step tailoring pass
- 01
Copy the requirements
Paste the posting into a document and split it into must-haves and nice-to-haves.
- 02
Map each must-have to a line
Find the bullet, project or certificate that proves it. Note where there is none.
- 03
Reorder
Move the best-matching project or role to the top of its section.
- 04
Rewrite the summary
Name the posting's job title and the three or four matching skills you actually have.
- 05
Reorder the Skills line
Put the skills the posting names first, but only if they are on your resume already.
- 06
Save a copy
Keep the tailored file separate from the master, named for the role.
| Posting says | Your line | If you have nothing |
|---|---|---|
| Python automation with pytest | Automated 140 UI and API cases in Python with pytest, shortening regression from 2 days to 5 hours | Not applicable here |
| Experience with CI pipelines | Run the suite on every pull request through GitHub Actions | Not applicable here |
| Performance testing with JMeter | No line on this resume | Leave it off. Do not add it. If you are mid-course, say so once and truthfully. |
A generic summary and a tailored one
- Before
Test engineer with 1.5 years of experience seeking growth in a reputed company
AfterTest automation engineer with 1.5 years in IT services, with 140 UI and API cases automated in Python and pytest. Applying for the Python automation role that uses REST testing and CI.
WhyUses the posting's title and three of its skills, each of which is true and shown further down the page.
Keep your profiles in step
A tailored resume still has to agree with your LinkedIn and Naukri profiles on titles, employers and dates. Change the emphasis in the copy you send, and keep the facts in your profiles identical, because recruiters and verification firms compare them.
Before you submit: a short checklist
- I split the posting into must-haves and nice-to-haves.
- Each must-have I claim maps to a line on the resume.
- I added no skill I cannot demonstrate in an interview.
- The summary names the posting's title and only skills I have.
- The tailored file is saved separately and named for the role.
- Titles and dates still match LinkedIn and Naukri.
Questions people ask
Should I make a new resume for every posting?
Keep one master resume and make a tailored copy for each posting. Change the order, the summary and the skill order. Never change a fact, because employers compare copies with your profiles.
How do I know which words in the posting matter?
Start with the job title, then the skills that are repeated or listed as required. Jobscan describes its own match rate as counting repetition, so a skill that appears several times in a posting is usually a priority.
Can I copy phrases from the posting into my resume?
Use its names for skills you have, such as 'REST API testing'. Do not copy its sentences. Copied lines read as generic and detectors treat verbatim stuffing as a warning sign.
Sources
Numbers on this page come from these sources, and the text says where a source is a vendor blog or a survey. Where a claim has no source here, it is guidance, not fact.
- Resume Now: AI applicant report, March 2025https://www.resume-now.com/job-resources/careers/ai-applicant-reportA vendor survey of US respondents: personalised details and unpersonalised AI resumes.
- Jobscan tutorial: how the match rate is builthttps://www.jobscan.co/jobscan-tutorialA vendor's description of its own tool, including the role of repetition.
- Greenhouse: Unsuccessful resume parsehttps://support.greenhouse.io/hc/en-us/articles/200989175-Unsuccessful-resume-parseCauses of failed parses: header and footer details, tables, text boxes, bare company names, abbreviated titles.
- ATS Verification: Resume guidance for Indiahttps://atsverification.com/for/india/Year-only date ranges and tenure calculation; employer ATS landscape. A secondary source.
Keep reading
- GuideATS-friendly resume in India: what parsers read and what trips them
- GuideResume bullets with numbers when you have none
- GuideResume summary for freshers: how to write two good lines
- GuideResume for career switchers and gap years: say it plainly
- Employer formatResume for HCLTech: a format for lateral IT-services engineers
- Employer formatResume for Accenture: writing evidence for each qualification
- Employer formatResume for Cognizant: name the domain, show the testing
Next step
Build yours in the chat
Answer a few questions, one at a time. The reviewer drafts each line, asks for the numbers it cannot guess and never adds a fact you did not give. Already have a resume? Check it first and see what a parser reads.