Barclays interview process (2026)
Round-by-round breakdown of the Barclays software engineering interview across 3 levels and 13 rounds: what each round covers, what interviewers evaluate, sample questions, and preparation tips.
Graduate Analyst (BA3) — Campus
Difficulty: Medium · Timeline: ~2-4 weeks (campus drive) · Recommended prep: 6-8 weeks
-
Round 0: Online Assessment (HackerEarth)
Assessment · ~90 min · difficulty 2/5 · elimination round
Focus: Java/C++/Python MCQs, OOPS, DBMS, SQL query writing, 1-2 coding problems
Barclays runs its campus OA on HackerEarth: roughly 90 minutes with two sections. Section 1 is 12-30 technical MCQs (+4/+6 marking) spanning Java, C++, SQL, error/exception handling, OOPS and DBMS. Section 2 has 1-2 coding problems (often string manipulation) and in recent drives a written SQL query question (e.g. filter customers by month from a yy-mm-dd date column and sort ascending). Shortlist ratios are tight — one 2024 drive took 48 of a much larger pool to interviews and made 10 offers.
What they evaluate: Breadth across CS fundamentals plus the ability to finish easy-medium coding problems quickly. MCQ accuracy matters because of negative/weighted marking.
Sample question: Given a string S of lowercase letters, build a new string where the character at 1-based position i is shifted forward in the alphabet by i (wrapping z back to a). Print the generated string. Example: "abcz" -> "bdfd".
Tips: Revise Java + OOPS MCQ banks (GFG company-wise) and practice writing raw SQL by hand — the SQL question is asked as a written query, not multiple choice. Do not leave the coding question for the end; it carries the most marks.
-
Round 1: Technical Interview — DSA + CS fundamentals
Onsite · ~45-60 min · difficulty 3/5
Focus: DSA (strings, sorting, arrays), OOPS pillars, dynamic method dispatch, DBMS, projects
Face-to-face (or virtual) round, frequently taken by a senior engineer or VP from the Pune/Chennai technology centre. Expect 1-2 DSA problems solved on paper or a shared doc — LeetCode easy-medium, with a bias to strings and sorting variants — plus rapid-fire CS fundamentals: the four OOPS pillars with real examples, dynamic method dispatch, access modifiers, HashMap vs Hashtable, and basic SQL joins. Your resume projects get a genuine deep dive: architecture, your exact contribution, and why you chose the stack.
What they evaluate: Clean working code on easy-medium problems, articulate OOPS/DBMS fundamentals, and honest, detailed ownership of resume projects.
Sample question: Given a sentence, return the longest word in it (first one if there is a tie). Follow-up: do it in a single pass without splitting the string into an array first.
Tips: Practice explaining code aloud while writing on paper — no IDE crutch here. Know every line of your resume; Barclays interviewers probe project claims harder than algorithms.
-
Round 2: Techno-HR round with a VP
Onsite · ~45-50 min · difficulty 2/5
Focus: Project deep dive, cloud basics (AWS, service models), light coding, situational questions
Signature Barclays campus round: a single VP (often 7+ years in the bank) runs a combined technical + HR conversation. Typical flow — introduction, project walkthrough with functionality questions, one small coding task (e.g. longest word in a sentence), cloud computing basics (AWS, IaaS/PaaS/SaaS), then situational questions on teamwork and time management. Campus folklore that holds up in reports: if this round crosses ~30 minutes, you are being seriously considered.
What they evaluate: Whether you can hold a 45-minute conversation with a senior banker-technologist: clarity, composure, genuine interest in fintech, and consistency between your resume and your answers.
Tips: Prepare a crisp 2-minute project narrative with one failure/learning story. Read up on how banks use cloud and why Barclays runs technology out of Pune — interviewers like candidates who know what Barclays Technology Centre India actually builds.
-
Round 3: HR + RISES values discussion
Behavioral · ~20-30 min · difficulty 1/5
Focus: RISES values (Respect, Integrity, Service, Excellence, Stewardship), relocation, offer fit
Short closing conversation, sometimes merged into the VP round. Questions map directly to the Barclays RISES values — Respect, Integrity, Service, Excellence, Stewardship — plus practicalities: willingness to relocate to Pune (primary) or Chennai, shift comfort, and why banking technology over a product company.
What they evaluate: Values alignment and commitment. Answers are expected to reference concrete incidents, not adjectives.
Tips: Memorise RISES and prepare one real story per value. A specific answer to "why Barclays over a startup" — stability, scale of payment systems, global codebases — lands well.
Software Engineer (BA4) — Lateral
Difficulty: Medium · Timeline: ~3-5 weeks · Recommended prep: 4-6 weeks · Cooldown: ~6 months
-
Round 0: Recruiter screen
Phone · ~20 min
Focus: Experience summary, current stack, notice period, grade mapping, compensation range
Short call from Barclays talent acquisition (or a partner agency) for Pune/Chennai openings. Covers your Java/tech stack, years of experience, current CTC and notice period, and which grade (BA4 vs AVP) the requisition maps to. Barclays moves fast for laterals — end-to-end averages under a month, and interview slots are often on weekends.
What they evaluate: Basic fit for the requisition: stack match (usually Java/Spring in Pune), notice period, and compensation alignment.
Tips: Ask which team and grade the role maps to up front — BA4 vs AVP changes both interview depth and pay band. Keep your notice-period answer precise.
-
Round 1: Technical Round 1 — Core Java + DSA
Onsite · ~60 min · difficulty 3/5 · elimination round
Focus: Core Java, collections, HashMap internals, multithreading, design patterns, DSA (strings, arrays)
The make-or-break lateral round, usually with an AVP from a sister team. Reported staples: implement Singleton and discuss how it can be broken (reflection/serialization), HashMap internals and the Java 8 treeification change, immutability, collections framework trade-offs, exception handling, and multithreading basics. Alongside the Java grilling you get 1-2 DSA problems around LeetCode easy-medium — Fibonacci, palindromes, and medium string questions written on paper or a shared editor.
What they evaluate: Depth in core Java rather than framework name-dropping: can you explain what the JVM and collections actually do under the hood, and still write clean working code under observation.
Sample question: Given a string, find the length of the longest substring without repeating characters. Example: "abcabcbb" -> 3 ("abc"). Explain the sliding-window invariant before coding.
Tips: Prepare core Java thoroughly: OOPS, Collections, Multithreading, Exception Handling and Java 8 features come up in nearly every Barclays lateral report. Practice medium string problems on paper.
-
Round 2: Technical Round 2 — Spring Boot + service design
Onsite · ~60 min · difficulty 3/5
Focus: Spring Boot internals, JPA, REST/RAML, SQL/DBMS, low-level design of a service, current project
Techno-managerial round, often with the team's AVP or VP. Reported topics: Spring Boot annotations and what happens behind @SpringBootApplication, JPA repository implementation, REST contract design (RAML has come up), transaction handling, SQL tuning, and a low-level design discussion of a service you would build — e.g. sketch the classes and API for a funds-transfer or reconciliation component. Your current project is dissected: architecture, failure handling, and what you personally shipped.
What they evaluate: Whether you can own a Java microservice in a regulated bank: sound API/persistence design, defensive error handling, and honest depth on your production experience.
Sample question: Design the classes and REST API for a simple funds-transfer service: idempotent transfer endpoint, balance check, audit trail. Walk through what happens if the debit succeeds and the credit fails.
Tips: Rehearse one end-to-end story of a production incident you handled — banks probe failure handling hard. Be ready to defend every framework choice with a trade-off, not a preference.
-
Round 3: Hiring manager round (VP)
Behavioral · ~45 min · difficulty 2/5
Focus: Past projects, situational questions, RISES values and mindset, team fit
Round with the hiring VP, sometimes joined by the team's Director. Mostly behavioral: previous projects and work experience, situational questions (conflicting priorities, pushing back on a bad requirement), and the Barclays values-and-mindset framework. Barclays tells candidates in advance which 3-5 competencies they will be assessed against — expect questions mapped to those.
What they evaluate: Consistency of your experience story, ownership under ambiguity, and alignment with the assessed competencies and RISES values.
Tips: If the recruiter shared your assessed competencies, prepare one STAR story per competency. Ask concrete questions about the team's book of work — VPs read that as genuine intent.
-
Round 4: HR + fitment discussion
Other · ~30 min
Focus: Compensation, grade fitment (BA4), notice period, background checks
Closing call with HR: compensation negotiation against the BA4 band, joining date vs notice period, and initiation of background verification (banks are strict — employment history, education, and references are all checked). Reports describe this round as light on technical content.
What they evaluate: Salary alignment inside the grade band and a clean background check.
Tips: Negotiate on the grade first, then the number — a BA4 vs AVP fitment moves the whole band. Have payslips and relieving letters ready; BGV at Barclays is thorough.
AVP — Software Engineering
Difficulty: Medium · Timeline: ~2-4 weeks · Recommended prep: 4-6 weeks · Cooldown: ~6-12 months
-
Round 0: Recruiter + hiring team screen
Phone · ~30 min · difficulty 1/5
Focus: Leadership scope, tech stack depth, team context, compensation band
Screening call for AVP requisitions in Pune or Chennai. Beyond the usual stack/notice/CTC checks, expect questions on the size of systems and people you have influenced — AVP at Barclays India is a senior-engineer/lead grade (often 8-12+ years). Glassdoor data shows AVP loops move quickly, averaging under two weeks from application to decision.
What they evaluate: Whether your seniority genuinely maps to the AVP grade: system scale, mentoring, and delivery ownership.
Tips: Quantify scale early: transactions per day, team size, systems owned. AVP screens filter hard on genuine seniority rather than years alone.
-
Round 1: Technical deep dive with AVP panel
Onsite · ~60 min · difficulty 4/5 · elimination round
Focus: Advanced Java/JVM, concurrency, performance tuning, DSA, past architecture decisions
Technical round taken by one or two AVPs from an adjacent team in the same group. Content skews to depth over breadth: JVM memory model and GC tuning, java.util.concurrent and real concurrency bugs you have fixed, design-pattern trade-offs in code you actually shipped, plus a medium DSA problem to confirm hands-on coding has not rusted. Data-heavy teams add SQL tuning and messaging (Kafka/MQ) questions.
What they evaluate: Hands-on depth expected of a senior engineer: you must still code, and you must explain the why behind past architecture and tuning decisions in production systems.
Sample question: Your service's p99 latency doubled after a JVM upgrade with no code change. Walk through how you would diagnose it — GC logs, safepoints, JIT warmup — and what evidence would distinguish each cause.
Tips: Bring war stories with numbers: an OOM you root-caused, a lock you removed, a query you tuned. Panels at this level distrust generic answers instantly.
-
Round 2: System design round
System_design · ~60 min · difficulty 4/5
Focus: HLD for banking-scale systems: payments, reconciliation, resilience, idempotency, compliance
Whiteboard/virtual HLD round for AVP candidates. Prompts are banking-flavoured: design a payment-processing pipeline, a real-time fraud-check hop in a transfer flow, or an end-of-day reconciliation system. Non-negotiables the panel listens for: idempotency and exactly-once effects on money movement, audit trails, graceful degradation when a downstream (e.g. a core banking host) is slow, and data-residency/regulatory constraints a UK bank operates under.
What they evaluate: Structured HLD ability plus banking judgement: correctness of money movement over raw throughput, and clear failure-mode reasoning.
Sample question: Design a UPI-style instant payment flow for a bank: validation, debit/credit legs across two banks, timeout and reversal handling, and an audit trail that a regulator can replay. Where do you place idempotency keys and why?
Tips: Lead with the consistency story — reviewers at a bank care more about "no money lost or duplicated" than about serving a billion QPS. Name your reconciliation strategy explicitly.
-
Round 3: VP hiring manager + Director — values & mindset
Behavioral · ~45-60 min · difficulty 2/5
Focus: Barclays competency framework (AVP-VP), RISES values, stakeholder management, delivery leadership
Final round with the hiring VP and often the Director of the team. Reported as mostly behavioral: previous projects, situational questions, stakeholder and delivery stories, mapped to the published Barclays AVP-VP competency framework. You are told before the interview which 3-5 competencies you will be assessed against. Expect probing on leading without authority, handling audit/regulatory pressure, and developing junior engineers.
What they evaluate: Leadership behaviours at the AVP grade: judgement, stewardship of systems and people, and evidence-backed answers against the named competencies.
Tips: Download the Barclays AVP-VP competency PDF and prepare one STAR story per competency the recruiter names. Directors here probe the "what would you do differently" follow-up hardest.
Other companies' interview processes
Worked sample solutions (code, design diagrams, and STAR answers) for every round are available in the FAANGPlus app: open interview processes.