How to write a resume for a job title that barely exists yet
Forward deployed engineer. AI product manager. MLOps engineer. Context engineer. Every hiring cycle mints job titles that didn't exist two years earlier — and by definition, nobody applying has five years of experience in them. This guide covers the specific mechanics of writing a resume for an emerging role: how to translate adjacent experience, which keywords to mirror, and how to prove capability for a job the market is still defining.
For an established title, the screening pipeline is calibrated: recruiters know which keywords to search, which companies produce good candidates, and what five years of progression looks like. For an emerging title, none of that calibration exists. The recruiter is often working from a JD the hiring manager wrote last month, screening for a role their company has never hired before.
That changes the game in your favor in two ways. First, keyword competition is thin — few resumes contain "forward deployed" or "LLM evals" at all, so honest use of the role's vocabulary makes you findable. Second, nobody has the "standard background," so the resume that wins is not the one with the title already on it; it is the one that translates adjacent experience most convincingly.
The failure mode is writing your resume in your old role's language and hoping the reader does the translation. They won't — you have to.
The translation method
Every emerging role is a recombination of existing ones. A forward deployed engineer is a software engineer crossed with a consultant who ships at customer sites. An AI product manager is a product manager whose surface area includes model behavior, evals, and prompt iteration. An analytics engineer sits between data analyst and data engineer. Your first task is to name the recombination the role actually is, then evidence each half.
Concretely: take the JD and split its requirements into (a) things you have done under a different name, and (b) things genuinely new. For (a), rewrite your bullets using the JD's vocabulary — the work of a "solutions engineer who embedded with clients for integration projects" IS forward-deployed work, and your resume should say so in those words, without changing the facts. For (b), close the gap with evidence: a shipped side project, a production experiment at your current job, a published write-up.
The summary is where the translation gets stated explicitly: "Solutions engineer with 5 years embedding with enterprise clients — the forward-deployed pattern — now specializing in LLM integration projects." One sentence, and the recruiter no longer has to figure out why you fit.
Emerging fields have unstable vocabulary: one company's "AI engineer" is another's "LLM engineer" is another's "member of technical staff." Recruiters search all the variants, so your resume should carry the cluster, honestly placed: the title you're targeting in your summary, the variants in context in your bullets ("built agentic workflows," "ran model evals," "shipped RAG pipelines").
Mirror the specific job description hardest — for a new role, the JD's exact phrasing is the best available data about what that company's ATS search will contain. Include the tools by exact name: the model families, frameworks, and infrastructure the JD mentions. And keep everything defensible; in a new field, interviewers probe claimed experience quickly, because they are also still figuring out what expertise looks like.
We maintain dedicated keyword-and-example guides for 100+ specific roles — including the fast-emerging AI titles — in the resume-guide section of this site; find your target title there for its current keyword set.
Proving capability without the years
Nobody has ten years of prompt engineering. Hiring managers for emerging roles read for capability signals instead of tenure:
Shipped evidence in the new domain, at any scale. A production feature at work beats everything; a side project with real users beats a certificate; a certificate beats a claim. "Built an internal RAG assistant on our support docs — deflects ~30% of tier-1 tickets" is a junior-scale bullet that outweighs years of adjacent seniority.
Learning velocity, demonstrated. The half-life of specifics in these fields is short, so evidence that you track the frontier matters: what you built last quarter with tools that shipped this year.
Judgment from the old domain. Emerging roles are staffed with people who bring mature judgment from an adjacent craft. Senior evidence from your prior role is not filler — it is the reason to trust you with an undefined one. Keep your strongest legacy bullets; frame them as transferable judgment, not history.
Positioning for the wave, honestly
One warning: do not retitle yourself into a job you haven't done. "AI Product Manager" as your header when your actual title was Product Manager is defensible only if you genuinely shipped AI product work — and the standard, honest format is "Product Manager (AI features)" or a summary line that makes the claim precisely. Reference checks in small, new fields are unusually easy; the communities are tiny.
The durable play is the opposite of inflation: pick the emerging role adjacent to your real strengths, do one real piece of work in it now — at your job if possible, publicly if not — and write the resume that connects the two with exact, checkable claims. Early markets reward the candidate who is verifiably 70% there over the one who claims 100%.
Paste the emerging-role job description into the free scorer with your resume — it will show precisely which of the JD's terms your resume already carries and which are missing.
