✶ The SHIFT Playbook
The role you should retrain into (and the 90-day path to get there)
You watched two of the most powerful people in AI disagree about whether your job survives. Here is the part neither of them said out loud: you don't pick a side. You pick a destination.
The roles getting eaten first are predictable. So are the ones getting built. Below is the exact map I use with operators stuck between "AI is coming for me" and "I have no idea what to do about it." Three of the most exposed roles, where each one is heading, and the skills that carry you across.
Part 1 · The role map
01SDR→AI GTM Engineer
What changesYou stop sending the sequences. You build the system that sends them, books the meetings, and updates the CRM on its own.
Skills that bridge the gapPrompt design for outbound, Claude wired into your CRM, one automation tool (Make or n8n), and the offer math behind a campaign.
First proof to shipRebuild one outbound play as a working agent. Measure replies against your old manual numbers.
02Junior Copywriter→Prompt Librarian
What changesYou stop writing one-offs. You own the prompt library and the brand voice system the whole team writes through.
Skills that bridge the gapPrompt engineering, encoding a brand voice into reusable templates, and the editing taste to catch where AI output goes flat.
First proof to shipTurn your 10 best pieces into one repeatable prompt system. Hand it to someone else and watch them get 80% of your quality.
03Tier-1 Support→Agent Supervisor
What changesYou stop answering tickets. You train, QA, and improve the agent that answers them, and you handle the edge cases it can't.
Skills that bridge the gapWriting knowledge bases an agent can actually use, evaluating agent responses for accuracy, and designing clean escalation paths.
First proof to shipBuild a support agent on your own docs. Track how many tickets it deflects in week one.
Part 2 · The 90-day path
This works for any of the three transitions above. The point is not to learn everything. It is to ship something while everyone else is still arguing in the comments.
Days 1 to 30 · Pick & rebuild
Choose your destination role. Learn one tool deeply (Claude). Rebuild a single task from your current job as an AI workflow.
Days 31 to 60 · Ship & document
Build 3 working systems. Document each one. Post the builds publicly. This is your portfolio for the new role.
Days 61 to 90 · Package & pitch
Pitch the new role internally with your portfolio, or take one paid project doing it for someone else. Either way, you now have proof, not a plan.
# the whole playbook in one line
> pick destination → learn Claude → rebuild 1 task
> ship 3 → document → post publicly
> pitch role OR land 1 paid project
The people who win this aren't the ones who learned the most. They're the ones who shipped something while the rest debated Altman vs Amodei.
Want me to look at your role?
Reply with the job you're in right now and I'll tell you the AI-era version of it, plus the one skill to start on this week.
Join the build ✶
Automate the unscalable.
Mike