Barclays Software Engineer interview typically runs 2-3 rounds: online assessment, technical interview, HR/behavioral round. It usually takes about 1-2 weeks and is fairly structured, with resume-driven discussion.
$125K
Avg. Base Comp
$158K
Avg. Total Comp
3-4
Typical Rounds
2-4 weeks
Process Length
Our candidates consistently describe Barclays as a process that values practical engineering fluency over flashy algorithm performance. Across experiences, the strongest signal is comfort with the basics: SQL, databases, OOP, Java, and core backend concepts like HashMap internals, JVM memory, indexes, and threading. Even when coding appears, it tends to stay approachable and grounded in everyday implementation choices — filtering strings, simple sorting, queue variants, or other problems where the interviewer can quickly see how you think.
A recurring theme is that Barclays leans heavily on resume-backed discussion. Multiple candidates reported being pressed on projects they had actually built, why they stopped at a certain stage, how they would extend them, and how they would apply that work in a real environment. That means the bar is not just “can you answer the question,” but “can you explain your engineering decisions clearly and connect them to production reality.” We also see a noticeable emphasis on design judgment: SOLID principles, design patterns, SQL vs. NoSQL tradeoffs, and when a database choice or data structure makes sense.
The non-obvious make-or-break factor is that Barclays often mixes technical depth with behavioral judgment in the same conversation. Our candidates report questions about conflict, leadership, risk, initiative, and how they handle challenges, alongside technical follow-ups. The people who do best sound grounded, specific, and calm — not over-rehearsed. In other words, Barclays seems to reward candidates who can show they build thoughtfully, explain tradeoffs well, and understand how software fits into a real business context.
Synthetized from 7 candidates 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 process was pretty straightforward and felt more supportive than stressful. I first went through an online test that had a mix of MCQs and a coding section. The MCQs covered a broad spread of basics like Python, C++, Java, SQL, MongoDB, database queries, OOP, and even computer networks and security. After that, there were two coding questions that were easy to medium in difficulty, so it didn’t feel like a heavy LeetCode-style screen.
The interview round was on Microsoft Teams and lasted about 30 minutes. It started with a quick introduction, then moved into technical questions and a bit of behavioral discussion. I was asked about circular queues and the different ways to implement them, along with core Java topics like collections, threading, and types of queues. There was also a dynamic programming problem, and they wanted me to talk through time and space complexity. On the behavioral side, I was asked how I resolve conflicts and where I see myself in five years. Another round focused more on leadership, and one interviewer also asked about core C/C++ concepts, project experience, and how I’d apply what I’d built in real-world scenarios. One thing that stood out was that the coding tasks were practical rather than tricky, like filtering brackets inside a string or writing simple logic on a notepad. Overall, the process was smooth, well conducted, and in my case the result came the same day. My main takeaway is to be comfortable with Java basics, queues, OOP, and explaining your projects clearly, because the questions were more about fundamentals and practical thinking than obscure algorithms.
Prep tip from this candidate
Brush up on circular queues and the different ways to implement them, plus core Java topics like collections, threading, and queue types. Also be ready to explain a dynamic programming solution with time and space complexity, and to talk through your project experience and conflict-resolution examples clearly.
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 | |
| Priority Queue Using Linked List | |
| String Palindromes | |
| Impossibly Iterative Fibonacci | |
| Blob Indexing | |
| 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 | |
| Rolling Bank Transactions | |
| String Shift | |
| Comments Histogram | |
| Prime to N | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Cumulative Distribution |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically start with an online assessment that combines coding with fundamentals. Across experiences, this stage included MCQs on Python, Java, C++, SQL, MongoDB, OOP, databases, computer networks, and security, plus 1-2 easy to medium coding questions and sometimes aptitude or behavioral-style questions.
The first live round is usually a technical screen over Microsoft Teams or similar video call. Interviewers focus on core backend and CS fundamentals such as Java, Spring, queues, HashMap, JVM memory, SQL, databases, OOP, DSA basics, and resume/project discussion, often with practical coding or problem-solving follow-ups.
Later rounds often mix behavioral questions with technical depth. Candidates were asked about conflict resolution, leadership, initiative, risk handling, and future goals, while still being tested on topics like database indexes, SQL vs NoSQL, SOLID principles, design patterns, and explaining past project decisions.
Some candidates had a final conversation with higher management or a senior interviewer. This round leaned heavily on resume-based discussion, practical engineering judgment, and behavioral fit, with occasional coding or logic questions and broader questions about how the candidate would apply their work in real-world scenarios.