TLDR: Hiring markets run a roughly three-year cycle where employers write job descriptions covering three or four roles and attach a salary that wouldn’t cover one. The trap catches competent people specifically, because only someone with the full scattered skill stack reads the description and feels recognised by it. Employers lose too, through burnout, quality decline, and a reopened requisition within the year. When a role reads like it needs a unicorn and pays below market for one discipline, the salary is the honest signal.
Bait
There were warning signs, I suppose, in the job title. AI Personalization and Growth Marketing Manager, which is three disciplines fused into one, though I didn’t think much of it at the time because the description below it felt familiar: integrate language models into the CRM stack, build test-and-learn workflows, own the logic for real-time content assembly, and act as the internal subject matter expert for a team that had never done any of this before. Five responsibilities, each of which I’ve done somewhere, which is the feeling these descriptions are engineered to produce.
The recruiter, warm and efficient and just back from Ibiza, described the person they wanted as a marketing engineer, and I thought yes, that’s a real thing, I’ve been that. The salary came at the end of the call, as it always does, and it was eighty to ninety thousand pounds for a role in London requiring two days a week in the office, barely above the average for London, and when I gave her my range she said she’d check whether there was flexibility. What arrived instead, the very next day, was a rejection claiming the role actually required someone who independently navigates Snowflake and BigQuery, writes complex SQL, manages production language model edge cases, and builds data-piping solutions for real-time product engines, most of which I’ve done actually, and none of which appeared in the JD I’d applied to or in the forty minutes we’d spent on the phone.
Cycles
I don’t say this to complain about one company, which would be tedious, and anyway the more interesting fact is this isn’t new. It ran in 2020, when I’d open a listing and find four jobs stapled together with a salary that wouldn’t have covered one of them in the city they expected you to commute into daily. It ran again in 2023, and now again in 2026, and the three-year rhythm is regular enough that I’m less surprised and more curious about the mechanics. Earlier this year I came across a listing for technical writing, UX writing, and localisation, three distinct crafts each with its own literature and its own professional bodies and its own conference circuit, offered at thirty thousand pounds in London, which is less than a single one of those roles commands and roughly what you’d need to not quite afford a flat in zone four.
The cruelty of it, and I use that word deliberately, is in who it catches. Someone underqualified reads a description like that and closes the tab, because they know they can’t do it and the description has done its job as a filter. But someone who’s spent fifteen years accumulating precisely that scattered combination of skills, who studied computer science and informatics and taught database courses and wrote for engineers and spent a decade in growth marketing and learned to orchestrate language models because the tools arrived and seemed obviously useful; that person reads the same four-job description and thinks, with something close to relief, that finally here is a role that wants all of it. Pick me. That thought, that flare of recognition, is what the description is fishing for, and it most reliably snags the ones most capable of doing the work and therefore most valuable to underpay.

Everybody loses
What happens next is predictable. The person takes the job, because they’ve been looking for months and the description spoke to them, and for the first quarter they’re brilliant, then they start context-switching between four disciplines every day and getting good at none of them, and quality declines, and sick days accumulate, and eventually a company with a properly scoped role and properly benchmarked salary makes a call and they take it, because of course they do, and the requisition reopens and all the institutional knowledge walks out the door. Everyone else on the team has spent nine months watching their colleague drown in a badly scoped job and has drawn their own conclusions about how the place treats people. The company has spent that time paying for a solution it didn’t get, and now it’s paying agency fees again, and the entire arrangement has cost more than simply hiring the right number of people at the right price in the first place.
Unicorns
But what I keep returning to, what seems to me more fundamental than the economics, is that unicorns don’t need to exist. We have horses. We have rhinos. We have narwhals, which are magnificent and strange and perfectly adapted to swimming under Arctic ice. A creature combining all three isn’t an upgrade on any of them, and not even coherent as a design, because consider the practical difficulty of a horned horse lowering its head to graze: the horn goes straight into the dirt. You’ve taken three functional animals and produced one that can’t feed itself. The reason unicorns are mythological is because that’s the only place they work.

Companies build job descriptions the same way, taking three coherent roles that each have a clear shape and known market rate and fusing them into something that reads impressively in a requisition and can’t be performed by a single person. Then they price the composite below the market rate for its cheapest component, and then, when a candidate points out the mismatch, they discover they wanted something else entirely all along, something they’d neglected to mention, which is a graceful way of saying they never scoped the job and were hoping someone would show up and solve that problem for them and not ask too many questions.

So here’s some advice for anyone reading a description and thinking the role is asking for a rare combination you happen to be: that’s a warning. You shouldn’t have to be a statistical anomaly to be employable, and if a company has written a role only an anomaly could fill and then priced it below market for a single discipline, they’ve just told you a great deal about how they think, what they understand about the work, and how they intend to close the gap between what they need and what they’re willing to pay, which is with your evenings. Read the scope, read the number, and if the two don’t meet, the number is the honest one.