Barclays Software Engineer candidates commonly report an online assessment, a resume-driven technical interview, and an HR or values conversation. Prepare project deep-dives, SQL, OOP, Java and STAR stories.
$120K
Avg. Base Comp
$140K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Barclays Software Engineer interview as a broad screen, not a pure algorithm contest. Several reports begin with an online assessment that mixes MCQs, aptitude or behavioral items, and easy-to-medium coding problems. Several people say the technical interview was built around the projects on your resume, with follow-ups on what you built, why you stopped where you did and how you would extend it.
Fundamentals come up repeatedly. Candidates mention SQL and database basics, OOP, core Java topics such as collections, threading and queues, Spring annotations, and data structures such as arrays, linked lists and hash maps, including how a hash map works under the hood. One experienced candidate was asked about microservices and JVM memory, and one interview included a dynamic programming problem with a time and space complexity discussion. Another candidate felt the Java questions leaned toward syntax and framework recall rather than design discussion, so the exact format likely varies by team, level and location.
Behavioral and values questions carry real weight. Reports describe STAR-style prompts about risk, initiative, leadership and conflict, later rounds with higher management, and a separate values and culture fit conversation. Outcomes are mixed, with both offers and rejections, so preparing only for coding is risky. Rehearse two or three project stories in detail, refresh SQL and OOP basics, and practice explaining time and space complexity aloud. Role-specific stacks, such as frontend or mobile work, may change the technical mix.
Synthesized from 60 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Barclays process.
The online assessment came first, and it was the part that felt most predictable. After that I had two interviews back-to-back, each about 45 minutes long. I went in expecting a mix of coding and general technical questions, but most of both rounds were technical deep dives built directly from my resume. The interviewer picked projects and roles I had listed and started pulling on them: why I made certain design choices, what I would change looking back, and how the pieces actually worked together. Once they had that context, they would build a hypothetical situation around the same work and ask how I would handle it. It felt less like a quiz and more like a conversation that kept getting more specific.
The structure was loose. I never got a clear sense of what each round was meant to cover, and the transitions between topics felt improvised. Mixed in with the deep dives were some small fundamental questions that caught me off guard because they were so basic compared to everything else. The gap between the heavy discussion of my own work and those simple checks made the whole process feel uneven.
I did not get an offer. The main lesson I took away is that a resume is a set of claims that will be tested. Going in, you should be able to explain every project in detail, including the tradeoffs and what you would do differently, and you should also be comfortable with the basics you might assume are too simple to come up.
Prep tip from this candidate
Be ready to defend every project on your resume in depth, since the interviews were built around deep dives into it followed by hypothetical scenarios about the same work. Also brush up on basic fundamentals, because simple questions came up alongside the harder discussion.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Barclays
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Find the Missing Number | |
| Bagging vs Boosting | |
| Attribution Rules | |
| Sort Strings | |
| CNNs vs Intensity-Based Features | |
| Priority Queue Using Linked List | |
| Prime Numbers Identification | |
| String Palindromes | |
| Blob Indexing | |
| Impossibly Iterative Fibonacci | |
| Safe Deployments | |
| Why Do You Want to Work With Us | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| Dropbox Database | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Maximum Profit | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment before the live interviews. It typically mixes CS-fundamentals MCQs, such as databases, OOP and networking, with aptitude or behavioral items and a few easy-to-medium coding problems.
Candidates describe a technical round led by resume and project questions. Reported topics include arrays and linked lists, hash maps, SQL and database basics, OOP, and Java or Spring fundamentals. You may be asked to code a modest problem and explain its time and space complexity. Difficulty is usually described as approachable but broad.
Several candidates report a behavioral discussion, sometimes combined with technical questions or held with a manager or senior team member. Reported themes include risk, initiative, leadership, conflict and process improvement. Prepare STAR examples with concrete outcomes, since the emphasis can be on structured storytelling more than technical depth.
Candidates report an HR segment or a values and culture fit conversation, sometimes combined with technical questions. Reported prompts include how you resolve conflicts and where you see yourself in five years. Expect to connect your experience to the team's values. Whether this is a separate round varies across reports.
