How to Crack Capital One: The Software Engineer Interview, From Real Experiences
Prepare for Capital One software engineer interviews with reported assessment patterns, interview questions, and preparation advice.
On this page
Last reviewed November 16, 2026.
For software engineers at every level.
Built by the Codinzhub team from Capital One interview experiences that candidates shared, including the ones posted on Codinzhub. Each experience is one person's interview, and Capital One changes its process by team and level, so use this as a map, not a promise.
The 30-second version. Apply on the careers site or through a recruiter, take a 70-minute CodeSignal OA with four questions (two easy, two medium and long), then a Power Day of four one-hour rounds: a technical case, a coding round (a business-logic class such as a banking system, not a puzzle), system design (banking and credit cards) and behavioral. New grads (TDP) get a three-round Power Day with an agentic coding round where an AI assistant is allowed. Decisions are fast: some candidates heard the same afternoon.
Guides by level: New grad, TDP and campus · Senior and lead engineers
Round-by-round breakdown
Stage 1: Application, where candidates applied
How it works. Most US candidates applied on the careers site or were contacted by a recruiter. One lead engineer said applications through job boards got almost no answers; applying on Capital One's own site with a resume tailored to the job description is what brought calls. In India, Capital One hires through campus drives; 2026 drives in these experiences include IIT Bombay, IIT Kharagpur, IIT Delhi and IIT (BHU) Varanasi.
Stage 2: Shortlisting, how candidates moved forward
How it works. Usually a short recruiter call about your background, the team, the office location and pay, with no technical questions. Some candidates got the OA with no recruiter call at all. The OA link usually gives you one to two weeks to finish it. Capital One also sends prep material before the Power Day, and some recruiters held a prep call to answer questions about the format.
Stage 3: Online assessment
At a glance
- Length: about 70 minutes on CodeSignal, with camera, microphone and an ID check
- Questions per round: 4 (two short and easy, two long and medium)
- What was asked: simulation, matrix operations, multi-source BFS, hash maps, subarray tricks, string parsing
- Most common: a rotting-oranges grid over a given number of days; matrix commands (reverse a row, swap rows, rotate); the moon-phase calendar
How it works. The first two questions take about 25 minutes; the last two are long, wordy problems that are mostly careful logic rather than clever algorithms. One candidate advised doing them in the order 1, 2, 4, 3, because question 3 is often the slowest; getting full marks on one of the last two beats half marks on both. CodeSignal now has hidden tests, so you must find bugs by reading your own code. You may look up syntax in official docs but not solutions. Have a clear PNG of your ID ready: one candidate's ID check took ages, and PDF is not accepted. Passing three of four questions was enough to reach the Power Day for one SWE1 candidate.
OA questions candidates reported:
| Question (our summary) | What it tests | Position |
|---|---|---|
| Count elements greater and smaller than a target; say which side wins | Counting | Q1 |
| Count case-insensitive triplets whose first and third letters match | Strings | Q1 |
| How many numbers in an array are a power of k (watch k = 1) | Maths edge cases | Q1 |
| Rank teams by points, then goal difference, then goals; return the top two | Custom sorting | Q1 |
| Moon phase on a given date when phases repeat every 8 days | Date arithmetic | Q2 |
| Count three-digit numbers in a range with no repeated digit | Brute force | Q2 |
| Count subarrays matching an up, equal, down pattern | Pattern matching | Q2 |
| Apply commands to a matrix: reverse a row, swap rows, rotate | Simulation | Q3 |
| A grid where rotten cells spread each day; return the grid after k days | Multi-source BFS | Q3 |
| Place Tetris-like shapes into a grid at the first top-left spot that fits | Careful simulation | Q3 |
| Text justification where each group of words starts a new line | String formatting | Q3 |
| Allocate and free memory blocks by ID | Simulation | Q3 |
| Count pairs whose concatenation equals a target number | Hash map | Q4 |
| Running length of the longest consecutive run seen so far | Union-find or hash map | Q4 |
| Largest value of a valid plus-minus expression on a right-and-down path in a grid | Grid DP | Q4 |
| Pairs that become equal with at most two digit swaps | Digit counting | Q4 |
| Count pairs of points within distance 2 on both axes | Hashing by cell | Q4 |
Capital One OA questions shared on Codinzhub:
| Question | Drive | Topic |
|---|---|---|
| Digit Operations to Make Two Integers Equal | IIT Bombay | Shortest paths |
| Longest Subarray With Absolute Diff Within a Limit | IIT Bombay | Sliding window |
| Erect the Fence | IIT Bombay | Geometry |
| Minimum Cost for Conversion of Start to Target | IIT Bombay | Graphs |
| Best Shift Total Within a Limit | IIT Kharagpur | Arrays |
| Ashgrove Postal Depot Punctuality Bonus Run | IIT Kharagpur | Simulation |
| GCD Pair | IIT Kharagpur | Number theory |
| Maximum Profit with Deadlines and Bonus | IIT Kharagpur | Greedy |
| Maximum Points Earned | IIT Kharagpur | DP |
| KGCD: Count Pairs with a Given GCD | IIT Kharagpur | Number theory |
| Optimal Paths | IIT Kharagpur | Grid DP |
| Maximum Review Buffer | IIT Kharagpur | Scheduling |
| Minimum Distance to Reach All Targets in a Grid | IIT Delhi | BFS |
| Bitwise OR with K | IIT (BHU) Varanasi | Bits |
| Reach the Target | IIT (BHU) Varanasi | BFS |
More questions: Browse Capital One questions.
Stage 4: The Power Day
How it works. Four one-hour rounds, usually back to back on one morning. You can often pick a slot, and some candidates split the rounds over two days. A senior candidate said back-to-back rounds were draining and advised asking for a break. New grad (TDP) Power Days have three rounds: behavioral, case and agentic coding; see the new grad guide.
Technical case round
At a glance
- Length: about an hour
- Questions per round: 1 case in three parts
- What was asked: a real Capital One product, rules to apply by hand, then code to explain or debug
- Most common: the virtual card number case
How it works. Part one is open discussion: the benefits and challenges of the product for customers and for Capital One, then the technical challenges. Part two gives you rules (what each digit of a card or transaction number means, when a payment is valid) and a list of payments to judge out loud, one by one. Part three hands you code that implements those rules and asks you to debug it. The code is deliberately messy: one candidate found it using cardNumber % 2 to read the last digit. If time remains, the interviewer may ask how you would split the code into classes, such as parsing apart from validation. Several candidates called this the hardest round to prepare for.
Questions candidates reported:
| Question (our summary) | What the interviewer focused on |
|---|---|
| Virtual card numbers: pros and cons, judge payments by digit rules, debug the validator | && versus ` |
| Software practices, simple maths, then review code tied to the same theme | Structured reasoning; the code review part was the hardest |
| A real Capital One problem: explain given code, simple maths, write basic logic | Thinking out loud |
Coding round
At a glance
- Length: about an hour
- Questions per round: 1 problem in three or four growing parts
- What was asked: an object-oriented class with business rules
- Most common: the banking system
How it works. Not a typical puzzle. You build a class, and new requirements arrive as you finish each part. The interviewer gives test inputs as arrays of strings, and you must write your own test harness to run them; two candidates said this took longer than the class itself. One interviewer cared more about the thought process and edge cases than about finishing.
Questions candidates reported:
| Question (our summary) | Follow-up reported |
|---|---|
| Banking system: create account and deposit | Transfers between accounts; top N accounts by activity (ask whether activity means count or amount) |
| A bank account class with deposit, transfer and withdraw | Edge cases like overdrafts |
| Parse transaction data and sort by date, company or cashback offer | Time and space complexity |
| A business-logic method that keeps getting new requirements | Keep earlier behaviour working |
More questions: Browse Capital One questions.
System design round
At a glance
- Length: about an hour
- Questions per round: 1 design with a detailed list of requirements
- What was asked: banking and credit card systems on AWS
- Most common: a credit card platform
How it works. The prompt often comes with about five functional requirements already written out, not a one-line question. Topics stay within banking and cards, so one senior candidate said there is less ground to cover than at a big tech company. Interviewers asked about AWS choices, such as EC2 versus Fargate, and about security.
Questions candidates reported:
| Question (our summary) | What the interviewer focused on |
|---|---|
| A credit card system: login, payment authorisation with fraud checks, monthly credit bureau reports, spending view, real-time credit limit increases | Breadth first, then one or two deep dives such as payment idempotency |
| A credit card application site: login, sign-up, apply | Scalability and AWS |
| A banking application: APIs, screens and database | Sketches and text, no code (SWE1) |
| A smart electric meter system for an apartment building | High-level design |
More questions: Browse Capital One questions.
Behavioral round
At a glance
- Length: about an hour
- Questions per round: 3 or 4, with deep follow-ups
- What was asked: learning, conflict, failure, strengths, AI at work
- Most common: STAR stories; how you use AI to work faster
Questions candidates reported:
- A time you had to learn something new quickly.
- A conflict with a teammate, and a time you challenged a manager or mentor.
- Your strengths and weaknesses.
- Why Capital One.
- How you use AI in your daily work, and how it makes you more productive.
One lead engineer answered the AI questions with examples like drafting API docs and test setup, and said to treat AI "like an intern" whose work you check.
More questions: Browse Capital One questions.
Stage 5: Decision and offer
How it works. Fast. One candidate whose last round ended at noon got a pass call at 1:30 the same afternoon. New grads then go through team matching. A lead engineer's search took about three months in total, and a senior candidate said recruiter feedback matched what the interviewer said in the room.
Capital One experiences shared on Codinzhub
| College | Role and result | What was asked |
|---|---|---|
| IIT Kharagpur | Software development, selected | Two OAs, the second with a short design question; a round on the OA solutions; CV grilling; HR |
Topics to prioritise
Across these experiences, the most common topics are matrix and grid simulation, multi-source BFS, hash maps, object-oriented class design, banking-domain system design and structured case reasoning. Several candidates said DFS and BFS beyond the grid problem rarely came up, and that the case round is the one people under-prepare for.
The Codinzhub Next-Round Playbook
What Capital One candidates who moved on did. Put together by the Codinzhub team from the Capital One experiences in this guide.
To get past the OA
- Time yourself on full four-question sets. One candidate did five or six timed sets in ten days and said it steadied them.
- Finish the two easy questions in about 25 minutes, then pick the long question you can fully solve.
- Try CodeSignal's practice test first so the hidden tests and the interface do not surprise you.
To get past the case round
- Go through the rules one at a time, out loud, in a fixed order.
- When debugging, check every boolean operator and every boundary first. Do not trust the given code.
To get past coding
- Practise the banking system end to end, including a small test runner that reads string arrays.
- Ask what each vague word means, like "activity", before you code it.
To get past system design
- Lay out entities, services and the main read and write paths before going deep.
- Ask the interviewer which area they want to explore; one candidate lost the round diving into payments first.
- Know caches, queues, load balancers, idempotent payments and the basic AWS compute options.
To get past behavioral
- Use real stories in STAR form; interviewers ask follow-ups that made-up stories cannot survive.
- Have two concrete examples of using AI in your work.
FAQ
Is the coding round a puzzle like other companies?
Usually not. It is a class with business rules that grows over three or four parts.
Can I use AI in the interview?
Only in the new grad agentic coding round, where it was allowed. Other rounds did not mention it.
Does Capital One ask hard algorithms?
Rarely. Candidates described the OA as long and wordy rather than tricky, and the Power Day as practical.
About this guide
This guide is researched and written by the Codinzhub team. We read every Capital One interview experience we could find, kept only what candidates actually described, and rewrote it in our own words. Questions are our own short summaries; the practice links point to similar problems, not the exact interview questions. Found something out of date? Share your own experience on Codinzhub and we will update the guide.
Keep track of what you’ve learned.