How To Write Up A Resume

Writing a resume that doesn't get auto-rejected is mostly about understanding how the screening tools actually work before you worry about fancy formatting.

I've spent years looking at applicant tracking system outputs and reading recruitment manager responses, and the thing that consistently surprises people is how little actual human attention gets paid to a resume before it's either filtered out or tossed into a pile. The software scans for keywords, date ranges, and job titles. If your resume fails any of those basic checks, nobody ever sees it. After that, the human reader typically spends about six to eight seconds on an initial pass. That's it. You're not writing a narrative. You're writing a structured document designed to survive two different kinds of scrutiny. Start with the content structure before you touch any template. Most people open Word or Google Docs and immediately start wrestling with columns and fonts. That's backward. Build the document as plain text first, then apply formatting. I once spent an afternoon reformatting a resume with a clean two-column layout only to realize the ATS couldn't parse the right column at all. It dropped about forty percent of my bullet points. Switched to a single-column layout with clear section breaks, and everything went through correctly. Don't skip the plain-text phase. Test your resume by copying and pasting it into a blank text document. If the information survives the paste intact, your formatting isn't going to break an ATS.

How To Write Up A Resume for Specific Roles Without Losing the Plot

The biggest mistake I see is people writing one resume and submitting it everywhere. That approach works for entry-level roles where any job count looks fine, but it falls apart quickly. Recruiters can tell when a resume has clearly been mass-generated. The skills section will be generic, and the job descriptions won't align with the role you're applying for. I tailored my resume for a mid-level operations role once and had to address a gap in my background where I'd managed projects informally but never held a title with "manager" in it. Instead of inflating my title, which would have been easily verifiable and would have caused problems later, I restructured the relevant bullets to emphasize scope and decision-making authority. Things like "coordinated cross-functional teams of up to twelve people" and "owned budget allocation for quarterly initiatives." Same facts, different framing. It worked. The interviewer acknowledged the title discrepancy immediately and moved on, which told me she was actually reading the document. Section order matters more than most people realize. For experienced professionals, put work experience above education. Education goes first only if you're a recent graduate with limited relevant experience, or if your degree from a recognizable institution is a significant signal for the role. Even then, work experience should still come first unless your work history is genuinely irrelevant. A marketing role applying for a research position with a PhD from a top program is one of those rare cases where putting education first makes sense. Don't follow that logic just because you went to a good school and the job doesn't require it. Use consistent date formatting throughout. Something like "Mar 2019 – Dec 2022" is fine. Mixing "March 2019 to December 2022" with "03/2019-12/2022" on the same document looks careless. ATS date parsers also prefer the consistent format, and inconsistent dates can cause timeline gaps to appear that don't actually exist. I've seen resumes get flagged for unexplained employment gaps because the formatting made a three-week transition between contracts look like a six-month break.

The Bullets Are Where Most Resumes Fail

Job descriptions that just list responsibilities are useless. "Responsible for managing social media accounts" tells a recruiter nothing about what you actually did or how well you did it. Every bullet should follow a simple pattern: what you did, how you did it, and what the result was. Even an approximate result is better than nothing. "Increased organic web traffic by approximately 30% over six months through targeted content optimization and SEO restructuring" is infinitely more useful than "Managed content strategy and improved web presence." You don't need exact figures for everything. If you don't have hard numbers, describe scope. "Managed a portfolio of twenty recurring client accounts" conveys real information. Keep each bullet to one line when possible. Two lines maximum. Recruiters scan horizontally and vertically, and long paragraphs kill both directions. If a bullet is running three lines, it's doing too much work. Split it into two separate bullets or cut the less important part. The skills section needs to be honest and specific. Listing "Microsoft Office" is so generic it's basically noise. If you actually use Excel for data analysis, write "Excel (pivot tables, VLOOKUP, conditional formatting)." If you know Python but only used it for basic scripting, don't list machine learning frameworks. Recruiters and hiring managers will ask about whatever you put in that section, and overclaiming creates immediate trust issues. I've watched candidates get grilled on statistical methods they claimed proficiency in and couldn't answer basic questions about. The resume looked strong on paper and fell apart in twenty minutes.

Quantify where it's easy. Years of experience, team size, budget ranges, percentage improvements, output volumes. Everything doesn't need a number, but anything that can be quantified without stretching the truth should be. One data point in a bullet is worth three descriptive sentences.

Common Pitfalls That Sabotage Otherwise Good Resumes

Photo inclusion is a significant issue depending on the country and industry. In the United States and United Kingdom, photos on resumes are strongly discouraged and can actually hurt your chances. ATS systems sometimes crash or misparse images, and many employers consciously or unconsciously filter out resumes with photos to avoid discrimination claims. In Germany or parts of Asia, photos are still standard and expected. Know your market before you decide. References on the resume are almost never necessary. "References available upon request" is filler that takes up space. Employers will ask for references at the appropriate stage regardless. Use that space for another bullet point or a relevant project description instead. I've reviewed hundreds of resumes and have never once needed someone to say "references available upon request" to make a hiring decision. Objective statements are largely dead except in very specific situations. A well-written resume speaks for itself. An objective like "Seeking a challenging position in a growth-oriented company" adds nothing. If you need a summary, make it a professional summary that highlights your most relevant qualifications in two or three lines. "Operations manager with eight years of experience scaling logistics workflows for e-commerce companies. Reduced average order fulfillment time by forty percent across three implementations." That's useful. The objective paragraph is not.

File naming matters more than people think. "Resume.pdf" tells the recruiter nothing. "John_Smith_Operations_Manager_Resume.pdf" is immediately searchable and helps your document survive even after it's been downloaded and stored in someone else's system. I've found myself searching for a specific candidate's resume months later and couldn't find it because it was saved as document1.pdf. Name your file with your name, target role, and the word resume. Length guidelines are flexible but have real consequences. One page is ideal for under ten years of experience. Two pages is standard for more experience. Three pages is almost never justified unless you're in academia with a publication list, or you're applying for a senior government position where detailed project histories are expected. A recruiter's default assumption is that someone who needs three pages doesn't understand how to prioritize information. Make them prove you wrong with content, not length. Here's something most guides won't tell you: tailoring your resume for a specific job posting usually takes between fifteen and thirty minutes if you already have a solid base document. The process is straightforward. Read the job description carefully and highlight the three to five most repeated requirements or keywords. Then go through your resume and make sure those terms appear in your work experience bullets or skills section. Not every keyword needs to be there, but the core ones should. This is different from just matching words. Context matters. If the job asks for "stakeholder management" and you wrote "client communication," change it. Same skill, different terminology. The ATS is looking for the language in the job description.

What This Approach Doesn't Handle Well

Keyword optimization has real limitations. Modern ATS systems are getting better at understanding semantic meaning, which means stuffing identical keywords repeatedly across your resume is less effective than it used to be and can actually trigger spam filters in some systems. A resume that reads like a keyword salad is worse than a resume with moderate keyword coverage and strong content. There's a threshold where optimization becomes counterproductive. This method also doesn't work well for career changers with limited transferable experience. If you're moving from teaching to software engineering and your work history contains zero relevant technical experience, a traditional resume structure will struggle to present your case convincingly. In that situation, a hybrid or functional resume format that leads with a skills-based summary and relevant projects may serve you better. But be aware that some ATS systems and recruiters view functional resumes with skepticism. They associate that format with people trying to hide employment gaps or short tenures. Use it strategically, not as a default. International resumes face additional complications. A resume that works in the US market may be considered incomplete in other regions where a personal statement, date of birth, or marital status is standard. Conversely, including those details in a US application can raise concerns. If you're applying internationally, research the norms for your target country specifically. There's no universal standard.

The most reliable way to verify your resume before sending it anywhere is to have someone who hasn't seen your career read it. Not a friend who wants to be encouraging. Someone who can tell you what they understood about your background after a single pass. If they walk away confused about what you actually do or can't identify your primary strengths, the resume needs work regardless of how good it looks on the page. I keep a master resume document with every job I've ever had, every skill, every metric, every project. When I apply for something, I pull from that master and cut it down to what's relevant for that specific role. This usually takes me about twenty minutes for a standard application and fifteen to twenty for a highly targeted one. The master document itself is thorough and occasionally unwieldy, but that's fine because nobody outside of me ever needs to see it. The application version is always the trimmed, purpose-built version.