In 2023 “prompt engineer” was the job you could land without a degree and quote a fat number for. The trade press ran the headlines, the LinkedIn banners updated overnight, and a generation of people who had never shipped a line of code suddenly held a title that sounded like one. Two years on, the standalone postings have all but gone. The role did not graduate. It evaporated.
The odd part is what outlived it. Class Central still catalogs more than 2,800 prompt-engineering courses, a working monument to a skill the market has quietly stopped hiring for. The usual reading is that the models got good enough that everyone can prompt now, so the specialists folded back into the crowd. I think the arc says something less flattering. It was never a skill. It was a tax.
What the craft actually was
Strip the mystique and prompt engineering was a bag of coping mechanisms for a tool that couldn’t take a plain request. You opened with “you are an expert” because a bare question got you a worse answer. You added “take a deep breath” and “think step by step” because someone measured that the incantation moved the score. You fenced your input in triple backticks, threatened the model, bribed it with a fake tip, and stacked three examples in front of every real ask because one-shot fell over. None of that was about your work. All of it was about steering a system that could not simply be told.
Call that a craft if you want. It was unpaid QA. The vendor shipped an interface that misread ordinary language, and rather than fix it, they let a folklore grow up around the misreading and called your fluency in it a competency. You were doing the tool’s error handling by hand, on your own time, and paying for a course to learn how.
Read the cottage industry back the other way and it stops flattering anyone. The 2,800 courses and the job titles that once sounded like engineering: none of that is evidence that phrasing a request is deep and valuable. A thriving market in workarounds is a bug report with a price tag on it. Nobody sells a syllabus on how to phrase an email to a capable colleague, because the colleague understands you. The size of the prompt-engineering economy was never a measure of how skilled you had to be. It was a measure of how badly the interface had failed.
When the vendor tells you the trick was the problem
The most honest account of this came from inside the building. At the AI Engineer World’s Fair in 2025, OpenAI’s Sean Grove got up and pointed out that developers prompt a model, keep the output, and throw the prompt away, which he compared to shredding the source and then carefully version-controlling the binary. His point was that the disposable thing in that loop is the prompt. The tricks were never the artifact worth keeping. Even the people who sold you the model think the incantation was a phase.
So here is the line you get to disagree with. Being proud of your prompt-craft is Stockholm syndrome. It is affection for the demands of your captor, mistaking the effort you spent appeasing a broken tool for a talent you possess. When “prompt engineering is dead” trends, the correct feeling is not grief for a lost specialism. It is relief. A defect got repealed. The thing you were forced to compensate for stopped being your problem, which is exactly what should happen to every workaround that ever earns a course.
The skill you keep is the one you already had
Now the objection I owe you, because Brief is in the business of telling people to write good instructions. Isn’t a brief just a prompt with better manners? No, and the difference is the whole argument. Briefing is telling a capable associate what a good outcome looks like, in the same plain words you’d use with a person you trust. Prompt engineering was memorizing the quirks of a thing that couldn’t be trusted to hear you the first time. One is communication you have done your entire working life. The other is compensation for a tool that failed at the only job an interface has.
A system that needs a secret handshake to understand you has told you something about itself, not about you. The right response to a decade of prompt cheat-sheets is not nostalgia and it is not a certificate. It is to expect the tool to meet you where you already speak, and to treat any product that still asks for incantations as what it is, which is unfinished. Keep the judgment. Keep the clarity about what you actually want. Bin the phrasebook. You were never supposed to learn the border language of a country you were only passing through.
Brief is opening to a small group at a time. Direct a team instead of operating one more tool.
Request access