How to Write a Resume

TL;DR

Why Your Resume Format Matters

A resume is not just a list of jobs — it is a structured document that must satisfy two audiences simultaneously: ATS software that scans for relevance, and a recruiter who spends 6–10 seconds on the first pass. A resume that confuses either one gets discarded. The format, structure, and language you choose directly impact how far your application goes.

Stat worth knowing

The Anatomy of a Strong Resume

Every effective resume contains the same core sections. The order and weight you give each section should reflect the role you are applying for and your level of experience.

1. 1

   Contact Header

   Full name, professional email, LinkedIn URL, GitHub (for engineering roles), city and country. No photo, no date of birth.

2. 2

   Professional Summary

   2–3 sentences. Who you are, what you specialize in, and what value you bring. Tailor this to every job.

3. 3

   Work Experience

   Reverse chronological order. Company, title, dates, and bullet points focused on impact — not just responsibilities.

4. 4

   Skills

   A concise list of technical skills, languages, frameworks, and tools. Mirror the job description terminology.

5. 5

   Education

   Degree, institution, graduation year. For experienced professionals, keep this brief.

6. 6

   Optional Sections

   Certifications, open source contributions, side projects, publications — relevant to role only.

How to Write Work Experience Bullets

The experience section is where most resumes fail. The difference between a weak and strong resume is almost always in how accomplishments are framed. Avoid listing job duties — instead, describe what you built, fixed, or improved, and back it with measurable outcomes.

Before vs After (IT Example)

Formula for strong bullet points

• Action verb + what you did + technology used + measurable outcome
• Use "Migrated" not "Was involved in migration"
• Use "Reduced build time by 40%" not "Improved CI/CD pipeline"
• Use "Led a team of 4" not "Worked with the team"
• Use "Handled 50k requests/day" not "Built high-traffic service"

The Professional Summary Section

The summary sits at the top of your resume and is often the only section that gets read in full. It should immediately answer: who you are, what you specialize in, and why you are a strong candidate for this role. Avoid vague phrases like "results-driven professional" — they signal nothing. Be specific about your stack, domain, and impact.

Before vs After (Summary Example)

Formatting Rules That Actually Matter

ATS parsers are sensitive to formatting. Decorative resumes with columns, icons, and tables look polished in design tools but frequently break when parsed. Stick to a clean, single-column layout that both ATS and humans can read without friction.

Formatting Dos and Donts

Keywords and ATS Optimization

ATS software matches your resume against the job description using keyword analysis. If your resume does not contain the exact terms the job description uses, your score drops — even if you have the relevant experience. This is why tailoring your resume for every application is not optional.

How to extract and use keywords

• Copy the job description and identify repeated technical terms
• Note the exact phrasing — use "React" not "ReactJS" if that is what they use
• Mirror titles: if the role says "Software Engineer" use that, not "Developer"
• Include tools, platforms, and methodologies mentioned in requirements
• Weave keywords naturally into bullets — not as a keyword dump

Pro Tip

How Long Should a Resume Be?

For most candidates with under 10 years of experience: one page. For senior engineers, tech leads, or candidates with extensive relevant projects: two pages is acceptable. Three or more pages is almost always too long unless you are in academia or a specialized research role. Recruiters do not read long resumes — they scan them.

What to cut when trimming your resume

• Roles older than 10–12 years (unless directly relevant)
• Generic skills everyone has (e.g., "Microsoft Office", "email")
• Objectives section — replace with a targeted summary
• References available upon request — assumed and wastes space
• Irrelevant hobbies or personal details

Common Resume Mistakes

The most common resume problems are not about missing skills — they are about how the resume is written. These mistakes cause qualified candidates to get filtered out before a human ever reviews their application.

• Sending the same resume to every job without tailoring
• Listing responsibilities instead of accomplishments
• No measurable outcomes — every bullet is vague
• Using a designed template with columns, icons, and graphics
• Missing keywords from the job description
• Inconsistent date formats or unexplained gaps
• Email address that looks unprofessional

Pre-submission checklist

• Tailored professional summary for this specific role
• Keywords from the job description appear in experience and skills
• Every bullet point starts with a strong action verb
• At least 50% of bullets include a measurable result
• Single-column layout, clean PDF export
• No typos or inconsistent formatting
• Contact info is complete and professional
• File named: FirstName-LastName-Resume.pdf

How Evalo Helps

Evalo analyzes your resume against any job description and automatically identifies gaps, missing keywords, and weak bullet points. It rewrites your resume sections to align with the specific role — so you do not have to manually tailor every application from scratch.

• Automatic keyword extraction from job descriptions
• AI-powered resume rewriting for ATS alignment
• Bullet point improvement with measurable framing
• Tech stack gap analysis for IT roles
• Summary rewrite tailored to each position

Ready to write a resume that gets interviews?