Resume format · IT services
Resume for HCLTech: a format for lateral IT-services engineers
Our research holds no HCLTech-specific application details, so this page invents none. It covers what holds across large IT-services employers when you apply with two to four years of delivery work behind you.
- Last reviewed
- October 2026
- Reading time
- 4 min
In short
- We have no HCLTech-specific process details. The advice is for lateral applicants to large IT-services firms.
- Put several projects under one employer as Role and Project entries, so a parser reads one job and not several.
- Add a technical-environment line per project, leave out confidential client data, and spell out company names and titles.
- Show releases, defects, SLAs, users served and response-time cuts, not duties.
What we know, and what we do not
Two years in, the shape of the page changes
After about three years, Class X and XII marks have done their work and should come off. The summary stops describing a degree and starts naming years, domain and stack. Skills move above Education, because the reader is now asking what you can deliver, not where you studied. One page is the safer default, and two are acceptable only when every line is a result.
One employer, several projects
Indian IT resumes list projects under each employer. The risk is that a parser reads each project line as a separate job and inflates or scrambles your tenure. Keep one employer entry with a clear title and dates, then describe projects inside it with a Role and Project line and a technical environment. Greenhouse's parsing guidance also warns that bare company names and abbreviated titles cause trouble, so spell both out.
One employer, two roles, one technical-environment line
- Lead a 4-person pod that delivers 2 releases a month, with no rollback in the last 6.
Client names and confidentiality
The client's industry is usually safe to state, such as 'UK insurer' or 'US retail bank'. The client's name may be covered by your contract, so check your company's policy before using it. Never include internal URLs, customer data, credentials or system diagrams. The interviewer wants your contribution, not the client's secrets.
Bullets that show delivery
- Before
Worked on production support
AfterResolved 85 production incidents in a Java and Oracle application over 6 months, with 92% closed inside the 4-hour SLA
WhyVolume, period and an SLA figure. 'Worked on' says only that you were assigned.
- Before
Part of the testing team
AfterExecuted 450 test cases a sprint for an insurance portal and logged 60 defects in JIRA, 52 accepted by the developers
WhyThe pace, the output and the acceptance rate show the quality of your reports.
- Before
Involved in release activities
AfterCoordinated 9 releases across 3 environments with a rollback checklist that cut release-night issues from 5 to 1
WhyNames the count, the scope and a change that other people could see.
Keywords for a lateral move
Use the technology names the posting uses, exactly, and keep a skills list of 12 to 15 that you can discuss for ten minutes each. If the posting asks for years in a technology, state years in the summary only when they are accurate, such as '3 years of Java'. Leave notice period and current CTC off the resume; portals and recruiters ask for them separately.
Before you submit: a short checklist
- The official careers page, not a forum post, is my source for the current process.
- Company names and job titles are spelled out in full, with month-and-year dates.
- Each employer appears once, with projects described inside it.
- Every project has a technical-environment line and no confidential client data.
- At least two of every three bullets carry a number.
- School marks are gone and the summary names years, domain and stack.
- Notice period and CTC are not on the page.
Questions people ask
Should I list every project I have worked on?
No. Choose the two or three most relevant to the target role and compress the rest to a line. Beyond about three years a second page is acceptable only if every line on it is a result.
Do I need a Technical Environment line?
It is common on Indian IT-services resumes and helps keyword search. Keep it to one line per project and list only technologies you used in that project.
How do I describe a support or maintenance role?
With volumes and times: incidents a month, SLA adherence, time to resolve, defects removed. 'Handled support' says nothing a reader can weigh.
Can I include my notice period?
Leave it off. Portals and recruiters ask separately, and a figure on the resume can narrow your options before the first call.
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.
- 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.
- Jobrise: 15 resume mistakes freshers make in Indiahttps://jobrise.io/en/blog/resume-mistakes-freshers-india/A 500-resume review by one career site.
Keep reading
- GuideATS-friendly resume in India: what parsers read and what trips them
- GuideResume bullets with numbers when you have none
- GuideWhat to remove from an Indian resume, and when to keep it
- GuideResume for career switchers and gap years: say it plainly
- Employer formatResume for Accenture: writing evidence for each qualification
- Employer formatResume for Capgemini: tailoring to the posting you are applying to
- 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.