You're staring at a blank document and you don't know where to start. That's normal. Most people open a template first, pick a font, and then realize they can't remember half their dates. When you build a resume from scratch the right way, you collect facts before you touch layout—and you don't waste an hour fighting a two-column design that Workday will scramble anyway.
I've screened stacks of these, and the file that wins is boring and specific. This guide walks you through eight steps: inventory, target role, structure, experience, skills, summary, ATS testing, and export. Before you format anything, check your resume for free once you have a draft—you'll catch parsing problems early instead of after fifty silent applications.
You won't need a design degree. You will need a spreadsheet or notes app, one target role family, and the patience to verify dates before you submit. That's the whole game: facts first, format second, test before you send. Most people skip step one and wonder why the bullets feel thin.
Quick Wins
- Open a blank doc and list every employer, title, and month-year date you can verify.
- Highlight three required skills from one target posting and find matching proof in your notes.
- Paste your draft into a plain text editor and confirm jobs and dates stay together.
What does it mean to build a resume from scratch?
Building from scratch means you start with verified facts, not a Canva template. A resume is a one- or two-page evidence file: who you are, what you've done, and what you can prove with dates, tools, and outcomes. Applicant tracking systems in Workday, Greenhouse, Lever, and iCIMS don't grade creativity—they extract text into fields recruiters search later.
A resume from scratch is not a biography. It's a filtered argument for one role, written so both a parser and a tired recruiter can find the proof fast.
This is not the same as dumping every job you've ever had onto a page. You're selecting evidence for a target. It's also not the same as copying a posting into white text—recruiters have seen that trick, and it breaks trust fast.
If you're comparing your finished file against automated screening, read what a good ATS score means so you don't treat a diagnostic number like a hiring verdict.
How to build a resume from scratch: step by step
Step 1: Build a complete fact inventory
Open a plain document or spreadsheet—not your resume. List every employer, job title, city and state, and month-year date range. Add education, licenses, certifications, projects, volunteering, and tools. Then write unpolished notes: customers served, systems used, problems solved, people trained, budgets handled, deadlines met.
Verify details while records exist. Compare dates with offer letters, tax records, or old calendars. Don't guess a degree title. If your official title was vague, keep it and add a clarifying functional title in parentheses only when accurate—"Associate II (Customer Support)" is fine when the work matched.
Numbers are useful only when they're real. Record defensible counts, ranges, dollars, and time saved. If no number exists, capture scope: enterprise clients, regulated records, or a high-volume queue. A credible qualitative outcome beats a fabricated percentage.
Step 2: Define the target role and read the posting
A resume built for "any job" communicates no clear fit. Choose a role family, seniority level, and industry context. Gather three representative postings and highlight repeated titles, responsibilities, tools, and credentials. Separate must-haves from preferences.
Create a two-column relevance note: employer need on the left, your honest proof on the right. If the posting asks for Salesforce, place your Salesforce administration beside it. If it asks for a credential you don't hold, don't disguise the gap—decide whether the role is still realistic.
Edge case — career change: map transferable actions, not industry nouns. A teacher planning curricula can describe program design, stakeholder communication, and progress measurement. Don't claim product management unless you actually did it.
Step 3: Create the document structure on a blank page
Set US Letter, single column, margins between 0.5 and 1 inch. Use Arial, Calibri, or Georgia at 10.5–12 point. Put contact information in the body—not a header. City and state, phone, professional email, LinkedIn, portfolio when relevant. Skip the full street address.
Add standard labels: Summary, Skills, Professional Experience, Education, Certifications or Projects when useful. Experienced candidates place Experience above Education. Students can lead with Education and Projects. Avoid a fully functional format that strips dates from skills—recruiters need chronology.
Don't shop for visual flourishes before the writing exists. Text boxes, sidebars, and icon ratings create parsing risk. If you want a ready structure, use HireFlow's free resume builder instead of redesigning every line.
Step 4: Draft work experience from recent to older roles
For each role, enter employer, location, title, and month-year dates in a consistent pattern. Add three to six bullets for recent relevant work; one to three for older roles. A job from fifteen years ago doesn't deserve equal space just because it lasted longer.
Draft each bullet with action, object, method, and outcome. Weak: "Created reports." Strong: "Built weekly Salesforce pipeline reports for regional sales leaders, flagging stalled opportunities and standardizing forecast review." Avoid "responsible for," "helped with," and "worked on" when you can state your exact contribution.
| Before (duty) | After (evidence) |
|---|---|
| Helped customers | Resolved billing and access requests across phone and email queues; documented recurring issues for the support lead |
| Worked on reports | Built a weekly Excel inventory report combining warehouse and sales data for replenishment review |
| Managed projects | Coordinated launch tasks, owners, dependencies, and status updates for three regional openings |
Use posting vocabulary where it matches your work. If the employer says "customer onboarding" and you wrote "new client setup," the recognized phrase improves clarity. Don't paste an entire requirements list. See resume bullets that show outcomes for more patterns.
Step 5: Add Skills, Education, projects, and credentials
Build Skills from the overlap between your inventory and target postings. Group related terms in plain text: Data, Platforms, Operations. Prefer "Excel: PivotTables, XLOOKUP, Power Query" over "Excel: advanced." No progress bars or star ratings.
For Education, include degree, field, institution, and location. State credentials exactly as issued, with expiration or in-progress status. Never write a certification acronym after your name before it's awarded.
Edge case — no paid experience: use Projects with name, context, tools, date, and two or three bullets. Label academic, personal, volunteer, or client work accurately. A GitHub link should open and avoid confidential data.
Composite example — mid-level analyst: Skills might read "SQL, Excel (PivotTables, Power Query), Tableau, stakeholder reporting." Education stays compact: "B.S. Economics, State University, 2019." A certification in progress gets an expected date only when the plan is real—not "CPA (anticipated)" if you haven't enrolled.
Step 6: Write the summary last and tailor the top third
Now write two to four lines. Start with target identity, relevant scope, and strongest specialization. Add two or three job-related skills and one credible outcome. Remove unsupported adjectives: dynamic, visionary, results-driven.
Don't use an objective explaining what you want from the employer. A career changer can connect prior and target work: "Teacher moving into customer enablement after six years designing software training, facilitating live workshops, and measuring learner completion."
Tailor the top third per application. Change summary, reorder Skills, place the most relevant bullets first. Keep factual history unchanged. Compare language with keywords ATS systems look for , but include only terms demonstrated elsewhere.
Step 7: Prepare the file for Workday and Greenhouse
Workday may parse into structured profile fields. Greenhouse extracts searchable text and keeps the attachment. Use standard headings, dates beside roles, contact in body text. Don't assume a polished preview means every field imported correctly.
Run a plain-text test: select all, copy, paste into a simple editor. Check whether name appears first, sections stay in order, dates stay near employers. Follow portal instructions for DOCX or text-based PDF. For Workday quirks, see the Workday resume format guide .
Edge case — overlapping dates: if you held two part-time roles, list both with accurate ranges. Don't merge them into one block or stretch dates to hide overlap.
Edge case — NDA client names: when you can't name a client, describe the sector and scale: "Fortune 500 healthcare client" or "regional logistics operator (under NDA)." Never invent a recognizable brand. Interviewers will ask which company—and vague inflation breaks trust faster than a generic label.
Step 8: Proofread, export, name, and archive
Proofread in passes: facts first (names, dates, degrees, links), then content (vague claims, repeated verbs), then mechanics (spelling, tense). Present tense for current work; past tense for completed roles. Read aloud or bottom to top to disrupt familiarity.
Export per instructions. PDF must contain selectable text. Filename: Firstname-Lastname-Resume-Role.pdf—not Resume_final_v3_USE_THIS.pdf. Save three layers: fact inventory, master resume, tailored submission copy. Record employer, role, date, and filename in your tracker.
Common mistakes when building a resume from scratch
Starting with a fancy template. Two-column layouts and invisible tables scramble parsing before a human sees your file. Build content first, then keep the layout boring.
Writing the summary before the evidence. You end up claiming skills the experience section doesn't support. Draft bullets first; summarize second.
Guessing dates or titles. Background checks compare against payroll and credential records. Verify now or fix later under pressure.
Keyword stuffing. Repeating "stakeholder" fourteen times doesn't fool Greenhouse and makes you sound like a bot. Use posting language once per real example.
Skipping the upload review. Workday's auto-fill can import dates into the wrong field. Check every populated field before you click submit.
One resume for every industry. Keep one master, but tailor the top third and strongest bullets per role family. A generic file competes against tailored ones.
Using a functional resume to hide gaps. Recruiters read missing chronology as missing evidence. A short honest gap line plus strong recent bullets beats a thematic skills page with no dates.
Sounds simple, right? Most first drafts still blow it on bullet one—"assisted team" instead of what you actually changed. Fix that before you pick a border color.
Use HireFlow while you build from scratch
After Step 4, upload your draft to the free ATS resume checker . Look at what text extracts, which sections parse cleanly, and whether contact details survive. Fix structure before you polish wording.
When you're tailoring to a specific posting, run the job match score to see which requirements are documented versus missing. Use the gap list as an editing guide—not a reason to invent experience.
Pair the resume with a targeted letter from the cover letter generator when the application allows one. The letter explains context the resume can't carry in bullet form—career gaps, relocation, or why you're moving from one function to another.
Build the skeleton in the free resume builder if you want single-column structure without fighting Word tables. Export, then run the checker on the same file you'll upload—not an older version sitting in Downloads.
Frequently asked questions
Start with a fact inventory outside the resume: employers, titles, locations, dates, duties, projects, tools, education, credentials, and defensible results. Collecting facts first prevents layout decisions from controlling what you remember or omit.
Yes. Use education, coursework, projects, volunteering, campus leadership, caregiving, freelance work, and community involvement when they demonstrate relevant skills. Describe real actions and outcomes without presenting unpaid work as paid employment.
Write it last. Your strongest role, skills, and evidence become clearer after Experience, Skills, and Education are drafted. A final summary can then target the posting without introducing claims the rest of the resume does not support.
Use roughly three to six focused bullets for recent relevant roles and fewer for older or less relevant jobs. Quality matters more than symmetry. Each bullet should add distinct evidence rather than repeat the job description.
Keep one accurate master resume, then make a tailored copy for each role family or posting. Change emphasis, ordering, summary language, skills, and selected bullets while keeping employers, dates, credentials, and underlying facts consistent.