Barclays Files Developers Under 'Support.' Keep That Off Your Resume

Barclays is cutting about 5,000 jobs by year-end, and it put software developers in the "support functions" bucket that takes most of the hit. If you write code or run production systems inside a bank, look at your resume. There's a good chance it uses the same cost-line language your employer just used to justify cutting you. Citi and Barclays alumni are about to apply to the same postings with resumes that sound almost exactly like yours.

What did Barclays actually cut, and who counts as "support"?

Barclays is cutting roughly 5,000 roles, about 5% of its 93,000 staff worldwide. About 60% of the second-half cuts fall in "support functions," and that group explicitly includes software developers. That works out to roughly 2,400 support roles out of the 4,000 still to go. The other 1,000 positions were already closed.

Some context the headline leaves out:

• The bank is profitable. Barclays posted £2.3bn in Q3 pre-tax profit and is aiming for more than £1.1bn in savings by 2027.
• The CFO credits AI. Anna Cross said the cuts come as "AI makes our people more productive." CNBC's paraphrase is that the bank sees fewer developer roles ahead.
• The CEO plays AI down. C.S. Venkatakrishnan called AI "the icing on the cake, not the cake." He said the cuts close out a three-year cost-cutting program.
• Geography matters. The cuts center on the UK retail bank, but a significant share is expected in India, where some UK back-office work is done.

Barclays isn't the only bank doing this. Citi plans to eliminate 20,000 roles by the end of 2026. Standard Chartered plans to cut corporate-function jobs by more than 15% by 2030, from a base of 52,271 back-office staff. HSBC is reviewing a plan that could affect nearly 20,000 roles, with non-client-facing global service centers taking the brunt. Using Reuters' tracker, FourWeekMBA counted 39,920 AI-linked cuts across HSBC, Standard Chartered, Barclays, Mizuho, SEB, Danske Bank and DNB. That's about 39% of the total.

A "support function" is an accounting category. It describes how the bank books your salary, not what you do. The mistake is copying that label onto your own resume.

Why does a "support" title hurt you in the job market?

Very few people in UK finance tech carry a support title, so it stands out to recruiters as something to screen out. In Refolk's index of professional profiles, 9,777 people in UK banking and financial services hold Software Engineer or Software Developer titles. Only 484 hold Application Support or Production Support titles.

Here is how the talent pools compare:

Here's why it matters. When a recruiter at a fintech searches for "software engineer" plus "payments," the 9,777 come up and the 484 mostly don't. When the same recruiter sees "Application Support Analyst" at the top of a resume, they read it the same way the bank's finance team does: as work that keeps the lights on and can be automated or moved offshore. The title tells them how to think about you before they reach your first bullet.

A lot of support-titled work is real engineering, like writing automation, owning deployment pipelines, and debugging trading systems at 3 a.m. The title just hides it.

Why are ticket counts the wrong thing to brag about now?

The numbers most bank tech resumes lead with (tickets closed, incidents handled, PRs reviewed) measure exactly the throughput banks now say AI can absorb. Jane Fraser has said AI-assisted code reviews freed up 100,000 hours of capacity per week on Citi's engineering team.

If your best bullet is "Reviewed 40+ pull requests per sprint" or "Resolved 1,200 L2 tickets," you've written down the work the bank just told investors a machine does. Volume used to show you were diligent. Now it shows you were doing something that can be automated.

Fraser's memo works as a resume brief: "We are not graded on effort. We are judged on our results." Volume describes effort. Results are what the effort protected or produced.

How do you rewrite a cost-center bullet into a business outcome?

Rewrite every bullet so it names what the work protected or produced: revenue, regulatory risk avoided, or customer experience improved. Keep the technical detail as evidence for that outcome, but don't make it the headline.

A cost center is a team the company tracks only by what it spends, not by what it earns. If you work in one, you have to make the earnings connection yourself, because nobody inside the bank ever wrote it down.

The three-question rewrite

Run every bullet through these three questions:

1. What would have broken if I hadn't done this? A payment rail, a regulatory submission, a customer journey, a trading desk's morning.
2. Who outside my team noticed? Customers, traders, compliance, the regulator, an auditor.
3. What number describes that outcome? Transaction volume, uptime on a revenue system, onboarding time, audit findings closed, losses avoided. Use a real figure you can defend in an interview. If you don't have one, name the scale ("the bank's UK card authorization path") rather than inventing a figure.

Before and after

Fill the brackets with your own numbers. If you can't, the bullet isn't ready yet.

Words to retire

• "Supported": say what you kept running and for whom.
• "Maintained": say what you changed while maintaining it.
• "BAU": nobody outside a bank knows what business-as-usual means, and inside one it means "cost."
• "Assisted with": name your part, or cut the bullet.
• Internal system codenames: say what the system does and how much depends on it. Nobody outside your bank knows the acronym, and an applicant tracking system won't match it to anything. Where the work touched FCA reporting or Consumer Duty, name that instead.

Doing this for 15 bullets, and then again for every posting, is slow. That's the work Refolk does for you. It writes your resume from your actual history, then rewrites it for each posting you paste in, leading with the outcome that posting cares about, so a payments-reliability bullet reads differently for Moneybox than for a trading-tech role.

Can you retitle "Application Support" without lying?

Yes, if the new title describes the function you actually performed and your bullets back it up. "Software Engineer, Payments Reliability" is fair for someone who writes code to keep payment systems running. It isn't fair for someone who only routes tickets.

The payoff is moving out of a group of 484 support-titled profiles in UK finance and into the 9,777-strong engineering pool recruiters actually search. Some guardrails:

• Keep the official title somewhere. Use a functional title as the headline and put the HR title in parentheses or on a second line, e.g. "Payments Reliability Engineer (title: Application Support Analyst)." Background checks will see the HR title, so don't hide it.
• Match the title to your bullets. If you call yourself an engineer, at least half your bullets should show building, automating, or changing systems.
• Pick the market's word. Site reliability engineer, production engineer, and platform engineer describe the function in engineering terms. "Production support" describes it in the bank's cost terms.

This is where many resumes after a bank layoff go wrong in one direction or the other. Some keep the HR title and get filtered out. Others inflate to "Senior Software Engineer" with no code in the bullets and fall apart in the first technical screen.

Who will you be competing with for the same jobs?

You'll be competing with a large group of displaced bank technologists, many from Citi, clustered in a few cities, plus a much larger offshore engineering pool for any remote role. To stand out, your bullets need to be specific and quantified.

Refolk's index gives a directional read on where that competition is. In a 25-profile sample of UK support-titled people, 12 work at Citi and 9 are in Belfast or the Belfast metro area. Bank of America (3) and JPMorganChase (2) come next. It's a small sample, so treat it as a signal rather than a census. Still, if you're in Belfast, assume the next Citi round will put several people with nearly your resume into the same local postings.

Offshoring makes the pool bigger. Barclays expects a significant share of its cuts in India, and Refolk's index counts 40,038 software engineers and developers in Indian banking and financial services, about 4.1x the UK pool. Any fintech job open to remote applicants worldwide draws from that larger group.

What UK applicants can offer that's harder to copy:

• UK regulatory context. FCA rules and Consumer Duty are concrete knowledge areas, not soft skills.
• Proximity to revenue. Fintechs such as Moneybox, Capital on Tap and Neverless already employ UK finance engineers, according to Refolk's index. Pitch them product impact, not ticket throughput.
• Ownership stories. "I owned X end to end" is harder to commoditize than "I was one of 40 on the L2 rota."

Should you lead with AI skills?

No. Barclays is cutting while it makes a profit, so a line about being proficient in Copilot doesn't put you on the profitable side of the ledger. Bullets about revenue and risk outcomes do.

Barclays made £2.3bn in a single quarter. Its CEO called AI "icing." Will Howlett, an analyst at Quilter Cheviot, said "we are increasingly reaching the point where that investment translates into fewer people being required." Bill Winters at Standard Chartered talked about "replacing lower-value human capital with financial and investment capital." These are margin decisions. Being able to use the tools that replaced your colleagues isn't a reason to hire you.

Show AI use as a method inside a result. "Used an LLM-based triage script to cut mean time to resolve on the card-dispute queue by [X]%" works. Putting "AI tools" in your skills list does nothing for you.

FAQ

Is it really 60% of 5,000 Barclays jobs in support functions?

Not quite. Reporting says roughly 60% of the second-half cuts fall in support functions, including software developers. About 4,000 roles are still to go after 1,000 already closed, so the support share is around 2,400 roles. Applying 60% to the full 5,000 overstates it.

Can I change "Application Support Analyst" to "Software Engineer" on my resume?

Only if your work was engineering. Use a functional title like "Payments Reliability Engineer" with your official HR title shown alongside it, and make sure most of your bullets show building or automating systems. Background checks will see your HR title, so leave it visible.

Where are fintech jobs after bank layoffs most likely to come from?

UK fintechs are one obvious place to look. Refolk's index shows Moneybox, Capital on Tap and Neverless among the employers of UK finance engineers. Expect heavy competition for remote roles, since India's banking engineer pool is about 4x the UK's. To stand out, lead with UK regulatory knowledge and revenue-adjacent outcomes.