Prompt engineer: what the job is, what it pays, and whether it still exists

In short: a prompt engineer designs and debugs requests to AI models so that they reliably solve a real task. But as a standalone job title, the role has largely dissolved: the skill moved inside other roles — analysts, developers, marketers, product managers. Learning it is worth it; earning a living "on prompts alone" mostly isn't.

What a prompt engineer actually does

The title misleads: it sounds like someone spends the day composing elegant phrases for a chatbot. In practice the work is closer to engineering debugging. The brief is: "make the model produce a usable result across a thousand different inputs, not just on your one lucky example." Hence the actual work:

• Framing the task. Turning a vague "let AI handle customer requests" into a testable requirement with clear good/bad criteria.
• Designing the prompt. Role, context, format, examples, constraints — the basics from what a prompt is and how to write one.
• Testing. A set of dozens of real cases, a run, a comparison between prompt versions. Without this you're guessing.
• Fighting failures. The model lies, ignores the format, breaks on long inputs, drifts from the instruction. All of it gets fixed in the prompt, the data, or the architecture.
• Wiring in data and systems. Often the answer must rest on the company's knowledge base, not the model's memory.

Think before reading on: if the model got your task wrong in one case out of twenty — how would you even find out which one? Being able to answer that is half the profession.

Where the hype came from and why it deflated

In 2023 the models were more temperamental and the market was disoriented. A couple of loud job ads with six-figure dollar salaries made the headlines, and a sense of a new gold-rush profession appeared: "type text into a chat, get paid like a senior engineer". Then three things happened.

1. Models got smarter. Current versions understand plain human phrasing far better. Magic incantations like "you're a genius and my career depends on this" stopped producing any visible effect.
2. The skill turned out to be literacy, not a profession. Like knowing how to use search or a spreadsheet: critically useful, but nobody hires a "search operator" as a dedicated headcount.
3. Real problems turned out to be bigger than the prompt. A business doesn't need request text; it needs a working system with data, quality evaluation, cost control and safety. That's a different role.

About salaries — honestly

You've surely seen articles with specific figures. Treat them carefully: the numbers usually come from a handful of loud postings at the peak of the hype, from aggregators with tiny sample sizes, or from reports by companies that benefit from interest in the topic. There is simply no reliable average "prompt engineer salary" today — because there is no stable, widespread job title by that name.

What can be said without lying: you get paid for a role, not for prompts. ML engineer, data scientist, AI developer, product manager with an AI specialisation — those positions have a real market and real ranges, and prompt skill is one requirement among many, not a substitute for the rest. If you see a promise of “become a prompt engineer in a month and earn X” — that's selling a myth, not career advice.

You can check this in five minutes without taking our word for it: open any job board and search for the exact phrase “prompt engineer”, then for “AI engineer” or “machine learning engineer”. The difference in the number of results tells you more about the market than any salary survey. While you're there, read the requirements on the few postings that do turn up: almost certainly they'll list code, data and domain experience, with prompting itself as one bullet out of ten.

So the skill is useless?

It's needed — just differently. It has become part of baseline work literacy. Industry reports point at this indirectly: the World Economic Forum's Future of Jobs Report (2025) estimates that around 39% of key job skills will change by 2030 and names AI as the fastest-growing skill; Microsoft and LinkedIn's Work Trend Index (2024) reports that roughly 75% of surveyed knowledge workers already use AI at work, and around 71% of leaders would rather hire a less experienced candidate with AI skills than a more experienced one without them.

The caveat without which those numbers mislead: both reports come from interested parties (one company sells AI products and a hiring platform, the other lives on business attention to the topic), and both rest on surveys rather than objective measurement. Treat them as an order of magnitude and a direction of travel, not as fact. But the direction matches what's visible anyway: AI skills are increasingly demanded inside ordinary job ads.

What good prompt people actually become

• AI engineer / AI developer — builds products on top of models: integrations, agents, knowledge-base search. Code required.
• Product or project manager with an AI focus — knows where AI fits, what it breaks and how to measure the benefit. Less code, more product thinking.
• AI quality specialist — assembles test sets, evaluates outputs, catches regressions. Little glamour, lots of value.
• An amplified specialist in their own field — a marketer, lawyer, analyst or teacher who does their job noticeably faster. The most common and most underrated path.

A separate trend is AI agents: systems that carry out multi-step tasks with tools. There the prompt is only one layer — but nothing works without it. A neighbouring story is vibe coding, where code gets written through dialogue with a model.

Where to start if the topic grabs you

1. Take your own task, not a textbook one. A prompt without a real problem is an exercise in a vacuum.
2. Learn the basics. Role-task-context-format, examples inside the prompt, constraints, permission to say "I don't know".
3. Build a test set. Ten real inputs and a clear idea of what a correct answer looks like. That's what separates an engineer from an enthusiast.
4. Learn to catch lies. Understanding why AI hallucinations happen, and the techniques against them, is half the practical value.
5. Compare models. The same task behaves differently across them — see the comparison of ChatGPT, Claude and Gemini.

You are helping me debug a prompt.
Here is my task: [describe]. Here is the current prompt: [paste].
Here are three cases where the output was bad: [paste inputs and what went wrong].
Task: find which instructions or inputs are missing,
propose an improved version of the prompt, and explain exactly what you changed and why.
Do not rewrite from scratch — edit surgically.

The takeaway, without hype

"Prompt engineer" as a standalone profession was largely a one-season phenomenon. The skill, though, hasn't gone anywhere — it simply stopped being a job title and became part of normal work with AI. Learn it not for the line on your resume but so your actual profession runs faster. The practical side is in our article on AI for work, and the "will I be replaced" anxiety is covered in will AI replace my job.