Multi-ToolCareer

The AI Skill Worth Learning Now: Context Engineering

Prompt engineering was never really a job, and the models got good enough to do it for you. The skill that's actually sticking is context engineering. Here's what it is and how to start.

4 min read3 sources
  • #career
  • #context-engineering
  • #agents

There's a comforting story going around that "prompt engineering" was the hot new career. As an EM who hires for these skills and uses the tools every day, I'll be blunt: it was never really a job — and the models got good enough to make the title disappear. What's actually sticking, and what's worth your time, is context engineering.

Prompt engineering is what you say to the model. Context engineering is everything the model can see when it answers.

That sounds like a small distinction. It changes how you work.

Why the title died but the skill didn't

The "$200K prompt engineer" headlines peaked back in 2023. Two years later that standalone role has mostly evaporated — not because the skill stopped mattering, but because it spread into every job and the models started asking their own clarifying questions. AI literacy is now one of the fastest-growing skills employers ask for, yet almost nobody hires a "prompt engineer" anymore. That's the pattern to internalize for your own career: AI rarely deletes the work, it deletes the job description wrapped around it.

What context engineering actually is

The moment you build anything past a one-off chat — an agent, a workflow, a Claude Project — the prompt is a tiny slice of what decides the output. The real levers are the system instructions, the tools you expose, the examples you show, what you retrieve, and how much history you carry between turns. Anthropic frames the goal cleanly: curate the fewest high-signal tokens that get the result you want. More context isn't better; the right context is.

There's even a failure mode with a name — context rot: cram the window with everything and the model gets measurably worse at finding what matters.

Four moves that pay off immediately

  • Cut, don't cram. Every token you add competes for the model's attention. Remove anything that isn't pulling its weight.
  • Retrieve just in time. Don't front-load every doc "in case." Pull in the file, data, or reference at the moment the task needs it, so the window stays lean and on-topic.
  • Teach with examples. One or two clear, representative examples steer behavior far better than a long list of rules and edge cases.
  • Make tools unambiguous. If a teammate couldn't tell which tool to reach for, neither can the agent. Name and scope each one so the choice is obvious.

The four moves on one real prompt

Watch what the moves do to an actual support-reply agent. Before — everything, just in case:

[full 12-page product manual pasted]
[last 40 messages of chat history]
[every reply template we own]
[3 tool descriptions, two of them near-identical]
Answer the customer.

After — the same job, curated:

SYSTEM: You answer billing questions. Warm, two sentences max.
RETRIEVED: [only the refund-policy section, pulled by the customer's question]
EXAMPLE: Q: "Charged twice?" → A: "I see the duplicate — refunding the extra
now, it lands in 3-5 days. Sorry for the scare."
TOOLS: lookup_charge (find a charge by email) · issue_refund (reverse one charge)
Customer says: [message]

Cut the manual and stale history, retrieved one section on demand, taught with one example, and named two tools you can't confuse. Same four moves, done.

This week

Take one prompt or Project you lean on often and audit its context, not its wording. Delete one thing that isn't earning its place, add one good example, and rerun the same task. That edit — not a cleverer sentence — is context engineering. Do it a few times and you'll have the skill the market is actually paying for.

Sources