How To Position
Pick one target role and shape your story around it before you touch your resume.
By Kevin Tang · Updated July 2026
The short answer
Positioning means choosing one target role and shaping your resume around it before you write a single bullet. Pick one exact job title, not a broad category, and read about ten current postings for it to see which requirements repeat. Aim at the role your evidence can already back most of, then write a one line positioning statement, the role you are for and the outcome you deliver, that becomes your summary line and your answer to "tell me about yourself." One clear target makes every later choice on the resume easier.
Most job searches fail before a single application goes out, because the resume is trying to be all things to all employers. The fix is not a better template. It is a decision. Before you touch a word, choose who this resume is for. Everything in this chapter, and the three that follow, gets easier once you have made it.
Aim at one role, not a category
A resume that tries to fit three jobs fits none of them. Decide the exact title you are chasing: not "marketing," but "lifecycle marketing manager." Not "engineer," but "backend engineer, payments." Recruiters screen against one open req at a time, and applicant tracking systems score you against that one job description. When your resume is built for a specific target, every later choice gets easier, because you finally have a rule for what belongs and what does not.
Say you have done a bit of everything: some data analysis, some project coordination, some client work. The instinct is to list all three so you qualify for more jobs. It backfires. The data team reads the project work and the client work as noise and passes you over for someone who looks all-in on data. Pick the role you want next and the one your evidence supports best, and let that choice run the rest of the page. You are not deleting the other skills, you are deciding which story leads.
Read ten postings before you reread your own resume
One job posting is an anecdote. Ten is data. Pull up ten current listings for your target role at companies you would actually join, and read them with a notepad open. You are not applying yet. You are reverse engineering what this role is supposed to prove. As you read, capture four things:
- The exact skills and tools that appear in most of them, written in the words the posting uses.
- The responsibilities phrased as outcomes (owns retention, ships features, closes deals), not chores.
- The seniority signals: team size, budget, scope, and who you would report to.
- The phrases that repeat verbatim across postings. Those are your keywords.
Requirements that show up in eight of ten postings are the real job. Ones that appear once are noise. Rank them by how often they recur, and you have an ordered list of exactly what your resume has to demonstrate.
Here is what that looks like in practice. One posting for a lifecycle marketing manager repeats "email automation," "segmentation," and "A/B testing," names "owns the retention number" as the headline responsibility, mentions a "team of four," and asks for "four-plus years." Across ten similar postings, email automation and segmentation appear in nine, retention ownership in eight, a specific tool (say Braze or Iterable) in six. That tally is the job. Your resume's entire task is to prove the top of that list, in the posting's own words.
Write one line that says who you are for
Positioning is a single sentence you can say out loud: "[Role] who [does the valuable thing] for [type of company]." A few that work:
- "Product manager who takes zero-to-one B2B tools from prototype to paying customers."
- "Backend engineer who keeps payment systems fast and correct at high volume."
- "Financial analyst who turns messy operational data into forecasts leadership actually uses."
Each names the role, the outcome, and the context, so a stranger who read only that line would know exactly which job to hand you. Vague versions like "results-driven professional seeking a challenging opportunity" say nothing, and they cost you the scan. This line becomes your resume summary, your LinkedIn headline, and the first thing you say when someone asks what you do.
Target a role your evidence can reach
Ambition is good; delusion is expensive. Take your top-five requirements from the tally and ask, honestly, how many you can already back with real work. If you can prove three or four, this is a fair target, and the remaining gap is a story you can tell. If you can prove only one, you are aiming a level too high, and no amount of clever wording will hide it.
Two situations need extra care here. If you are changing fields, do not claim the destination title outright while your evidence does not back it yet. Lead with the transferable proof (the analysis, the ownership, the shipped result) that the new role rewards, and name the target as a direction rather than a done deal. If you are early-career or a new grad with little formal work, your evidence is projects, internships, and coursework that produced something real people used. Treat those as the work, because to the reader they are. Aim at the entry-level version of the role and prove you can already do a slice of it.
Use their words, not your company's jargon
Your employer may call the job "growth ninja" or "associate II." The market does not search for those. If your real title is obscure, keep it accurate but add the market-standard equivalent beside it, for example "Associate II (Financial Analyst)," because both a recruiter skimming and an ATS keyword filter are hunting for the common term. The same goes for internal tools: nobody outside your old company searches for "the Atlas dashboard," so name the category ("internal analytics dashboard") too. Positioning is partly translation, taking what you actually did and stating it in the vocabulary the target role already uses. The ATS resume guide covers this keyword matching in full.
Cut everything that does not serve the target
Positioning is subtraction as much as addition. The unrelated job from six years ago, the certification that points at a different career, the paragraph about a project nobody asked about: if it does not support your one line, it is diluting it. A caterer turned developer does not need three bullets on banquet logistics; one honest line covering the years is enough. This can feel like throwing away evidence of hard work. It is not. A focused resume is not a shorter career, it is a clearer argument. Keep what proves you can do this job, and move the rest to a single "additional experience" line or off the page entirely.
A gap in your history is not something positioning has to hide. Account for it in one plain line ("2023: full-time caregiving" or "2022: contract work and upskilling") and let the rest of the page do its job. Recruiters notice unexplained gaps far more than explained ones. State it once, without apology, and move on.
Do this work once and the next three chapters get faster. You will write bullets against a known target (Chapter II), apply only where you genuinely fit (Chapter III), and walk into interviews already knowing the story you are there to tell (Chapter IV).