Some job postings describe a seat that has been warm for a decade. Others describe a seat that nobody has ever sat in, and those read differently once you know what to look for. If the role is new, the posting is a wish list written by someone who does not yet know exactly what the job is, and the cover letter that wins is the one that proposes a shape for it.
How to tell a role is the first of its kind
Hiring managers rarely write "this is a new position" in bold. They leave clues instead, and you can usually find three or four of them in a single read.
- The title is invented or oddly specific. "Head of Customer Operations and Automation", "AI Enablement Lead", "Partnerships Manager, Marketplace". When a title has a comma or an "and" in it, someone stitched two needs together.
- The posting says "first", "founding" or "build". "You will be our first dedicated...", "build the function from scratch", "establish processes". That is the giveaway.
- The requirement list contradicts itself. Deep technical skill plus executive presence plus hands-on execution plus team leadership, for a mid-level salary.
- There is no "you will join a team of X". A role with predecessors usually mentions the team. A new role often mentions only the boss.
- The verbs are about creating, not maintaining. "Define", "set up", "launch", "own the roadmap" instead of "manage", "support", "report on".
If you see two or more of these, treat the posting as a draft. That changes how you read it and how you write back.
Read the posting for the pain, not the list
A role that did not exist last quarter exists now because something started to hurt. Maybe customers are churning and nobody owns retention. Maybe the founder is spending her evenings on vendor contracts. Maybe a competitor shipped something and the board asked a pointed question. The requirement list is the hiring manager's guess at the person who would make that pain stop.
So the useful question is not "do I match the bullets?" It is "why does this role exist now?" Look for the answer in three places:
- The first paragraph of the posting. Hiring managers often explain the context before they start listing skills, and they are more honest there.
- The company's recent news. A funding round, a new product line, a new market, a reorganisation, a regulator knocking. New roles tend to follow these events by a few months.
- The bullet that appears first or gets the most words. That is usually the thing keeping the manager awake.
Once you have a hypothesis about the pain, write it down in one sentence. "They have grown past the point where sales can run partnerships on the side." If you cannot write that sentence, you are not ready to write the letter.
Propose a shape for the first 90 days
This is the part most candidates skip, and it is where you can stand out. The hiring manager has a vague picture. You give them a sharper one. Not a full strategy, not a slide deck, just a short sketch of how you would approach the first three months.
Keep it modest and conditional. You do not know the internal situation, and pretending you do is the fastest way to sound arrogant. Three moves are usually enough, framed around listening first:
- Weeks 1 to 4: talk to the people who currently absorb the pain, map what exists, find the one or two quick fixes.
- Weeks 5 to 8: propose a scope for the role in writing and get it agreed with your manager.
- Weeks 9 to 12: deliver one visible result that proves the role was worth creating.
Notice what this does. It shows you understand that defining the job is part of the job. It shows you will not arrive with a plan copied from your last employer. And it gives the reader something concrete to react to in the interview.
Avoid the lecture
There is a line between proposing and preaching. "Your onboarding is clearly broken" crosses it. "From the outside, it looks like onboarding is where the role could make the earliest difference, and I would want to check that in the first weeks" does not. Use "it looks like", "I would want to check", "my guess is". One hedge per idea, then move on.
When no single human matches the list
New roles attract inflated requirement lists because the manager is describing an imaginary person who covers every gap. Nobody matches all of it, including the eventual hire. Trying to claim every bullet makes you look either dishonest or unfocused.
Instead, pick the two or three requirements that map directly to the pain you identified. Prove those with specific evidence. Then say plainly that you are choosing. Something like: "Your list is broad, which makes sense for a role that is just starting. I have focused this letter on the two things I think matter most in the first year."
That sentence does a lot of work. It shows judgement, which is the real qualification for an undefined role. It also quietly signals that you read the posting as a draft, not as scripture. Whether you should apply at all when you miss half the list is a separate question; here we assume you have already decided to go for it.
Illustrative excerpt
Here is a short example for a posting titled "Partnerships Lead (first hire)" at a software company that recently opened a reseller programme. The details are invented for illustration.
Your posting reads like a role that sits between sales and product, and I think the reason it exists now is the reseller programme you announced in the spring. Somebody needs to own those relationships before they start owning you.
>
I have spent the last three years building a partner channel from zero at a logistics software firm, starting with two resellers and a shared spreadsheet. The part I am proudest of is not the revenue; it is the onboarding kit that let partners sell without calling us every afternoon.
>
If I joined, I would spend the first month talking to your current resellers and your sales team, then come back with a written scope for the role. Your list of requirements is wide, so I have focused here on partner onboarding and deal structuring, which look like the two that matter most right now.
Notice what it does not do. It does not claim every bullet, does not prescribe a full strategy, and does not ask about salary or reporting lines.
Risk questions: which go in the letter, which wait
A new role carries real risk for the person who takes it. Nobody knows yet if it will survive the next budget cycle, who will defend it, or how anyone will judge it. You are right to care about that. The question is when to raise it.
Worth a light touch in the letter:
- How success will be measured. You can fold it into your 90-day sketch: "I would want to agree early on how we will judge whether the role is working." That shows maturity without demanding answers.
Better saved for the interview:
- Who the role reports to, and whether that might change.
- Whether there is a budget, headcount, or tooling attached, or if you start with a laptop and goodwill.
- Why the role is being created now and who pushed for it internally.
- What happens if the first hire does not work out.
Asking these in writing before anyone has met you can read as defensive. Asking them in a conversation reads as serious. Make a list, bring it to the first interview, and listen carefully to how the manager answers. A vague answer to "how will you know this role is working?" tells you a lot.
Keep the rest of the letter tight
Everything else about the letter stays the same as any good cover letter: one page, a specific opening, evidence over adjectives. If your experience sits mostly on LinkedIn, a tool like Postulit can turn that profile into a clean CV to send alongside the letter, so the letter can focus on the argument instead of retelling your history.
The difference with a new role is the centre of gravity. For a well-defined job, you prove you fit the box. For a job with no precedent, you help draw the box, then show you are the person to fill it.
Before you send it, check the letter against one test: could the hiring manager forward your 90-day paragraph to their boss as a starting point for the role? If yes, you have written the letter this posting was quietly asking for.