Skills for Resume: 100+ Examples for Freshers and Jobs
Choose role-specific skills you can prove, match the language of the job description accurately, and keep the section clear for recruiters and resume software.
PikaResume guidance
What skills should I put on my resume?
Put 10 to 15 skills that the job description asks for and that you can prove through work, projects, education, or certifications. Prioritise role-specific tools and methods, add a few relevant transferable skills, and demonstrate soft skills such as leadership or communication inside achievement bullets instead of listing unsupported adjectives.
Published by Pika Resume · Reviewed · Editorial standards
Pick a template to get started
Pick A Resume
Template
and build your resume in minutes!Pika users got hired at
By Aman Juneja, CEO, UIX Labs - built Pika Resume. Reviewed 2026-08-28.
Best skills to put on a resume
The best skills for a resume are the abilities the target role needs and that you can support with work, projects, coursework or certifications. Start with technical and domain skills, add a small number of relevant soft skills, and use the terminology from the job description only when it accurately describes your experience.
- Technical skills: tools, languages and methods such as SQL, Tally Prime, AutoCAD, Java or financial modelling.
- Computer skills: role-relevant software such as Excel, Power BI, Figma, Salesforce or SAP.
- Domain skills: knowledge such as GST, KYC and AML, supply planning, curriculum design or clinical documentation.
- Transferable skills: project management, stakeholder communication, analysis and negotiation, backed by specific results.
- Soft skills: leadership, adaptability and attention to detail, demonstrated in experience bullets instead of listed as unsupported claims.
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.
While you're here: check your resume for common ATS risks
Upload your resume, then sign in to run and save the free diagnostic. You will see your score, category breakdown, and issue counts.
Check my resume freeRole-wise skills that actually help in the Indian job market
Use this role-to-skill mapping as a starting point, then compare it with the requirements of the vacancy you are targeting. Keep only the skills you genuinely have and add a project, achievement or work example that supports the most important ones.
| Role / industry | Relevant skill examples | Evidence to add |
|---|---|---|
| Software engineer (Java backend) | Java, Spring Boot, REST APIs, microservices, SQL, MongoDB, AWS or GCP, Docker, Git, Kafka, JUnit, system design | A concrete scale claim - "designed APIs serving 50M requests/day" - tied to a specific service. |
| Software engineer (frontend) | JavaScript, TypeScript, React, Next.js, HTML, CSS, Redux or Zustand, REST/GraphQL, accessibility (WCAG), Storybook, Jest, Webpack | A live link to a portfolio site or a contribution to a well-known open-source repo. |
| Full-stack engineer | Node.js or Python, React, TypeScript, PostgreSQL, REST APIs, Docker, AWS, system design, Git, testing frameworks, CI/CD | A side project shipped end-to-end with a public URL. |
| Data analyst | SQL, Python (pandas, numpy), Excel (advanced), Tableau or Power BI, statistical analysis, A/B testing, data cleaning, dashboarding, business communication | A dashboard the recruiter can actually see. Hosted Tableau Public link or a screenshot in the portfolio. |
| Data scientist / ML engineer | Python, scikit-learn, TensorFlow or PyTorch, SQL, statistical modelling, feature engineering, MLOps, Docker, AWS Sagemaker or GCP Vertex, NLP or computer vision, Git | A Kaggle medal or a deployed ML model with a public endpoint. |
| Product manager | Product strategy, roadmapping, user research, A/B testing, SQL, analytics (Mixpanel, Amplitude, GA4), Jira, Figma, stakeholder management, PRD writing, OKRs | A shipped feature with measurable outcome - 'launched X, drove Y percent lift in Z'. |
| Performance marketing / growth | Google Ads, Meta Ads, SEO, GA4, Mixpanel, attribution modelling, CRO, email marketing, marketing automation, SQL, Looker or Tableau, copywriting | A campaign with a quantified result - 'scaled spend from 5L to 50L per month at sub-2 ROAS'. |
| Content marketing / SEO | Content strategy, SEO (on-page, technical, link building), keyword research (Ahrefs, Semrush), GA4, Search Console, copywriting, Webflow or WordPress, schema markup, content audits | A portfolio of published articles ranking on page 1 for non-trivial keywords. |
| Investment banking / corporate finance | Financial modelling, valuation (DCF, comps, precedent transactions), Excel (advanced), PowerPoint, Bloomberg Terminal, M&A processes, IFRS, due diligence, pitch deck design, SQL | A live deal closed or a live IPO worked on - named, with the deal size. |
| Chartered accountant / audit | Statutory audit, internal audit, IFRS, Ind AS, GST, income tax, transfer pricing, SAP FICO or Oracle Financials, Tally, Caseware, financial reporting, risk assessment | A specific client engagement at scale - 'led audit of a 500 crore listed entity'. |
| Operations / supply chain | S&OP, demand forecasting, inventory optimisation, SAP MM or Oracle SCM, Six Sigma, lean manufacturing, KPI dashboarding, vendor management, contract negotiation, P&L ownership | A cost-out or service-level win - 'reduced inventory days from 60 to 38, saved 12 crore'. |
| UX / product designer | Figma, Sketch, user research, wireframing, prototyping, design systems, usability testing, interaction design, accessibility (WCAG), Webflow, Framer, basic HTML/CSS | A case study showing the problem, the process, and the shipped outcome. Behance, Dribbble, or a personal site. |
30 technical and hard skills with matching roles
Pick only the skills that match your actual experience and the role you are targeting. Each entry uses common industry wording and names the role family where the skill is often relevant.
7 transferable skills worth proving on a 2026 resume
These skills apply across many knowledge-work, customer-facing, and operations roles. They are not a substitute for the technical skills in the job description. Add only the ones you can support with a project, result, or experience bullet.
| Transferable skill | What credible evidence looks like |
|---|---|
| AI tool fluency | Name the tool and workflow you have genuinely used, such as Claude for research synthesis or GitHub Copilot for test scaffolding. |
| Data literacy | Show how you read a dashboard, queried data, or turned a metric into a decision rather than writing only "analytical skills". |
| Written communication | Point to decision documents, client reports, technical writing, or an internal knowledge base you created or improved. |
| Project management | Name the project, tool, timeline, stakeholders, and outcome you coordinated from start to finish. |
| Cross-functional collaboration | Describe the teams you aligned and what shipped, changed, or improved because of that coordination. |
| Critical thinking | Use a bullet where you challenged an assumption, tested alternatives, and changed the plan using evidence. |
| Stakeholder management | Show the audiences you handled, the decision you helped reach, and how you managed competing priorities. |
How to list AI skills without sounding generic
For roles where AI tools are relevant, name the tool, the workflow, and the result. A bare phrase such as "AI tools" or "prompt engineering" is too vague to help a recruiter and too easy to challenge in an interview.
15 soft-skill claims to replace with evidence
Soft skills can help when the resume proves them. Generic claims such as 'team player', 'good communication skills' and 'hard worker' provide little context on their own. Replace them with a specific action, scope and result.
How to format a clear, ATS-readable skills section
A simple skills section uses standard headings and selectable text, with related skills grouped by category. This makes the section easier for recruiters to scan and reduces parsing risk across different resume systems. No format can guarantee how every employer platform will interpret a document, so review the exported PDF before applying.
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 a job description
Read the job description carefully and use its terminology when it accurately matches your experience. Different employers and systems interpret wording differently, so include a common long form and abbreviation where that helps clarity, such as 'Business Intelligence (BI)'. The goal is a truthful, relevant resume that a recruiter can understand quickly, not keyword repetition.
- 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 when it reads naturally, such as "Business Intelligence (BI)" or "Search Engine Optimization (SEO)".
- Reorder your skills block so the most relevant, well-supported skills appear first.
- 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 common patterns make a skills section harder to trust or scan. Review them before applying and fix the ones that appear in your resume.
- 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.
Skills section checklist before you apply
Run this final check after tailoring the resume to the job description. It catches both keyword gaps and credibility problems before a recruiter sees them.
- Keep 10 to 15 current skills, grouped under clear labels such as Languages, Frameworks, Cloud, Tools, and Domain Knowledge.
- Put the most important skills from the job description first, using its exact phrasing when it is accurate for your experience.
- Make sure every listed skill is supported by a project, certification, work bullet, or portfolio item elsewhere on the resume.
- Remove filler claims such as team player, hard worker, passionate, and good communication skills.
- Use the heading Skills or Technical Skills so parsers and recruiters can find the section immediately.
- Avoid progress bars, star ratings, icons, and text embedded inside images.
- Name specific AI tools and workflows only when they are relevant and you can explain how you used them.
- Remove any skill you would not be comfortable defending in a five-minute interview conversation.
- Read only the skills section: it should make your target role obvious without the recruiter needing to guess.
Ready to build your resume?
Build, edit, preview, and download with a Pika watermark for free. Watermark-free downloads and paid upgrades show the exact price before checkout.
Build my resumeHow to Build a Relevant Resume Skills Section
A five-step process for selecting, ordering and phrasing skills for a specific application.
- Pull the keywords directly from the JD. Open the job description for the role you are targeting. Highlight every must-have skill and every nice-to-have. Make a list. The must-haves are usually in the first 5 qualification bullets.
- Score your honest match. For each job-description requirement, mark whether you genuinely have the skill, have limited exposure, or do not have it. Keep only the skills you can explain with credible evidence.
- Build the skills block with JD phrasing. Write your skills block using the exact phrasing from the JD. Group by category (Languages, Frameworks, Cloud, Tools, Soft skills). 12 to 15 skills total. Order with the JD must-haves first.
- Drop the dead weight. Cut MS Office, Email, Internet, generic soft-skill claims, and any tool you have not used in 18 months. Cut anything you cannot answer a 60-second question about.
- Mirror to Naukri + LinkedIn. Copy the same skills (in the same JD-matched phrasing) into your Naukri Key Skills field and your LinkedIn Skills section. Recruiters search both directly; consistency across all three surfaces compounds the match.
Frequently Asked Questions
How many skills should I list on my resume?
12 to 15 skills for most resumes, grouped into 4 to 5 categories (Languages, Frameworks, Tools, Cloud, Soft skills). Senior leadership resumes can drop to 10. Fresher and lateral resumes can stretch to 18 if every skill is genuinely current and relevant.
Should I include soft skills on my resume in India?
Yes, but sparingly and never as bare claims. List 3 to 5 soft skills that match the role, and prove every one of them through specific bullet points in your Experience section. "Team player" on its own is dead. "Led a cross-functional team of 5 engineers and designers" is alive.
What are the best computer skills to list on a resume?
It depends on the role. For a finance or analyst role, advanced Excel (named features - VBA, Power Query, pivot tables) is essential. For tech roles, list the specific tools the JD asks for - Git, the relevant IDE, the relevant cloud platform. Generic 'MS Office' is not worth a line in 2026.
How can I make my skills section easier for ATS software to parse?
Use standard headings, selectable text and clear categories. Match the job description's terminology only when it is accurate, and write common acronyms with their long form when useful, such as 'Search Engine Optimization (SEO)'. Avoid skill bars, rating dots and text embedded in graphics. This improves readability but cannot guarantee how every employer system will parse a file.
Should I list skills I learned through online courses (Coursera, Udemy, NPTEL)?
Yes, if you can defend them in an interview. List the skill (not the course) in the Skills section, and the course itself in the Certifications section. 'Python' belongs in Skills. 'Python for Everybody - Coursera, completed 2025' belongs in Certifications. Hiring managers respect specific course completions when they are tied to a real project or assignment.
What skills should I list as a fresher in India?
Lead with the technical stack relevant to the role. For software roles: programming languages, frameworks, databases, cloud, version control, basic system design. For data roles: SQL, Python, Excel, a BI tool, statistics. For non-tech roles: domain knowledge from your coursework, the relevant industry tools, soft skills demonstrated through college projects. 12 to 15 skills total, every one backed by a project or internship.
Do I need different skills sections for different jobs?
Usually. Tailor the section to the important requirements of each role, while keeping every skill accurate and supported elsewhere in the resume. Remove unrelated tools instead of adding every keyword from the job description.
Should I list outdated skills I no longer use?
No. If you have not used a skill in 18 months, drop it. Listing dead skills makes your resume look stale and uses space that better keywords could occupy. The exception is foundational skills (SQL, Git) that you still use periodically - keep those if they are relevant to the role.
Where should the skills section go on the resume?
For skill-led roles, keep it where a recruiter can find it quickly. Freshers often place it after Education or Projects. Experienced candidates often place it after the Professional Summary or Experience, depending on which section provides stronger evidence.
Should I add language skills (Hindi, English, Tamil, etc.)?
Yes if relevant to the role. Sales, customer-facing, and BFSI roles in non-metro markets actively look for regional language fluency. List each language with a proficiency level (Native, Fluent, Professional, Basic). Do not pad with languages you took for two semesters and never use.
Naukri Key Skills vs resume Skills section - same or different?
Same content, same phrasing. The Naukri Key Skills field is searchable by recruiters - they type a skill, your profile shows up if it appears in this field. Mirror your resume's skills section exactly into Naukri Key Skills, with the JD-matched phrasing. Inconsistency across the two surfaces leaks recruiter views.
How do I show I have a skill I learned but never used at work?
Build a small side project that uses the skill, host it publicly (GitHub, a live demo URL, a portfolio article), and reference the project in your resume. A self-driven project is the cleanest way to claim a skill you do not have professional experience in. Without a project, a self-taught skill is hard to defend in the interview.