Skills to Put on Your Resume

Why the skills section decides whether a human ever reads your resume

Every major Indian employer now runs incoming resumes through an applicant tracking system before a recruiter sees them. Naukri RMS, Workday, Greenhouse, Lever, Zoho Recruit, and the bespoke pipelines at TCS, Infosys, and Wipro all do the same thing first. They parse your resume into text, run it against the job description, and score keyword overlap. The skills section is where this match is won or lost. Get it right and the resume reaches a recruiter. Get it wrong and a human never sees the document at all. The work experience section can be brilliant; if your skills block does not contain the keywords the JD asks for, the brilliance never gets read.

• The ATS reads your skills block as a flat list of tokens, not as prose. Each comma-separated entry is a potential keyword match.
• The recruiter scans the same block for 3 to 5 seconds, looking for the must-have skills they highlighted in the JD.
• Both readers need the same thing: the right 10 to 15 skills, in the right order, named the way the industry names them.
• Generic skills (MS Office, communication, teamwork) do not move the needle. Specific, JD-matched skills do.

Hard skills, soft skills, transferable skills - what to include and in what ratio

Resumes that read well in India usually mix three categories of skills, and the ratio shifts by seniority. Freshers lean heavier on hard skills because that is what they can prove with coursework, projects, and internships. Mid-career and senior professionals lean on transferable skills because that is what the role they are applying for actually rewards. Soft skills come last in both cases, kept short and demonstrated through bullet points rather than listed at length.

• Hard skills are measurable, teachable abilities tied to a specific tool, language, or method. Examples: Java, Python, SQL, Tableau, AutoCAD, financial modelling, IFRS, Tally, SEO, Six Sigma Black Belt.
• Transferable skills are abilities you carry across roles and industries. Examples: project management, stakeholder communication, data-driven decision making, P&L ownership, vendor negotiation, ATS recruiting, scrum facilitation.
• Soft skills are interpersonal qualities. Examples: leadership, problem solving, adaptability, attention to detail, ownership. List 3 to 5 maximum and demonstrate them in your bullet points, never just declare them.
• Domain knowledge is its own category in regulated industries (banking, healthcare, pharma, audit). Examples: KYC/AML, RBI guidelines, HIPAA, GxP, ICH-GCP. Include these explicitly if relevant.
• Ratio rule of thumb. Fresher: 70 percent hard + 20 percent transferable + 10 percent soft. Mid-career: 50/35/15. Senior: 35/50/15.

Role-wise skills that actually help in the Indian job market

Below is the role-to-skill mapping we have built from reviewing thousands of resumes across Indian IT services, product companies, banks, consulting firms, and PSUs. Each entry shows the 10 to 12 skills hiring managers in that role expect to see when they scan a resume. Use this as a starting point and then layer in the specific keywords from the JD you are targeting.

30 high-leverage hard skills (with the role each one signals to)

Pick the ones that match your actual experience and the role you are targeting. Each entry below names the skill the way the industry phrases it (which is what the ATS scans for) and the role family that values it most.

15 soft-skill claims to cut from your resume (and what to write instead)

Soft skills are not bad. Soft skills written as bare claims with no evidence are. Every recruiter in India has read 'team player', 'good communication skills', and 'hard worker' so many times the words no longer mean anything. Below are the soft-skill claims that are dead on arrival, and the replacement frame that actually lands.

How to format the skills section so it survives ATS parsing

The cleanest skills section is a single-column block with skills grouped by category. Indian recruiters who scan on mobile - which is most of them on Naukri and LinkedIn - need the section to be readable in 3 to 5 seconds. ATS parsers need it to be plain text without graphics. Both readers reject the same formatting mistakes, so the right format wins on both sides.

Skills for freshers vs experienced - different stakes, different strategy

The skills section serves a different role at every career stage. For a fresher, it is proof. You do not have years of shipped work, so the skills you list are evidence that you can do the job from day one. For a mid-career professional, the skills section is a keyword bank for the ATS plus a quick credibility scan for the recruiter. For a senior leader, the skills section gives way to a more strategic frame - it is about the systems you have built and the teams you have run, not the tools you have touched.

• Freshers and final-year students: list 12 to 15 skills, lead with the technical stack the role asks for, and back every claim with at least one project or internship that actually used that skill.
• 0 to 3 years of experience: list 12 to 15 skills, prune anything you have not used in the last 12 months, and add the specific frameworks and tools you have shipped with at work.
• 3 to 7 years of experience: list 12 to 18 skills grouped by category. Add domain knowledge (BFSI, healthcare, e-commerce, edtech) as its own line if relevant. Drop entry-level certifications.
• 7+ years of experience: list 10 to 15 skills focused on the systems, methodologies, and leadership skills the senior role needs. Tools matter less; strategic skills matter more.
• Career switchers: lead with the transferable skills relevant to the new field, then list any new technical skills you have built (courses, side projects, certifications) to bridge the gap.

How to match your skills to the job description (the ATS keyword game)

The single highest-leverage skills tactic in 2026 is to read the job description carefully and mirror its exact phrasing in your skills section. Most candidates list the skill the way they think of it; the ATS scores you against the way the JD phrases it. If the JD says 'React.js' and you write 'ReactJS', some parsers count it as a match and some do not. If the JD says 'business intelligence' and you write 'BI', you might lose the match. The defensive move is to use both the long form and the abbreviation when in doubt. This is not gaming the system. It is meeting the system on its terms so a human gets to read your work.

• Read the JD twice. Highlight every must-have skill and every nice-to-have. The must-haves are usually in the first 5 bullets and the qualifications section.
• Make a list of the JD keywords that you actually have. Be honest - listing skills you cannot defend in a 5-minute conversation will hurt you in the interview.
• Use the exact phrasing from the JD in your skills section. "React.js" if they wrote that, "React" if they wrote that.
• Where the JD uses an abbreviation, use both forms ("Business Intelligence (BI)", "Search Engine Optimization (SEO)"). The ATS scores either token.
• Reorder your skills block so the must-haves appear first. Some ATS parsers weight position.
• Mirror domain language. If the JD is for a fintech role and uses "Payments", "PCI DSS", "tokenization" - those exact phrases should appear if you have the experience.
• For Naukri profiles, add the same keywords to your Naukri "Key Skills" field. Recruiters search this field directly when they look for candidates.

Skills to avoid putting on your resume in 2026

Some skills are no longer worth the line they take. Either they are so generic they say nothing, they reveal that your resume is dated, or they actively reduce your credibility. Cut them and use the space for something the JD actually asks for.

• MS Office / Microsoft Word / PowerPoint. Universal baseline. Do not list. The only exception is advanced Excel for finance/analyst roles - and then write 'Excel (advanced - VBA, Power Query, pivot tables)'.
• Email / Gmail. Cut.
• Internet research. Cut.
• Typing speed. Only relevant for transcription, BPO data entry, and call-centre roles. Cut otherwise.
• Browsing the internet. Cut.
• Languages you cannot actually use professionally. Do not list 'French' if you took 3 classes in 8th standard. List only languages you can work in.
• Tools that died before 2018. Flash, Silverlight, Internet Explorer compatibility, jQuery 1.x. If you list them, you are dating yourself.
• Generic 'computer skills'. Either name the tools or cut.
• Skills with no context - 'AI', 'cloud', 'data science' on their own. Replace with the specific tool or library you have used.
• Outdated certification badges that are no longer renewed (lapsed AWS, lapsed PMP). List only currently valid certifications.

Common mistakes when writing the skills section

These are the patterns we see most often when reviewing Indian resumes through Pika's AI roast and through 1-on-1 mentoring. Every one of them is fixable in 10 minutes and every one of them costs candidates interviews they should have got.

• Listing every tool you have ever opened. Recruiters discount long lists - they read as padding. Stick to 12 to 15 skills you can defend.
• Padding with soft-skill cliches ('team player', 'hard worker'). See the cuts list above.
• Misordering skills - putting your weakest skill first because it is alphabetically earliest. Order by relevance to the JD, not by alphabet.
• Listing a framework without the underlying language ('Spring Boot' without 'Java', 'React' without 'JavaScript/TypeScript'). Always include both.
• Vague proficiency claims ('expert in everything'). Replace with measurable evidence in Experience.
• Skill bars and rating dots that do not survive ATS parsing.
• Stuffing keywords you do not have. Recruiters interview to skills; if you cannot answer a single basic question on a skill you listed, the entire resume loses credibility.
• Missing the JD's exact phrasing. 'Node.js' vs 'NodeJS' vs 'Node' - mirror the JD.
• Listing entry-level certifications when you have 5+ years of experience. Reads as immature.
• Putting Skills below References or hidden on page 2. Skills should appear in the top half of page 1 for any technical role.