The components of a resume are the sections that organise your identity, target role, skills and evidence into a document a recruiter can understand quickly. The strongest resume does not include every possible section. It includes the right sections, in the right order, for one target role.
Build the sections around one target role
Choose the sections that prove your fit, then check whether the finished resume is easy to scan and aligned with the vacancy.
On this page
The 10 essential components of a resume
Contact information
Name, phone, professional email, city and useful profile links.
Job title / headline
A concise target role or role family that tells the recruiter what you are applying for.
Summary / objective
A short role-specific opening that explains your direction and strongest evidence.
Skills
Relevant tools, methods, systems, languages or domain capabilities you can defend.
Experience
Roles, employers, dates and evidence-based bullets showing relevant work.
Projects
Academic, personal, internship, freelance or professional work that proves capability.
Education
Degree, institution, graduation year and relevant academic detail.
Certifications
Relevant completed credentials, training or licence information with accurate status.
Achievements
Selected awards, performance recognition or verified outcomes that add evidence.
Additional sections
Languages, publications, volunteering, leadership, portfolio or other role-relevant evidence.
1. Contact information
The contact block is the identity layer of the resume. It should make it easy to recognise you, contact you and open any relevant professional links.
- Full name
- Mobile number
- Professional email address
- City and state or city and country
- LinkedIn when useful
- GitHub or portfolio for roles that benefit from work samples
- Full residential address unless specifically needed
- Multiple phone numbers
- Unprofessional email IDs
- Broken portfolio or GitHub links
- Personal information that the employer did not request
2. Target job title or resume headline
The headline tells the reader what role you are positioning yourself for. It is different from changing your official employment history. The target headline can name the job family; experience entries should retain truthful role titles.
Junior Data Analyst | SQL | Excel | Power BI
Java Backend Developer | Spring Boot | REST APIs | SQL
Business Analyst | Operations Experience | Excel | Process Analysis
For detailed rules, use Job Title in Resume.
3. Professional summary or resume objective
You usually need one concise opening section, not both. A summary works best when you have relevant professional experience. An objective is useful for freshers, interns and some career switchers when it explains target role + capabilities + evidence.
Computer Science graduate with project experience in Java, Spring Boot, REST APIs and SQL, seeking an entry-level software engineering role focused on application development and debugging.
HR Operations professional with 4 years of experience supporting onboarding, employee records, HRIS updates, reporting and cross-functional coordination across multi-location teams.
See Resume Objective for Freshers for more examples.
4. Skills section
The skills section should function as a compact evidence index. It helps a recruiter see the tools, systems, methods and domain capabilities that matter for the target role. It should not become a list of everything you have ever studied.
| Role | Useful skill examples | Best supporting evidence |
|---|---|---|
| Software Engineer | Java, Spring Boot, REST APIs, SQL, Git, testing | Projects, internships, production features |
| Data Analyst | Excel, SQL, Power BI, data cleaning, reporting | Dashboards, analysis projects, work examples |
| HR | Recruitment, onboarding, HRIS, Excel, employee records | Internship or professional HR responsibilities |
| Sales | CRM, lead qualification, pipeline management, client communication | Accounts, calls, sales workflow, verified outcomes |
| Operations | SLA tracking, documentation, reporting, coordination, process control | Workflows, escalations, reports, service evidence |
Use Computer Skills for Resume and Communication Skills for Resume for deeper examples.
5. Work experience
For experienced professionals, this is often the most important section. Each role should make employer, title and dates easy to verify, then use concise bullets to show what you did and why it mattered.
For managers and team leads, see Team Handling Skills for Resume.
6. Projects
Projects are especially valuable for students, freshers, career switchers and technical candidates. A project section should show the problem, your contribution, tools used and how you verified the result.
What was built or analysed?
Give enough context for the reader to understand the project.
What did you personally do?
Name the module, analysis, feature, API, dataset, test or workflow you handled.
How do you know it worked?
Use testing, deployment, demo, reconciliation, trainer review or another genuine check.
For deeper guidance, read Project Description for Resume and Software Project Description Examples.
7. Education
Education is usually higher on a fresher resume and lower on an experienced resume. Keep the information factual and easy to scan.
Add relevant coursework only when it strengthens the target role and you have limited professional evidence. Avoid expanding the education section with unrelated school-level detail once stronger evidence exists.
8. Certifications and training
Certifications should add role-relevant credibility, not replace experience or projects. State the exact credential name, issuer and status accurately.
Good use
A completed cloud, finance, HR, analytics or coding credential that supports the target role and can be verified.
Risky use
Writing “certified” when you only watched a course, started training or are preparing for an exam.
9. Achievements
Achievements are useful when they add evidence beyond normal responsibilities. They can sit in a separate section or be integrated into experience, projects or education.
Useful examples
- Verified academic award
- Recognition for project or work quality
- Competition placement
- Selected performance award
- Published paper or accepted presentation
Avoid
- Generic “hardworking” claims
- Unverifiable rankings
- Invented performance percentages
- School achievements unrelated to the target role
- Participation certificates presented as major awards
10. Optional additional sections
Additional sections are useful only when they improve role fit or verification. They should not be included just because a template has space.
Languages
Useful for customer-facing, multilingual or region-specific roles when language ability matters.
Publications / research
Useful for research, academic, healthcare, technical or postgraduate applications.
Volunteering / leadership
Useful when it proves coordination, responsibility, domain exposure or transferable skills.
Portfolio / GitHub
Useful when the role benefits from work samples, code, design, writing or project evidence.
Professional memberships
Useful when genuinely relevant to the profession and current.
Interests
Usually optional. Keep them only when meaningful and space allows.
Which resume components are required and which are optional?
| Component | Freshers | Experienced | Decision rule |
|---|---|---|---|
| Contact information | Required | Required | Every resume needs a clear identity/contact block. |
| Target title / headline | Recommended | Recommended | Useful for role clarity when the application is targeted. |
| Objective / summary | Often useful | Often useful | Use one when it adds role clarity; skip generic filler. |
| Skills | Usually required | Usually required | Keep role-specific and defensible. |
| Experience | If applicable | Required | Include internships or real work accurately. |
| Projects | Usually valuable | Optional / selected | Use when projects add evidence not already clear from work. |
| Education | Required | Required but often lower | Keep dates and credential names accurate. |
| Certifications | Optional | Optional | Include relevant, completed or accurately labelled credentials. |
| Achievements | Optional | Optional | Use only when verified and useful. |
| Additional sections | Optional | Optional | Add only when role-relevant. |
Best order of resume sections
- Contact
- Target title / objective
- Skills
- Projects
- Internship
- Education
- Certifications
- Achievements
- Contact
- Target headline
- Professional summary
- Skills
- Experience
- Selected projects / achievements
- Education
- Certifications
- Contact
- Target role
- Transition summary
- Transferable + target skills
- Relevant projects / recent training
- Experience
- Education
- Certifications
The order should follow the strongest evidence, not a rigid template. For more structural choices, see Types of Resume.
How fresher resume components should differ
Freshers have less formal work history, so the resume should make education, projects, internships and practical evidence easier to find. A thin work-experience section should not occupy the centre of the page just because an experienced template does.
Use Resume Format for Freshers in India for a complete fresher structure.
How experienced resume components should differ
Experienced candidates should usually prioritise current role fit, recent achievements, scope and measurable responsibility. Earlier roles can be compressed so the resume gives more space to recent and relevant evidence.
If the evidence genuinely requires more space, use Two-Page Resume Format.
How resume components affect ATS readability
ATS systems vary, so no single section order guarantees screening success. The safer goal is a resume with recognisable headings, logical reading order, selectable text and role-relevant evidence that matches the vacancy truthfully.
Use clear headings
Examples: Skills, Experience, Projects, Education, Certifications.
Keep essential facts in text
Do not put important contact, skills or dates only inside images or decorative elements.
Match terminology accurately
Use job-description terms when they genuinely describe your skills or experience.
For a broader ATS workflow, use ATS-Friendly Resume Format and How to Improve ATS Score.
12 common mistakes with resume components
- Including every possible section instead of only useful ones.
- Using a generic headline that does not show the target role.
- Writing both a long objective and a long summary.
- Listing skills that never appear in projects or experience.
- Using duties instead of evidence-based experience bullets.
- Putting weak academic projects above strong professional experience.
- Keeping education too large after years of relevant experience.
- Claiming certifications or skill levels inaccurately.
- Creating an achievements section with unverifiable claims.
- Using creative section names that hide the meaning.
- Repeating the same information in multiple sections.
- Copying one section order for every job application.
Also review Resume Mistakes to Fix.
Audit your resume components in 60 seconds
Identify the target
Can a recruiter tell the intended role from the top third of the resume?
Check each section
Does every section add evidence, context or verification that matters for the role?
Check the order
Is your strongest relevant evidence visible before weaker or less relevant content?
Remove filler
Delete duplicated skills, vague objectives, weak achievements and irrelevant sections.
Use the sections to build one coherent application
After the structure is complete, compare the resume against the exact job description and fix only real gaps.