Lloyds Banking Group Software Engineer interview experience

No offer

Easy

Negative

Bristol, EnglandPosted Nov 2025 · Candidate report, summarized by Dataford

My interview started with the impression that I’d get a split format: React questions first, then a backend JavaScript coding portion.

When it actually ran, the structure didn’t match what I’d been told. Instead of separate sections, it turned into five React questions with a very short time limit for each answer.

The backend portion was also different from the way it was described—rather than a tailored backend task, it ended up feeling like standard LeetCode-style problems. That combination made it feel rushed and fragmented, where the main risk was not just the difficulty but the tight pacing.

Overall the experience wasn’t what I expected from the description, and the end result was rejection. I left feeling like the

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Lloyds Banking Group Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Lloyds Banking Group interview guidesEvery role we cover at this company