Barclays Is Cutting Developers. Pune's Clear Before the UK's 45 Days

Barclays told investors on Oct 22 that it will cut about 5,000 roles, and its finance director named "fewer developers" as one of the reasons. About 4,000 of those cuts are still to come before December, but the engineers won't all reach the market on the same day. If you're trying to hire laid-off bank software engineers, timing matters as much as where you search.

What Barclays actually announced on Oct 22

Barclays is cutting about 5,000 full-time roles, roughly 5% of its workforce. About 1,000 people left in the first half and the other ~4,000 are due out by December. Group Finance Director Anna Cross put developers in the frame herself, on the record:

"Around 60% of the Group actions relate to support functions, including fewer developers as AI makes our people more productive."

She added that the cuts "remain subject to collective and individual consultation as required." Remember that phrase. It drives the timing picture below.

The CEO tells it differently. C.S. Venkatakrishnan called AI "the icing on the cake, not the cake," and gave most of the credit to platform consolidation and fewer process steps. The only AI metrics Barclays has published measure adoption, not output. The bank is profitable, too: Q3 profit rose 12% to £2.3bn, and it booked another £201m in "structural cost actions" in the quarter.

Three weeks before the results, on Oct 1, Barclays said Claude Code should reach 50% of its developers by end-2026 and a majority in 2027. The rollout belongs to Group co-COOs Craig Bright and Anne Marie Darling, and the stated purpose is to "modernize legacy platforms, improve software quality." Reports put the centre of the cuts in the UK retail bank, with job losses also expected in India, where much of the UK back-office support sits.

Why Pune developers hit the market before UK staff

India technology centre staff will mostly be free first, not because the cuts start in India but because of the law. UK staff are held up by a statutory consultation floor, while most India IT staff are governed by their employment contracts.

Collective consultation is the legal duty to consult employee representatives before making redundancies. Under TULRCA s.188, 100 or more redundancies at one establishment within 90 days means at least 45 days of consultation before the first dismissal. Add notice periods and garden leave, and most UK Barclays engineers won't be free to start until Q1 2027.

India has no equivalent clock for most of this population. IT employees in managerial or supervisory roles who earn above the wage threshold usually fall outside "worker" status under Indian labour law. Their contract sets the notice period, and there's no consultation requirement unless a recognised union exists.

There's one caveat. The Karnataka High Court has held that non-supervisory software engineers can count as "workmen." That status brings one month's notice plus 15 days' pay per year of service. It adds a little friction, but nothing like 45 days of consultation before anyone can leave.

If you have a bank-grade req open now, the UK group can't help you this quarter. A December start is realistic in Pune. In London or Glasgow, the same candidate will be sitting out notice and garden leave until well into the new year.

The 43-to-3 gap: why headline searches miss UK engineers

Searching for "Barclays" in profile headlines finds India engineers and almost none in the UK. That tells you how people write their profiles, not how many engineers each country has. In Refolk's index of professional profiles, 43 India profiles have "Barclays" in the headline and a software-engineer or developer title. The same query in the UK returns 3.

14.3x

The reason is simple. Engineers in India commonly tag their employer in the headline, as "Barclays" or "BTCI." UK engineers mostly don't. A Boolean search on headline keywords quietly filters out nearly the whole UK population.

Read the last row with care. 24,864 India profiles mention Barclays somewhere, but only 8 of 25 sampled were currently at a Barclays entity. That number is a rough guide to the size of the alumni network, not a count of people employed there today.

Where to search in India: entity names and cities

Start with Pune, then Chennai, and search under the captive-centre entity names as well as "Barclays." According to Barclays' careers site, Pune (Kharadi) is its largest site outside London, with about 9,000 staff across Operations, Technology and Functions. Chennai has 5,000+.

Entity names to search

A captive centre (or GCC) is an offshore unit a company owns and runs itself rather than outsourcing. Barclays' India operation appears under several names:

• Barclays Technology Centre India (BTCI): a tag India engineers use in their headlines.
• Barclays Global Service Centre (BGSC): the other main captive-centre name.
• Barclays India Solutions: shows up on third-party GCC profiles. Include it in your search, but don't rely on it alone.
• Barclays Shared Services: I couldn't verify this as a current entity name. Test it on a small search before building a pipeline around it.

Cities, in priority order

Official Barclays India office lists name Pune, Mumbai, Noida and Chennai, and Gurugram appears in job ads. Refolk's India developer sample breaks down like this:

1. Pune: 13 of 25 (52%). Kharadi is the main search term.
2. Chennai: 2 of 25.
3. Hyderabad: 2 of 25.
4. Gurugram: 2 of 25.
5. Bengaluru: 1 of 25.

No official Barclays source lists Bengaluru, so don't tell a hiring manager to expect a Bengaluru pipeline from Barclays. Lead with Pune and Chennai, and treat Hyderabad and Gurugram as secondary.

Searching all of this by hand gets messy quickly: four entity names and five cities don't fit cleanly into one Boolean string. With Refolk you describe the person in plain English and get a ranked shortlist back, so the entity aliases don't have to be spelled out one by one.

How to find the UK group

UK Barclays engineers rarely put the bank in their headline, so search the current-employer field and filter by city. The only UK regions in Refolk's sample were Glasgow and Manchester. That fits: Glasgow is Barclays' tech campus and the UK counterpart to Pune.

A practical UK search setup:

• Current employer = Barclays. Don't use headline keywords.
• Location = Glasgow first, then Manchester.
• Title = software engineer or developer.
• Timing: build the list in December, make light contact, and expect start dates from January into Q1 2027.

Engineers in consultation can't commit to a start date, but they will take a conversation. If you introduce yourself in December, you'll be a familiar name when their notice period starts.

How to sort modernisers from legacy maintainers

The tool Barclays bought is meant for legacy code, so ask each candidate what they did with legacy code. Engineers who led platform migrations or adopted Claude Code early are the modernisers. Engineers who maintained UK retail-bank systems with no migration exposure are the group the tool was bought to replace.

This goes one step past "AI is cutting developers." Barclays said Claude Code exists to "modernize legacy platforms," and the cuts centre on the UK retail bank. Read together, that suggests the people leaving are disproportionately those whose job was keeping old systems running, not the people moving those systems somewhere new.

Barclays didn't buy Claude Code to replace builders. It bought it to replace the people who keep old platforms alive.

That doesn't make maintainers bad hires. People who kept retail-bank systems running know those systems from the inside. But you need to know which kind of engineer you're getting. Screen with questions like these:

• "What did your last migration move from, and to what?" Modernisers name the source and target platform without hesitating.
• "Did your team use Claude Code or another AI coding tool, and what changed?" Barclays only announced the scaled rollout on Oct 1, so early adopters chose to be early.
• "What did you decommission?" People who maintain systems keep them running. People who modernise switch them off.
• "Which part of your system would you rewrite first, and why?" This tests judgement, not tenure.
• "Retail bank, investment bank, or group functions?" Cross said ~60% of cuts fall in support functions, and that context shapes the answers to everything above.

Keep Venkatakrishnan's framing in mind as well. If AI really is "the icing, not the cake," then platform consolidation is doing much of the cutting. Engineers whose platform was consolidated out of existence may be strong. Their system simply lost the merger.

The alumni channel: a third have already left

Barclays India developers who have already moved to other employers are a separate sourcing channel and a path for referrals. In Refolk's sample, 8 of 25 India developers (32%) already list a non-Barclays employer.

32%

That points to a steady flow of engineers out of the captive centre, well before this round. For a recruiter, alumni are useful in three ways:

1. Referrals into current teams. Alumni still know who in Pune and Chennai is good. They can introduce you before the December wave.
2. Proof the pool travels. A Barclays-to-Google or Barclays-to-HSBC move shows that BTCI experience counts outside the bank. Use that when your hiring manager hesitates.
3. A read on the competition. HSBC already hiring Barclays alumni tells you at least one other bank values this pool.

FAQ

When will Barclays' laid-off developers be available to hire?

India technology centre engineers will mostly be available first, in November and December, because their exit is governed by contractual notice rather than a consultation period. UK engineers face at least 45 days of collective consultation under TULRCA s.188 before the first dismissal, followed by notice and garden leave. That pushes most UK availability into Q1 2027.

Why does a headline search find so few UK Barclays engineers?

Because UK engineers rarely put their employer in their headline. In Refolk's index, a headline search finds 43 India developer profiles mentioning Barclays and only 3 in the UK. Search the current-employer field instead, and filter by Glasgow and Manchester.

Is Barclays cutting jobs in Bengaluru?

There's no sign of a Bengaluru pipeline. No official Barclays source lists Bengaluru as an India office, and only 1 of 25 sampled Barclays India developers is there. Official lists name Pune, Mumbai, Noida and Chennai, with Gurugram in job ads. Pune (Kharadi, about 9,000 staff) and Chennai (5,000+) are where to look.

Should I avoid Barclays engineers who maintained legacy systems?

No, but know which kind you're hiring. Barclays bought Claude Code to modernise legacy platforms, so engineers with migration or early AI-tool experience are the modernisers. Maintainers know the retail-bank systems they kept running from the inside. Ask what they migrated, what they decommissioned, and whether their team adopted AI coding tools.