A resume is a short evidence document. It does not need to tell the full story of your life; it needs to help a reader understand what you have done, how you work, and why the experience is relevant to this role.
The most reliable way to write one is to make the decisions in order. Start with the job, collect evidence, draft the sections, and only then spend time on layout.
If you are learning how to make a resume from scratch, this sequence keeps formatting decisions from getting ahead of the content.
1. Turn the job description into a short brief
Copy the job description into a working note and mark three things:
- Responsibilities the role will actually perform.
- Tools, methods, or domain terms that appear more than once.
- Outcomes the employer seems to care about, such as faster delivery, accurate reporting, customer retention, or reliable operations.
Do not copy every phrase into the resume. Use the list to decide which truthful evidence should appear near the top. If a role emphasizes stakeholder interviews and you have done them in a project, make that project easier to find. If you have never used the named tool, do not add it to your skills list. This is how to tailor a resume without copying the posting or changing the facts.
2. Build an evidence bank before writing polished bullets
For each job, project, internship, or meaningful volunteer role, jot down:
- The problem, deliverable, or recurring work.
- Your specific action and the people or systems involved.
- The result, scale, constraint, or decision that followed.
- Tools or methods used in context.
This is where you can look at old reports, project files, calendars, feedback, or grade records. You are not putting all of this into the final resume. You are creating a pool of accurate material so you do not have to invent a metric at the last minute.
Connected example: from job description to resume bullet
The following junior frontend developer scenario is illustrative. It shows the reasoning process, not a real candidate’s employment history.
Job description → The role asks for someone who can build responsive interfaces, work from design files, and collaborate through Git.
Candidate evidence → The candidate has not done this in a paid job, but did complete an academic product-catalog project. Their project files show that they translated Figma layouts into Vue components, tested the pages at mobile and desktop widths, and used pull requests with classmates.
Resume bullet point → Built responsive Vue components from Figma layouts for an academic product-catalog project, collaborating through Git pull requests and resolving layout issues across mobile and desktop views.
The bullet uses the language of the role only where the evidence supports it. Calling it an academic project prevents the reader from mistaking it for paid employment. If the candidate did not track a speed, percentage, or user count, they should not add one.
3. Choose the structure that matches your evidence
Reverse chronological order is a useful default because it puts recent work first and makes the timeline easy to follow:
- Name and contact details
- Summary, if it adds useful context
- Experience, projects, or internships
- Education
- Skills, certifications, and selected links
Change the emphasis when your situation calls for it. A fresher may place projects, education, or an internship above limited paid experience. A career changer may need a short summary and a “Selected experience” section that translates earlier work into the target role. An experienced professional should give the most space to recent, relevant scope and reduce older history to what still supports the application.
How long should a resume be?
Use the space needed to present relevant evidence clearly. There is no universal one-page or two-page rule; expectations vary by country, industry, role, and the amount of experience that genuinely supports the application.
- Students: one focused page is often enough when projects, coursework, activities, and work can be presented clearly. Do not pad it to reach a target length.
- Early-career professionals: one page may still be enough, but do not remove a strong internship, project, or relevant role merely to obey a slogan.
- Experienced professionals: one or two pages can work. Keep the detail that proves recent, relevant scope and compress work that no longer supports the target role.
- Senior professionals: two pages, and sometimes more in fields that expect extensive leadership, technical, research, clinical, or publication history, may be reasonable. Relevance and navigation still matter more than seniority alone.
Check the job posting and credible guidance for the market you are applying in. A concise document is useful; an arbitrarily short one is not.
4. Write contact information that works as text
Include your name, a professional email address, phone number if appropriate for your market, location or work authorization context when relevant, and useful links such as LinkedIn, GitHub, or a portfolio. Make sure the visible text and destination agree. A link that says github.com/your-name but points to a template account is not a small formatting issue.
Keep contact details as selectable text. Do not make the email address or phone number an image or an icon-only decoration. The ATS Resume Guide explains how to check the exported text sequence.
5. Write a summary only when it earns its space
A summary can help when you are changing direction, moving into a senior role, or connecting a mixed background to a specific job. It is less useful when it only says “hardworking professional” or repeats the job title.
Illustrative example
Customer support specialist with three years of experience improving help-center content and resolving complex account issues. Known for turning recurring questions into clearer documentation and handoff steps. Seeking a customer-success role supporting B2B software users.
The summary names an area, a pattern of contribution, and a direction. Replace each part with facts you can explain. A fresher might write a two-sentence version focused on a degree, project, internship, or relevant capability instead of pretending to have years of experience.
6. Turn each experience entry into evidence
Use a simple framework for writing resume bullet points: Action + Context + Result.
- Action: What did you do? Start with a specific verb such as built, analyzed, coordinated, documented, tested, or trained.
- Context: What project, responsibility, team, customer, or system was involved?
- Result: What outcome or contribution followed? This might be a finished deliverable, a clearer process, a decision, a resolved problem, or a measurable change.
Not every bullet needs a numerical achievement. A precise contribution is stronger than an invented percentage. Use a number only when you know what it measures and can explain where it came from.
| Draft | Stronger illustrative version |
|---|---|
| Worked on weekly reports | Built weekly performance reports in Excel for account managers, giving the team one place to review delayed renewals and owners. |
| Helped with a website redesign | Coordinated content review for a website refresh, correcting outdated product descriptions before launch. |
| Responsible for lab equipment | Maintained and calibrated shared lab equipment, keeping service records ready for student project setup. |
The stronger versions do not claim more than the draft supports. They show the work, the setting, and why the work mattered. Treat them as resume writing examples, not lines to copy without evidence. Harvard’s resume guide similarly recommends specific, active, fact-based language and formatting that translates properly to PDF.
7. Adjust the advice to your experience level
If you are a fresher or early-career candidate
You do not need to apologize for having a short work history. If you are working out how to write a resume with no experience, start with evidence outside full-time employment:
- Academic projects: name the course or capstone, your contribution, the tools used, and the deliverable.
- Internships: describe the work you actually completed and distinguish observation or training from independent responsibility.
- Personal projects: explain what you built, why you built it, and what works. Link to a portfolio or repository when it helps.
- Freelance work: use the label “Freelance” or “Independent” only when that accurately describes the arrangement; do not invent a company name to make it look like employment.
- Volunteer experience: name the organization and contribution, and label the role as volunteer work.
- Relevant coursework: include selected courses when they match the role, ideally with a concrete assignment, lab, or case study rather than a long module list.
- Open-source contributions: identify the project and your contribution, such as documentation, testing, issue triage, or an accepted code change. Do not imply that maintaining the whole project was your job.
Projects can sit in a dedicated Projects section instead of Experience. Labels such as “Academic project,” “Personal project,” and “Volunteer project” give the reader useful context without diminishing the work.
Instead of:
Coursework: Python, databases, web development.
Try:
Inventory dashboard — academic project Built a small dashboard that filtered a provided sample inventory dataset by location and reorder status; documented the data-cleaning decisions in a project README.
If the records are sample data, say so. A reader can value a well-explained project without mistaking it for production experience or paid work.
If you are an experienced candidate
Give recent work enough space to show scope and judgment. You can group older positions under “Earlier experience” when the exact bullets no longer help the target role. Show progression when it is relevant: expanding team size, larger budgets, additional regions, more complex systems, or decisions that moved from individual execution to leadership.
Avoid filling the page with every tool you have touched. A selective list paired with current evidence is more credible than a catalogue of software names.
8. Finish the supporting sections
Use Education for degrees, institutions, dates when useful, and relevant distinctions. Add Projects when they demonstrate work that experience entries do not. Use Skills for a concise, truthful inventory. Add certifications only when they are current or relevant to the application.
For a portfolio-based role, links deserve attention: name the project, describe your contribution, and make the URL readable. For a regulated or location-specific role, follow the conventions and requirements of the market you are applying in rather than copying an example from another country.
US resumes and UK or European CVs
In the US, “resume” commonly describes the concise document used for most private-sector applications, while “CV” often refers to a longer academic, research, or medical record. In the UK, the National Careers Service describes a CV as the document used to summarize skills, achievements, and experience for job applications, even when it serves a similar purpose to a US resume.
Across Europe, the label “CV” is common, and Europass provides a cross-border CV format, but Europe is not one uniform hiring market. Expectations about language, length, photos, personal details, and document format can vary by country, industry, and employer. Follow the vacancy instructions and current local guidance rather than assuming that one European convention applies everywhere. Share sensitive personal details only when they are genuinely expected and you are comfortable doing so.
9. Apply restrained formatting
Use familiar headings, consistent dates, readable type, and enough space to separate entries. A resume does not need to look identical to every other resume, but important information should not depend on a graphic, an image, or a complicated reading order.
CareerContainer’s free resume builder lets you compare single-column and two-column template options, select Letter or A4, and download the finished document as PDF or DOCX. Those settings change presentation; they do not write or verify your claims. Choose the layout that suits the application, then inspect the exported file.
10. Run the final review in two passes
First review the content: Is every date correct? Can you explain every result? Does the top half show the evidence most relevant to this role? Are any sample names, placeholder links, or unsupported achievements left behind?
Then review the file: Can you select the text? Are headings and bullets in a sensible order? Are links visible and working? Does the PDF or DOCX have unexpected page breaks or clipped content?
The Common Resume Mistakes guide turns this review into before-and-after checks, while Resume Examples shows how the same principles change across experience levels.
A compact illustrative resume outline
The following is a structure demonstration, not a ready-made resume. Replace every name, number, employer, and claim with your own information.
Your Name
City, Country · email@example.com · phone · linkedin.com/in/your-name
Summary
Junior frontend developer with academic project experience building responsive interfaces and collaborating through Git. Interested in accessible, maintainable web applications.
Projects
Product catalog · Academic capstone
- Built responsive Vue components from Figma layouts and resolved layout issues across mobile and desktop views.
- Collaborated with classmates through Git pull requests and documented component setup in the project README.
Education
Relevant degree · Example University
Skills
Vue, JavaScript, HTML, CSS, Git, responsive design
The point is the relationship between sections: a target, a short explanation, evidence, and a compact supporting inventory. It is not a promise that this exact order or length is right for every role.
Frequently asked questions
How do I write a resume with no experience?
Lead with relevant evidence from academic, personal, volunteer, freelance, internship, coursework, or open-source work. Label each activity honestly, describe your contribution, and connect it to the target role without presenting a project as paid employment.
How long should a resume be?
Use the shortest length that gives your relevant evidence enough context. One page is often sufficient early in a career; experienced or senior candidates may need two or more. Country, industry, role, and relevant history all affect the answer.
Should I include a resume summary?
Include one when it adds context quickly, such as for a career change, mixed background, specialized focus, or senior scope. Skip it when it only repeats the title or uses generic qualities.
What is the best resume format?
Reverse chronological is a dependable default because it makes recent experience and dates easy to follow. Adjust section order for projects, education, or selected experience when that presents the strongest relevant evidence more clearly.
Should I customize my resume for every job?
Yes, but customize the emphasis rather than changing the facts. Use the job description to choose relevant evidence, order sections, and mirror accurate terminology; never add a skill or result you cannot support.