How to Write a Resume in 2026 (Step-by-Step)

There are three main formats. For 95% of job seekers, the right answer is chronological: Chronological (recommended for most): • Work history listed most-recent-first • Standard format; ATS parses it reliably • Best for candidates with steady career progression Functional (skill-based): • Groups skills rather than listing jobs • Hides employment gaps — but ATS often rejects it • Almost never recommended in 2026 Combination (hybrid): • Skills summary at top + chronological work history • Good for career changers or executives • Still ATS-parseable if structured correctly Key rule: Use a single-column, clean layout. Avoid tables, text boxes, and graphics. They break ATS parsing and can cause your resume to read as blank to automated screeners.

At the top of the page, include exactly these fields: • Full name (large, bold, 16-18pt) • City and Country (not your full street address) • Professional email address (firstname.lastname@gmail.com) • Phone number with country code • LinkedIn URL (customise to linkedin.com/in/yourname) • Portfolio or GitHub link (if relevant to your field) Do NOT include: • A photo (invites discrimination; breaks ATS in most systems) • Date of birth or age • Marital status • "Curriculum Vitae" or "Resume" as a heading (redundant) ATS note: Keep your name and contact details in the body of the document — not in a header/footer. ATS systems frequently skip header and footer regions entirely when parsing.

The summary is the first thing a recruiter reads. It needs to answer one question: "Why should I keep reading?" Use this formula: [Job title] with [X years] of experience in [specialty/industry]. [Biggest achievement, quantified]. Expertise in [Skill 1], [Skill 2], and [Skill 3]. Good example (Software Engineer): "Full-stack engineer with 6 years building SaaS products at Series A through Series C startups. Architected microservices platform handling 50M+ monthly events; reduced infrastructure costs by 40%. Expert in React, Node.js, Kubernetes, and AWS." Bad example: "Hardworking and motivated developer looking for a challenging role to grow my career and apply my skills." → Says nothing specific. Every applicant writes this. ATS tip: Mirror the exact job title from the posting in your first line. If the JD says "Senior Product Designer," use that phrase — not "Lead UX Designer" or "Senior Designer."

Format each role as: Job Title | Company Name | City | Start Month Year – End Month Year Under each role, write 4-6 bullet points using this structure: Verb + What you did + How / with what + Result with metric Weak: "Responsible for managing the sales team" Strong: "Managed 8-person enterprise sales team, implementing MEDDIC qualification framework; grew team quota attainment from 74% to 108% in 12 months" Quantify everything you can: • Revenue generated or cost saved ($) • Percentage improvements (%) • Size or scale (team size, user count, transaction volume) • Time saved or speed improved • Rankings or comparisons (top 10%, #1 in region) ATS keyword tip: Weave in keywords from the job description naturally within your bullets. If the JD requires "stakeholder management," that phrase should appear in your experience — not just the skills section.

List your hard skills in a dedicated section near the top or after your summary. ATS systems parse this section for keyword matching. Good skills section structure: Technical: Python, SQL, Tableau, Excel, R, AWS, Kubernetes Methodologies: Agile, Scrum, Kanban, Six Sigma, LEAN tools: Jira, Confluence, Salesforce, HubSpot, Figma Languages: English (native), Spanish (professional) Rules for your skills section: • List specific tools and technologies by name — not "Microsoft Office Suite" • Include version or depth where relevant: "Python (pandas, scikit-learn, Flask)" • Do not include generic soft skills here (leadership, communication) — demonstrate those in bullets • Match the skill vocabulary from the JD exactly — "project management" ≠ "programme management" in ATS

Format: Degree Title | Field of Study | University Name | Graduation Year For most professionals with 3+ years of experience, education goes AFTER work experience. For students and fresh graduates, education goes BEFORE work experience. Include: • Degree and major • University name and location • Graduation year (not start year) • GPA only if it's 3.5+ and you graduated within the last 3 years • Relevant coursework (for students only) • Thesis title (for STEM / research roles) Certifications belong here OR in their own dedicated section: • AWS Certified Solutions Architect • PMP • CPA / CFA / ACCA • Google Analytics Certified Always list the full certification name — ATS searches for exact certification names.

Length: • 0-5 years experience: 1 page • 5-10 years: 1-2 pages • 10+ years or senior/executive: 2 pages max (3 only for academic CVs) File format: • .DOCX is the safest format for most ATS • PDF is fine for most modern ATS, but avoid PDFs created from design tools like Canva or Adobe XD (text is embedded as images and cannot be parsed) • Never submit as .pages, .odt, or image files Final checklist before submitting: ☑ Tailored to the specific job description ☑ Exact job title used in the summary ☑ Every job has at least one quantified achievement ☑ Skills section uses terminology from the JD ☑ No photos, tables, or graphics ☑ Consistent formatting (same font, same bullet style) ☑ No spelling or grammar errors ☑ Contact details are accurate and professional ☑ LinkedIn URL is included and up to date Test it: Paste your resume into our free ATS checker below to get an instant score and see exactly which keywords you're missing for your target role.