How to Write a Resume That Actually Gets Read

A resume is not a career biography. It is a one-page argument that your background is relevant to a specific type of role. Most people get the format, the writing, or the selection wrong. This guide covers all three.

14 min read · By TeaKo

Before You Start: You Need Raw Material

This guide will teach you how to structure, write, and select what goes on your resume. But it assumes you already have something to work with: a clear inventory of your best experiences, projects, and results.

The tool for this is a hype doc: a private document where you collect every meaningful project, achievement, and contribution you have made -- written in full detail using the STAR method (Situation, Task, Action, Result). It is the raw material you will draw from when building your resume. If you have never built one, the section below on turning a hype doc into resume bullets shows exactly what an entry looks like.

If you skip this step, you will end up writing your resume from memory, and memory is a terrible editor. You will forget your best work, default to generic descriptions, and miss the results that actually make a bullet point strong.

Spend an hour on it before you write a single resume line. Everything below assumes you have that raw material to draw from.

Keep It Simple

The first mistake most people make has nothing to do with content. It has to do with presentation.

Many candidates spend hours choosing fonts, adding color accents, inserting icons, or using multi-column layouts. This effort is not just wasted -- it often works against them.

A resume should be a plain, clean, single-column document with no visual noise.

Here is why:

Applicant Tracking Systems (ATS) parse plain text. Columns, text boxes, images, and headers inside graphics often get scrambled or dropped entirely. A recruiter may never see your best bullet point because the parser could not read it.
Recruiters scan resumes in seconds. Visual clutter slows scanning. A clean layout with clear section headers, consistent formatting, and enough white space lets a reader find what they need faster.
Design does not compensate for weak content. A well-designed resume with vague bullet points will lose to a plain resume with specific, result-oriented evidence. Every time.

The practical rule: use a single-column layout, one readable font, consistent spacing, and black text on a white background. Bold your job titles. Keep it to one page unless you have more than ten years of relevant experience. That is it.

No colors. No images. No icons. No sidebars.

The resume that gets read is the one that is easy to read.

The Only Sections You Need

A strong resume does not need many sections. It needs the right ones, in the right order, with the right weight.

Based on the structure used at top business schools like INSEAD, the sections below are all you need.

Header

Your name, email, phone number, and one relevant link (LinkedIn or GitHub, depending on the role). Nothing else. No photo, no address, no date of birth.

Summary

Two to three lines that frame who you are professionally. This is not an objective statement. It is a positioning statement.

A good summary tells the reader three things: what type of professional you are, what kind of environment you have worked in, and what your strongest analytical or technical tools are.

Compare these two summaries for the same person:

Weak:

Analyst with experience working in startups. Skills include Python, SQL, Looker, Databricks, Prefect, Airflow, Excel, Hadoop, JIRA, Git, Google Analytics.

This is vague. "Experience working in startups" says nothing about what kind of analyst or what level. The skills list is a dump of every tool with no signal about where the person is strongest.

Strong:

Business-savvy Analyst with 6 years of experience working in fast-paced startups. Analytical hard skills: Python, SQL, Looker, Databricks, Prefect, Airflow, Excel.

This version states a role identity ("business-savvy analyst"), a level signal ("6 years"), a context ("fast-paced startups"), and a curated toolset. A recruiter reading this immediately knows what kind of candidate they are looking at.

Professional Experience

This is the section that matters most. It takes up the majority of the page and carries the most weight in any screening decision. We will cover how to write it in the next two sections.

For each role, include:

Job title and dates (right-aligned)
Company name, a brief descriptor, and location
Tech stack or tools used in that role
Two to four bullet points describing your most relevant work

List roles in reverse chronological order. Most recent first.

Education

Degrees, certifications, and relevant training. Keep it brief. Include the institution, degree or program name, and year. If you completed a relevant bootcamp or professional certificate, include it here.

Education goes last unless you are a recent graduate. Once you have two or more years of work experience, your professional experience section is what matters.

What to Leave Out

You do not need sections for "Interests," "Hobbies," "References," or "Languages" unless the role specifically calls for them. Every line on your resume should earn its space. If a section does not help the reader evaluate your fit for the role, remove it.

How to Write Your Experience: Action Verbs and Results

This is where most resumes break down. The problem is not that people lack experience. The problem is that they describe it in a way that sounds like a job description rather than a record of impact.

Every bullet point should start with a strong action verb in the past tense and end with a measurable or observable result.

The Formula

A strong resume bullet follows this pattern:

[Action verb] + [what you did] + [how or with what] + [result or impact]

To see why this matters, look at the same role described two different ways.

Side-by-Side: Same Experience, Different Signal

| Weak (what most people write) | Strong (what gets interviews) | |-------------------------------|-------------------------------| | Work on A/B tests related to transaction fees | Conducted A/B tests to optimize Mastercard/Visa fees, reducing costs by $5.5M annually | | Handle reports and data pipelines | Automated 20+ unstructured reports using Python pipelines and Looker, enabling self-service analytics | | Work on acquisition costs and conversions | Decreased customer acquisition cost by 20% across Paid Social and SEM by optimizing channel mix and running A/B tests | | Help improve support workflows | Reduced customer support demand by 10% by improving first-time resolution through testing and script redesign |

Same experience. Different signal. The difference is how the work is described.

Choosing the Right Action Verb

The verb at the beginning of each bullet sets the tone. Weak verbs make strong work sound routine. Strong verbs signal ownership, initiative, and capability.

Verbs to avoid: "Helped," "Assisted with," "Was responsible for," "Participated in," "Worked on." These verbs hide your actual contribution behind a passive frame. Notice how every bullet in the weak example above started with "Work on" or "Handle" -- verbs that describe presence, not contribution.

Verbs that work, organized by the type of contribution they signal:

Achievement and initiative: Accelerated, Built, Created, Delivered, Established, Implemented, Launched, Reduced, Transformed
Analysis and research: Analysed, Assessed, Diagnosed, Evaluated, Identified, Investigated, Mapped, Validated
Leadership and management: Coordinated, Directed, Led, Oversaw, Spearheaded, Supervised, Drove
Strategic planning: Automated, Designed, Developed, Formulated, Initiated, Proposed, Restructured
Communication: Authored, Briefed, Presented, Published, Reported

Pick the verb that most precisely describes what you did. "Led" is different from "Coordinated." "Built" is different from "Contributed to." Precision matters.

Words to Avoid

Some words carry negative or passive connotations that weaken your resume even when describing real work: Tried, Attempted, Assisted, Helped with, Participated, Relied on, Failed, Avoided.

If you find yourself writing "Help improve support workflows," ask yourself what your specific contribution was. Did you build a hypothesis tree? Run A/B tests? Redesign the script? Use the verb that reflects your actual role.

Make Results Visible

The result is the part most people leave out, and it is the part that makes a bullet point memorable.

Compare these two bullets describing the same marketing optimization work:

Weak:

Work on acquisition costs and conversions

Strong:

Decreased the average customer acquisition cost of Paid Social and SEM campaigns by 20% and leveraged SEO. Optimized channels' investment mix and conversion rates of art and copy by running A/B tests

The weak version tells you the person worked in the area. The strong version tells you what changed, by how much, and how they did it.

Results can be quantitative (reduced costs by 20%, saved $5.5M, automated 20 reports) or they can describe a concrete outcome (enabled self-service analytics, launched branches in two new cities, enabled multiple optimization projects). Both work. The point is that the reader should finish the bullet knowing not just what you did, but why it mattered.

What Experiences to Include: From Hype Doc to Resume

You have more experience than your resume can hold. The question is not "what have I done?" It is "which subset of what I have done makes the strongest case for this type of role?"

This is where your hype doc becomes essential.

The Hype Doc as Raw Material

Your hype doc contains the full story of each project or achievement, written using the STAR method:

Situation: What was the context or problem?
Task: What was your specific responsibility?
Action: What did you actually do?
Result: What happened as a consequence?

Here is what a hype doc entry looks like for a real project:

Situation: A partner deal assumed to reduce transaction processing costs was being applied broadly without validation.

Task: Evaluate whether the routing strategy tied to the partner deal was actually cost-efficient.

Action: Analyzed transaction-level data and segmented costs by route, partner, and transaction type. Identified subsets where the partner route was more expensive. Built a cost model and presented findings to leadership with an alternative routing proposal.

Result: Uncovered up to $8M in potential yearly savings and influenced a change in transaction routing strategy.

That is the full story. It has context, detail, and evidence. But it is far too long for a resume.

Compressing STAR Into a Resume Bullet

The skill of resume writing is compression: taking a full STAR story and distilling it into one or two lines that preserve the action and the result while dropping the setup.

Here is how to do it:

Step 1: Drop the Situation. The reader does not need the backstory. They need to know what you did and what happened. The context of the company or role is already clear from your job title and company description.

Step 2: Merge the Task and Action. Your task and your action often overlap. "Evaluate whether the routing strategy was cost-efficient" and "Analyzed transaction-level data, identified subsets where costs were higher" collapse into one statement about what you actually did.

Step 3: Keep the Result. This is the part that differentiates you. A bullet without a result reads like a job description. A bullet with a result reads like evidence.

Step 4: Lead with the strongest action verb.

Here is what this compression looks like in practice:

Hype doc (STAR):

Situation: Partner deal applied without validation. Task: Evaluate cost-efficiency of routing strategy. Action: Analyzed transaction-level data, segmented costs by route and type, identified subsets where partner route was more expensive, built cost model, presented to leadership. Result: $8M/year in potential savings, routing strategy changed.

Compressed bullet (resume):

Identified an opportunity to save up to $8M per year by analyzing transaction routing costs, uncovering inefficiencies in a partner deal and proposing an alternative strategy.

The full context is gone. What remains is the action, the method, and the outcome. That is all a screener needs.

One More Example: When Results Are Not a Number

Not every project ends with a dollar figure. Here is a STAR entry for an operational improvement:

Situation: Supplier approvals were handled manually, creating delays and inconsistencies.

Task: Move suppliers toward an automated approval process while maintaining data quality standards.

Action: Analyzed supplier data structures and identified key quality indicators. Built a framework for automated approvals and implemented a routine review system using internal tools and data checks.

Result: Enabled scalable supplier onboarding and reduced reliance on manual review processes.

Without compression, the person writing from memory might write:

Handle supplier approval processes

With compression from the hype doc, the resume bullet becomes:

Moved suppliers from manual to auto-approval: Leveraged supply chain object data to help suppliers improve their data transparency and created an automated routine review process to ensure standards were followed

Same work. One version sounds like a task. The other sounds like an accomplishment.

Choosing Which Experiences Make the Cut

Not every entry in your hype doc belongs on your resume. Selection criteria:

Relevance to your target role. A bullet about optimizing ad spend belongs on a marketing analyst resume. It may not belong on a data engineering resume. Match your bullets to the role you are pursuing.
Strength of result. Bullets with quantified outcomes or clear business impact rank higher than bullets that describe process without outcome.
Recency. Recent work carries more weight. Prioritize the last three to five years unless older experience is unusually strong.
Variety of skills demonstrated. Avoid four bullets that all describe the same type of work. Each bullet should show a different dimension of your capability: analytical, technical, leadership, communication, or strategic.

Two to four bullets per role is the right range. If you have more good material than fits, save the extras in your hype doc. They will be useful for interviews, cover letters, and tailoring your resume to specific job descriptions later.

Practical Checklist

Before you consider your resume done, verify each of these:

The layout is single-column, black and white, with no images or icons
The resume fits on one page (two pages only with 10+ years of relevant experience)
Every bullet starts with a past-tense action verb
Every bullet includes a result or observable outcome
No bullet starts with "Responsible for," "Helped," or "Worked on"
Each role has two to four bullets, not more
The Summary section states your role identity, context, and tools -- not a generic objective
Education is listed after Professional Experience (unless you are a recent graduate)
You have removed any section that does not help the reader evaluate your fit
The experiences you selected came from your hype doc, not from memory

The Resume Is a Translation Layer

Most career switchers do not have an experience problem. They have a packaging problem.

The work is already there. The results already happened. The challenge is compressing that work into a format that a recruiter can scan in seconds and immediately understand why you are relevant.

A strong resume does not describe everything you have done. It presents the specific subset of what you have done that makes the best case for what you want to do next.

Start with a hype doc that captures the full picture. Then compress, select, and format. The resume is not where you tell your story. It is where you make your argument.

Once your resume is structured, the next useful step is seeing how it maps to the roles you are targeting. A tool that compares your background against real job descriptions can make the gaps -- and the overlaps -- visible. That is what TeaKo is built to do.