Refolk
October 23, 2026·9 min read

BBC Cuts 1 in 10 Roles. A 'BBC' Search Finds 4.7 Journalists per Engineer

The BBC's cuts hit the newsroom, not tech. Where its engineers sit, when the 45-day consultation rule lets them leave, and how to find them via github.com/bbc.

BBC job cuts 2026BBC redundancies engineershire BBC software engineersSalford tech talentUK collective redundancy 45 days
BBC Cuts 1 in 10 Roles. A 'BBC' Search Finds 4.7 Journalists per Engineer

If you're waiting for thousands of BBC engineers to hit the market after the October 20, 2026 announcement, you'll be waiting a long time. A figure of 2,300 cuts has circulated, but no major outlet reports it. The BBC is reducing headcount by roughly one in ten over several years, the October announcement was mostly newsroom roles, and its technologists are buried under journalists in any employer search. If you want to hire BBC software engineers, start with the code they commit, not the employer they list.

What did the BBC actually announce on October 20?

On October 20, 2026, the BBC announced around 100 BBC News roles and about 10 BBC Scotland roles. Both are part of a multi-year target of 1,800 to 2,000 positions. No major outlet has reported a 2,300 figure, and none of the October cuts were engineering teams.

The bigger target is real. The BBC aims to remove between 1,800 and 2,000 positions, close to one in ten of its roughly 21,500 employees. Trade press calls it the biggest round of BBC redundancies since 2011. But it is spread over years, and some of it has already happened.

TrancheRolesWhat it covered
Multi-year target1,800 to 2,000About 1 in 10 of ~21,500 staff
June~550Earlier round, already cut
Oct 20, BBC News~100Newsroom, £5.5m toward a £51m target
Oct 20, BBC Scotland10Closing the linear channel

Two people are making the decisions. Matt Brittin, a former Google executive, became director-general on May 18, 2026. Rachel Jupp is director of BBC News. The BBC also says it intends to keep compulsory redundancies to a minimum, and that matters a lot for sourcers (more on that below).

How many of the BBC redundancies are engineers?

None of the announced cuts so far hit engineering teams, and the strategy behind them probably protects tech jobs. The October cuts fell on linear channels and the newsroom, and the content from those channels is moving onto iPlayer and Sounds, so the platform teams are picking up work rather than losing it.

BBC Three, BBC Scotland and Radio 4 Extra are going off air. Brittin's line was that much of their content "will still be found where audiences already enjoy them on iPlayer and Sounds." That is the mechanism to understand. The channels close, the programming survives, and the streaming platforms that inherit it still need the people who build them.

So don't plan for a flood of 2,000 engineers. Plan for a smaller, slower stream of technologists who leave voluntarily. That stream is smaller than the headline, but it skews toward the people you most want to hire, because the first to take a voluntary package are the ones confident of landing elsewhere.

Why does a "BBC" employer search mostly find journalists?

A "BBC" keyword search mostly returns editorial staff and alumni, not current engineers. In Refolk's index, only 1.2% of UK profiles with "BBC" in the headline carry an engineering title, and editorial titles outnumber them 4.7 to 1.

Here is the breakdown from three queries in Refolk's index, UK only, keyword "BBC". Shares and the ratio are derived from the counts.

GroupCountShare of all "BBC" headlines
All UK "BBC" headlines36,605100%
Journalist / producer / editor / presenter titles2,1255.8%
Software / data / platform engineer, EM, developer titles4511.2%
Ratio, editorial to engineering4.7 : 1n/a
Engineering sample currently at a BBC entity15 of 2560% (sample)
4.7 : 1
Editorial to engineering titles among UK "BBC" headlines
In Refolk's index, 2,125 journalist, producer or editor profiles against 451 engineering profiles.

The noise runs deeper than the ratio. The top titles in the 36,605 pool are CEOs and CTOs at startups like Trint and Clippd. Most of them are BBC alumni or people who mention the BBC in their headline. Even inside the engineering slice, 4 of 25 sampled profiles matched "ABC Consultants," which is substring noise. Only 15 of 25 engineering profiles in the sample currently worked at a BBC entity.

A current-employer filter catches the people who advertise the BBC and misses many of the people who build it. This is the gap Refolk closes. You describe the person, something like "backend engineer who has worked on iPlayer, based near Salford," and Refolk checks that against GitHub activity and profile history together instead of matching the word "BBC" in a headline.

Where do the BBC's technologists actually work?

The BBC's engineers sit in four tech hubs: London, Salford, Newcastle and Glasgow. Salford's MediaCityUK is the one the BBC calls "our national HQ for digital teams."

A few details that change how you search:

  • Salford shows up as Manchester. Engineering profiles in Refolk's sample often list "Manchester," because Salford rolls up into it. Filter on Salford alone and you miss them. A 2020 count put 3,200 staff across six departments at MediaCityUK (an old figure, but it gives you the scale).
  • Newcastle is a real cluster, not an outpost. 4 of 25 sampled engineering profiles were in Newcastle, Gateshead or South Shields. The BBC set up its Newcastle hub to work on BBC iPlayer, BBC Sounds and BBC News Online.
  • Glasgow and London round it out. The graduate scheme places engineers across all four hubs.
  • The stack is mainstream. The BBC's graduate programme lists JavaScript, Python, Scala, AWS, Java, Kotlin and Swift, so these engineers' skills transfer well beyond broadcasting.

What BBC engineers are paid

Advertised BBC engineering pay runs from £43,000 to £53,000 at mid-level, £55,000 to £65,000 at senior, and up to £85,000 for a Salford iPlayer engineering team lead.

RoleAdvertised BBC pay
Mid-level software engineer£43,000 to £53,000
Senior software engineer£55,000 to £65,000
iPlayer engineering team lead, SalfordUp to £85,000

The mid and senior bands come from an older posting, so treat them as indicative rather than current. They still give you a benchmark to build an offer against.

When can BBC staff actually leave under the 45-day rule?

Under UK collective redundancy law, an employer proposing 100 or more dismissals within 90 days at one establishment has to consult for at least 45 days. That minimum is a floor, it is counted per site, and contractual notice comes on top of it.

The rules that shape your timeline:

  1. The 45-day clock starts when consultation formally begins, not when the announcement hits the press.
  2. It is a minimum. It is the statutory floor, not the ceiling, and consultation can run longer.
  3. Thresholds are counted by establishment, not across the company. Salford and London run separate clocks, and the 45-day minimum only applies where a single site crosses 100 proposed dismissals.
  4. Notice periods stack on top. Consultation ending is not the same as someone being free to start with you.
  5. The 90-day proposal isn't law. A plan to bring back a 90-day minimum had not been enacted as of August 2026.

Here's the arithmetic. If consultation opened on October 20, the earliest any dismissal could take effect is around December 4, 2026. Add contractual notice, and a realistic start date moves into Q1 2027.

The window for BBC engineers isn't the next few weeks. It runs from now through the end of Q1 2027.

That is good news if you're sourcing. You have time to build a relationship before the candidate is officially on the market.

How do you find BBC engineers through github.com/bbc?

Start with the BBC's public GitHub organisation, which has 977 repositories, and work back from contributors to people. Commit history tells you who builds which product far more reliably than a headline does.

977
Public repositories in the github.com/bbc organisation
Each one has a contributor list that maps engineers to the products they ship.

A practical workflow:

  1. Pick repos by product, not by stars. bbc/simorgh is the React app behind World Service sites (1,715 stars, 280 forks, updated October 1, 2026). bbc/peaks.js and bbc/audiowaveform are the most-starred audio tools in the org, which points you toward audio engineering. bbc/sofie-core is the BBC's fork of the Sofie studio automation system, which is broadcast tooling.
  2. Pull the contributor list and filter for recency. Someone who committed last month is probably still there. Someone whose last commit was years ago is probably an alum, and you've likely met them already in that 36,605-profile noise pool.
  3. Separate staff from outside contributors. Open-source repos attract external pull requests. Check for org membership, a BBC email address in commit metadata, or repeated reviews on other people's PRs.
  4. Match the GitHub handle to a profile. This is the slow step. Handles rarely match names, and many BBC engineers never put the BBC in their headline at all.
  5. Note location from the profile, not the repo. Check for Manchester, Newcastle, Gateshead and Glasgow as well as Salford.

Step 4 is where most sourcers give up, and it's the step Refolk does for you. You ask in plain English and get back people matched across their GitHub activity and profiles.

Who leaves first when redundancy is voluntary?

When the BBC keeps compulsory redundancies to a minimum, the first people out are the ones most confident they'll get hired elsewhere. Those are usually the engineers you want, and they show up in code activity before they update a profile.

The mechanism is self-selection. A voluntary package suits people who already have options. So the signal to watch is behaviour, not job titles:

  • Commit cadence changes on bbc repos, either a burst of handover work or a sudden drop-off.
  • New personal repos or side projects appearing alongside BBC work.
  • Profile changes like a new headline or a refreshed portfolio link.

Waiting for an "ex-BBC" headline means you reach them after everyone else does. Tracking recent commits to bbc repos month to month gets you there first.

Where ex-BBC technologists go

Alumni show you where these engineers tend to land. Trint, a startup founded by a BBC alumnus, is one of the top employers in Refolk's index results for "BBC" headlines. If you're pitching a BBC engineer, a company like that is the comparison you're competing against.

FAQ

Is the BBC really cutting 2,300 jobs in 2026?

No major outlet has reported 2,300. The BBC's own target is 1,800 to 2,000 positions over several years, about one in ten of its roughly 21,500 staff. About 550 positions were cut in June. On October 20, the BBC announced around 100 BBC News roles and 10 BBC Scotland roles. None of the announced cuts were engineering teams.

Are BBC iPlayer and Sounds engineers being made redundant?

Not in the October announcement. The cuts fell on linear channels and the newsroom. Content from BBC Three, BBC Scotland and Radio 4 Extra is moving to iPlayer and Sounds, so the platform teams probably gain work. Engineers who do leave are more likely to go through voluntary redundancy than to have their roles cut.

How long does UK collective redundancy consultation take?

Where 100 or more dismissals are proposed within 90 days at one establishment, the minimum is 45 days from when consultation formally begins. It is a floor, it's counted per site, and contractual notice comes on top. If consultation started October 20, 2026, the earliest dismissals land around December 4, and realistic start dates fall in Q1 2027.

What's the fastest way to hire BBC software engineers?

Skip the "BBC" current-employer filter. In Refolk's index, only 1.2% of UK "BBC" headlines belong to engineers. Start with recent contributors to github.com/bbc repos like simorgh, peaks.js and audiowaveform. Match their handles to profiles, include Manchester and Newcastle in your location filters, and benchmark your offer against advertised BBC pay: £55,000 to £65,000 for seniors, up to £85,000 for a Salford iPlayer team lead.

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next