Positioning, resume, LinkedIn

Headline: Delivery manager → AI [primary role] | [domain] | [scale hint]. Profile: three lines — who you help, the proof (a program, a number), the AI muscle (evals, thin slices, RAG/HITL — pick two). Then the latest role's bullets, each: situation, action, result. AI-related bullets go first if they are real. Recruiters skim 10 seconds. If the primary role is not in the first two lines, you are still a generic DM.

A headline that still says "PMP | Agile | Stakeholder Management | MS Project" is a 2016 headline. A headline that says "AI Delivery Lead | operations programs | multi-vendor, messy data" is a 2026 headline for the default pair. A headline that says "GenAI | LLMs | LangChain | GPT-4 | Agents | Transformers" is a keyword dump and a promise you will be asked to keep. Pick the first shape. Domain and scale are how a human remembers you. Tool lists are how an ATS matches you to the wrong req.

The three-line profile is positioning v1 compressed. Line 1: seat + who you help. Line 2: one program with a number. Line 3: two AI muscles and the honesty clause if the work is independent. Example: "Delivery lead moving into AI implementation for operations and claims-adjacent programs. Ran a 14-month multi-vendor cutover, 4 suppliers, steering every month. Design thin slices: retrieval, evals, HITL — independent work, not a production claim." That profile can be copied. Yours needs your nouns and your number.

First bullets of the latest job are the only bullets most screeners read. Put the messiest, most decision-shaped work first. "Owned RAID and cut-scope on [program], including the month-nine decision to drop a vendor workstream that could not hit UAT" beats "responsible for stakeholder communication." If you have a real AI workstream, it goes first. If you do not, the independent artifact bullet goes first in a Projects section or as the last of the four, labeled Independent — not buried after certifications.

Do not rewrite 2008–2014. Nobody is hiring you for the first PM job. Two pages maximum, one if you can. Dates, employer, title as they were (do not retitle yourself AI Lead on a job that was Project Manager). The headline and profile carry the pivot. Lying in the job title field is how background checks and old colleagues become a problem. You already know this. Do not get cute because the market is noisy.

Read the top third as a stranger with ten seconds and a stack of forty DMs. If they cannot say the seat out loud after ten seconds, rewrite. If they only remember tools, rewrite. If they remember a program, a number, and a seat, stop polishing and go to the honesty pass. Polish is how this day becomes a font exercise. You are not here to enjoy a resume. You are here to get a loop for the seat you picked yesterday.

Watch a hiring manager actually skim, because Dana's ten seconds are not a metaphor. She opens the PDF, reads the headline, reads two profile lines, reads the first bullet, and decides whether this is a delivery lead who can be put in front of a skeptical ops director or a generic DM with a new hobby. She does not reach page two. She does not read the certifications. She does not open the appendix of tools. If the seat is not speakable after that pass, she files you with the other forty DMs who managed stakeholders and delivered on time. That is why the top third does all the work. Rewrite it as if she will never be generous. She will not. Screeners are not cruel. They are busy. Busy people use the first two lines as a filter. Put the primary there, or you are still a generic DM no matter how good week three was.

The domain and scale hint is the line people skip because it feels like bragging. It is not bragging. It is how a human remembers you after forty PDFs. Multi-vendor operations, claims-adjacent, fourteen months, four suppliers: that is a picture. PMP, Agile, MS Project is not a picture, it is a 2016 default. If you have a domain, it belongs in the headline next to the seat. If you do not, stay with the delivery muscle and the slice, and do not invent passionate about healthcare. Invented domains fail the first conversation with a person who has that domain in their bones. Read the top third as a stranger. If they cannot say the seat out loud, rewrite. If they only remember tools, rewrite. If they remember a program, a number, and a seat, stop polishing. Polish is how this day becomes a font exercise.

Good: "Designed a retrieval-augmented copilot for a program wiki: chunking rules, recall@5 eval sketch, ACL/HITL non-goals, cost envelope at 10×." Good: "Built a versioned prompt library for status and RAID used on [workstream]." Good: "Wrote a use-case charter and operating pack (eval bar, HITL roster, $ at 10×, kill criteria) for an internal SOP assistant; independent, not production." Bad: "Expert in LLMs, LangChain, agents, and generative AI transformation." The bad one is how you get a technical screen you fail.

If the work was this academy, say "Independent: designed…" — that is allowed. "Led enterprise GenAI platform" is not, unless you did. If the work was a real program at your company, say exactly the slice you owned. "Ran vendor POC for a knowledge assistant: golden set of 40, death date, security path" is a strong bullet if true. "Championed AI adoption across the function" is a weak bullet even if true, because it cannot be probed without collapsing into slogans.

Situation, action, result still applies. Situation: messy wiki, stale SOPs, seniors as a helpdesk. Action: designed the slice, eval, HITL, cost. Result: a pack you can walk in 12 minutes, or — if real at work — a shadow pilot, a kill, a number. If there is no result yet because it is independent work, the result is the artifact and the judgment, not a fake 30% productivity claim. Invented percentages are how pivot resumes die in the first screen with a hiring manager who has seen too many of them.

One AI bullet is enough if it is specific. Three vague ones are worse than none. You may add a second if you have a prompt library actually used on a workstream, or a real RAID/eval you ran. You may not add a third that lists tools. Tools go in a short skills line, and only the ones you can discuss. If you are tempted to add LangChain because a post mentioned it, and you cannot talk through what it is for ten minutes, it is not a skill. It is bait.

FDE-primary bullets should sound like implementation, not like PMO. "Designed and (if true) ran a retrieve-and-generate loop on a 20-document corpus with a golden set and a refuse-when-empty path" is an FDE bullet. "Facilitated agile ceremonies for the AI squad" is not. Solutions-primary bullets should sound like discovery and qualification. "Ran a discovery that turned a chatbot request into a scored use case with a no on write-tools" is a solutions bullet. Transformation-primary bullets should sound like portfolio. "Scored N ideas, killed M, funded K with eval bars" — only if you did.

Read the bullet to a person who knows your job. If they laugh, it is inflated. If they say "I didn't know you did that," it is either a real hidden piece of work (keep) or a stretch (cut). If they say "that sounds like you," keep. The honesty pass is not only for tools. It is for volume. Delivery managers inflate hours and scope on resumes because everyone else does. You are trying to survive a second loop with an engineer in the room. Inflation is a time bomb. Cut it today.

Take one bad bullet and rewrite it live, on paper, before you touch the rest. Expert in LLMs, LangChain, agents, and generative AI transformation becomes Independent: designed a retrieval copilot for a program wiki, chunking rules, recall-at-five sketch, ACL and HITL non-goals, cost envelope at ten times. Read both out loud. The first one gets you a technical screen you fail. The second one gets you a conversation about judgment. If the work was this academy, the word Independent has to stay, or a recruiter will tidy it into Led. If the work was a real vendor POC at your company, say the golden set, the death date, and the slice you owned, not championed AI adoption. Situation, action, result still applies. If there is no result yet, the result is the artifact and the judgment, not a fake thirty percent. Invented percentages are how pivot resumes die in Dana's pile.

Altitude of the same work changes by primary seat, and stuffing all altitudes into one bullet is how you sound unplaceable. Delivery-primary: the charter, the eval bar, the kill, the steering fight. FDE-primary: the retrieve-and-generate loop, the refuse-when-empty path, the golden set on a corpus. Solutions-primary: the discovery that turned a chatbot request into a scored use case with a no on write-tools. Transformation-primary: scored N, killed M, funded K, only if you did. Do not write facilitated agile ceremonies for the AI squad and hope it flexes. One specific AI bullet is enough. Three vague ones are worse than none. Read the bullet to a person who knows your job. If they laugh, it is inflated. If they say they did not know you did that, it is either hidden real work or a stretch. Keep the first. Cut the second. You are trying to survive a second loop with an engineer in the room, not win a LinkedIn contest.

You will mention the academy artifacts on the resume, in LinkedIn, and in the intro. The phrasing is the difference between a professional with a portfolio and a person who took a course. Use: "Independent: designed [specific slice] with evals, HITL, and a cost envelope." Do not use: "Certified GenAI professional" or "Completed 30-day AI bootcamp" as the headline of your career. The artifacts are evidence. The month is not a credential. Hiring managers have seen the credential version. They have not seen enough people who can walk a charter.

Name the object, not the school. "Project-wiki copilot design: retrieval, ACL, refuse-when-empty, golden-set sketch." "Use-case charter and one-table operating pack." "Versioned prompt library for status and RAID." "12-minute walkthrough script." "90-day plan for the seat." Those lines are inspectable. "Fieldpath AI academy graduate" is not inspectable and sounds like a funnel. You may say in conversation that you used a structured month to build the pack. You may not make the month the story. The pack is the story.

If a recruiter asks "where did you build this," tell the truth in one sentence: "Independent work I designed this month so I would have a specific slice to walk, not a slogan. I have not deployed it in production. I have run [whatever is true: a notebook / no code / a vendor POC at work]." Then go back to the eval. Recruiters are used to bootcamp projects that pretend to be startups. Precision is how you separate. If you hide the independent nature, the second loop will find it and you will look like you hid it.

Do not put a GitHub link unless the repo is something you can talk through. An empty repo or a fork of a tutorial is worse than no link. A small folder with a README that matches the six boxes, an eval table in CSV, and a prompt spec is better than a cloned LangChain app you cannot explain. FDE and solutions may click it. Delivery and transformation often will not. Either way, the link is a promise. Only make it if you will keep it.

If your company owns a real artifact, lead with that and use the independent work as a supplement. "At [employer]: vendor POC charter, golden set, death date. Independent: wiki-copilot design to go deeper on retrieval and evals." That stacking is adult. The reverse stacking — academy first, real job as a footnote — is how you look junior. You are not junior. You have run programs. The paper should still look like a delivery leader who added a muscle, not like a career-switcher who erased a decade.

Write the exact artifact sentence you will paste, today, and reuse it on LinkedIn, the resume, and the intro. One sentence, not three versions. Version drift is how you get caught in a contradiction that was only sloppy. Delivery managers already version RAID logs. Version this sentence. When the pack changes on day 28, update the sentence if you must, once.

A recruiter will ask where you built this. Answer in one sentence, then go back to the eval. Independent work I designed this month so I would have a specific slice to walk, not a slogan. I have not deployed it in production. I have run a notebook, or I have not, or I ran a vendor POC at work: say whichever is true. Recruiters are used to bootcamp projects that pretend to be startups. Precision is how you separate. If you hide the independent nature, the second loop will find it and you will look like you hid it. Do not put the month in the headline of your career. The pack is the story. The month is how you built the pack. Hiring managers have seen the credential version. They have not seen enough people who can walk a charter. Be the second kind, in phrasing as well as in fact.

If your company owns a real artifact, lead with that and use the independent work as a supplement, not the other way around. At employer: vendor POC charter, golden set, death date. Independent: wiki-copilot design to go deeper on retrieval and evals. That stacking is adult. Academy first, real job as a footnote, is how you look junior. You are not junior. You have run programs. The paper should still look like a delivery leader who added a muscle, not like a career-switcher who erased a decade. Write the exact artifact sentence you will paste, today, and reuse it on LinkedIn, the resume, and the intro. One sentence, not three versions. Version drift is how you get caught in a contradiction that was only sloppy. Delivery managers already version RAID logs. Version this sentence. When the pack changes on day twenty-eight, update it once.

A skills line can say: RAG, evals, prompt specs, vendor POC charters, stakeholder delivery, [your domain]. It should not say PyTorch unless you can train something. It should not say Kubernetes unless you can talk a cluster. It should not say "GPT-4o" as if a model name were a skill. ATS is real; lying is also real and shorter-lived. Match the language of the posts you scored as 5s on day 22, but only the words you can defend for ten minutes.

Primary-seat keywords differ. Delivery: operating cadence, RAID, eval plan, HITL, cost envelope, vendor POC, steering, change. FDE: retrieval, thin slice, golden set, customer tenant, implementation plan, Python (if true), evals. Solutions: discovery, qualification, reference architecture, POC scope, objection handling, technical appendix. AI PM: PRD, evals as acceptance, refusal policy, cost/latency budget, scope cut. Transformation: intake, scoring, kill list, value realization, operating model. Put the primary set in the skills line. Put the backup set in the About, not as a second headline.

Domain keywords are underused and more honest than tool keywords. Claims, warehouse ops, public sector grants, clinical operations, trade finance — whatever you have actually delivered. A hiring manager in that domain will forgive an empty GitHub. They will not forgive a person who cannot talk their process. If you have a domain, it belongs in the headline. If you do not, do not invent one ("passionate about healthcare"). Stay with the delivery muscle and the slice.

Mirror a 5-scoring post without copying it. If they said "human-in-the-loop" and you said "HITL," that is fine — pick one and be consistent. If they said "evaluation harness" and you only have a golden-set table, write "golden-set eval plan," not "built an evaluation harness." Mirroring is not stuffing. Stuffing is listing twelve orchestrators. You can usually tell the difference because stuffing makes you slightly sick. Believe the nausea.

Delete three fake-strong words today as a ritual. Candidates: "expert," "thought leader," "end-to-end owner" (if you were not), "hands-on" (if you were not), "architected" (if you facilitated), "transformed" (if you ran a workstream). Replace with a noun and a number. The resume will look less expensive and more true. True is what survives the loop. Expensive is what gets you the first call and then a quiet rejection after the engineer round.

When you are done, search your own PDF for model names. For each one, ask: can I talk for ten minutes — what it is, what it is not, what I would measure, what I would not use it for? If no, delete. If yes, keep at most two. A resume that names eight models is a person who reads Twitter. A resume that names none and still says RAG, evals, HITL, and cost is a person who has done this month. That is the person the five seats are hiring.

ATS is real; lying is also real and shorter-lived. Match the language of the posts you scored as fives on day twenty-two, but only the words you can defend for ten minutes. If they said human-in-the-loop and you said HITL, pick one and be consistent. If they said evaluation harness and you only have a golden-set table, write golden-set eval plan, not built an evaluation harness. Mirroring is not stuffing. Stuffing is listing twelve orchestrators. You can usually tell the difference because stuffing makes you slightly sick. Believe the nausea. Primary-seat keywords differ, and unioning all five rows into one salad is how you get the wrong req. Put the primary set in the skills line. Put the backup set in the About, not as a second headline. Domain keywords are underused. Claims, warehouse ops, public sector: whatever you have actually delivered.

Delete three fake-strong words as a ritual, not as a mood. Expert, thought leader, end-to-end owner if you were not, hands-on if you were not, architected if you facilitated, transformed if you ran a workstream. Replace with a noun and a number. The resume will look less expensive and more true. Then search the PDF for model names. For each one, ask whether you can talk for ten minutes: what it is, what it is not, what you would measure, what you would not use it for. If no, delete. If yes, keep at most two. A resume that names eight models is a person who reads Twitter. A resume that names none and still says RAG, evals, HITL, and cost is a person who has done this month. That is the person the five seats are hiring. Dana will probe the first tool she does not believe. Do not give her an easy one.

Rewrite About from positioning v1, expanded to about 150 words. Same spine: seat, proof, number, two muscles, honesty clause, what you want. No buzzword salad. No "the future of work." No emoji. No carousel of five seats. The first two lines show on many surfaces without a click. Put the seat and the proof there, not a throat-clearing about being passionate.

Stealable shape: "Delivery lead moving into [primary role] for [domain]. I have run [program type] with [number: vendors, sites, months]. The hole I kept hitting was [knowledge / reporting / exception handling] that lives in people's heads. I now design thin AI slices — retrieval, evals, HITL, cost at 10× — and the operating pack that funds or kills them. Independent design work; not a fake production claim. Looking for [primary] seats where judgment plus enough building is the job. Happy to walk a wiki-copilot design or a charter." Then stop. If you want a backup seat mentioned, one clause, not a second paragraph.

Headline field on LinkedIn is not your job title at the current employer unless you want to stay there. It can match the resume headline: "AI Delivery Lead | operations programs | multi-vendor." Current employer title stays accurate in the experience section. Recruiters search headlines. Hiring managers at your company also read headlines. If you are applying internally, do not pick a headline that insults your current role. If you are applying externally and your company is sensitive, you already know how to be careful. Do not ask this academy to make that political call.

Featured and activity are optional. If you feature something, feature a writing sample you could defend (a public post about evals, not a motivational quote). If you cannot feature something honest, feature nothing. Empty Featured is better than a LinkedIn newsletter you generated and did not read. Comments on other people's posts do not get you the five seats. Conversations do. Day 30 will put conversations in the job OS. Today is paper.

Open to Work: use the recruiter-only flag if you need to, and list the primary title plus two noisy variants (Program Manager GenAI, AI Engagement Lead, Solutions Engineer — whichever matches the pair). Do not list Machine Learning Engineer. You will get the wrong mail. You will answer it because it feels like opportunity. It is not. It is a loop you will fail. Filter at the flag, not in your inbox at 11pm.

When the About is done, send it to one person who has seen you deliver and ask: "Does this sound like me, and can you tell the seat?" If they cannot tell the seat, rewrite. If they say it sounds unlike you — too grand or too small — rewrite. Then paste. Do not wait for a perfect week. The About can change after day 28 when the pack is assembled. Shipping a true paragraph today is the assignment. A draft in notes is not a LinkedIn About.

If you are employed and your company watches LinkedIn, you already know the politics. You can ship the About with a quieter headline and still put the primary seat in the first two lines. You can wait to turn on Open to Work until the pack exists. What you cannot do is leave a 2019 About that says you are a generic PM who likes teamwork. The paper you rewrote today and the public About have to agree, or a recruiter will ask which one is the lie. Make them agree. Then stop editing.

The first two lines of About show on many surfaces without a click. Put the seat and the proof there, not a throat-clearing about being passionate. Delivery lead moving into AI Delivery Lead for operations programs is a first line. Passionate about the intersection of delivery and the future of work is a first line that makes Dana close the tab. Expand positioning v1 to about one hundred fifty words: seat, proof, number, two muscles, honesty clause, what you want. No emoji. No carousel of five seats. If you want a backup mentioned, one clause, not a second paragraph. Headline field on LinkedIn is not your current job title unless you want to stay. It can match the resume. Current employer title stays accurate in Experience. Recruiters search headlines. Hiring managers at your company also read headlines. Do not pick a headline that insults your current role if you are applying internally.

Open to Work is a filter. Recruiter-only flag if you need it. List the primary title plus two noisy variants that match the pair. Do not list Machine Learning Engineer. You will get the wrong mail and you will answer it because it feels like opportunity. It is a loop you will fail. Filter at the flag. Featured stays empty unless you have a writing sample you could defend, a public paragraph about evals, not a motivational quote. Comments on other people's posts do not get you the five seats. Conversations do. Day thirty will put conversations in the job OS. Today is paper. Send the About to one person who has seen you deliver and ask whether it sounds like you and whether they can tell the seat. If they cannot tell the seat, rewrite. Then paste. A draft in notes is not a LinkedIn About. The paper you rewrote today and the public About have to agree, or a recruiter will ask which one is the lie.

Print or paste the top third and the About. Walk them with a red pen. Rule 1: every tool name must survive a ten-minute probe. Rule 2: every percentage must have a method. Rule 3: every "led" must be a thing you could call a colleague to confirm. Rule 4: the independent work is labeled independent. Rule 5: the primary seat appears in the headline and the first two lines. If a sentence fails a rule, cut or rewrite. Do not negotiate with yourself.

Add one number from your real past if the top third still has none. Headcount, budget, vendors, cycle time, sites, a go-live, a cut. If you cannot remember a number, you are still writing in adjectives. Open an old steering pack. The number is there. Put it in line 2 of the profile. This is the highest-leverage edit of the day. It is also the one people skip because they feel shy about scale. Shyness here reads as emptiness. You ran a thing. Say the size.

Delete the summary of responsibilities that duplicates the job description you were hired on. Nobody needs "responsible for managing risks, issues, and stakeholders." They need the month you killed a workstream, the vendor you held to a death date, the UAT you refused to start. Two of those bullets beat eight responsibilities. You are not applying to be a generic DM. You are applying to be the person who can do that job pointed at a model. The paper has to already sound like that person.

If you have a cert, it can live under education or as one short line. It cannot replace the artifact bullet. If you have no cert, do not panic-buy one this week. A cert without a walked charter is the trap from day 1. You are on day 25. The pack is the cert. Treat it that way on the paper.

Run the same pass on your recruiter screenshots and your email signature if those still say the old identity only. Consistency is not branding. Consistency is so you do not tell a recruiter you are an FDE and send a resume that says transformation. You picked a pair on day 22. The paper, the About, and the 90-second intro (tomorrow) all say that pair. If they disagree, the loop feels a lie even when you are honest, because the artifacts disagree with each other.

Stop at 80 minutes of editing. Diminishing returns on a resume are real and they eat day 26. Save a PDF named with the primary role and today's date. You will make a variant for the backup seat only if a loop for the backup is actually booked — not tonight "just in case." Just-in-case variants are how you send the wrong PDF. One primary paper. A backup paragraph in notes. That is enough.

Run rule three with a real name, not in your head. Every led must be a thing you could call a colleague to confirm. Pick the colleague. If you would not send them the bullet, cut the verb. Led the cross-functional AI working group, if you attended the meeting, becomes sat in a working group, or it dies. Architected the landing zone, if you facilitated, becomes wrote the RAID and the decision log for the landing-zone vendor. This is not modesty. This is so a background conversation does not become the reason a loop dies after you were the favorite. Delivery managers inflate hours and scope because everyone else does. You are trying to survive a second loop. Inflation is a time bomb. Cut it today, with a person in mind who could contradict you, because that person exists even if they are friendly.

Stop at eighty minutes of editing and save one PDF named with the primary role and today's date. Diminishing returns eat day twenty-six. A backup-seat variant exists only when a backup loop is booked, not tonight just in case. Just-in-case variants are how you send the wrong PDF. One primary paper. A backup paragraph in notes. Run the same pass on recruiter screenshots and your email signature if those still say the old identity only. Consistency is so you do not tell Priya you are an FDE and send Dana a transformation resume. You picked a pair on day twenty-two. The paper, the About, and the ninety-second intro all say that pair. If they disagree, the loop feels a lie even when you are honest, because the artifacts disagree with each other. Then stop. You are not here to enjoy a resume. You are here to get a loop for the seat you picked.