Capital One Interview Process & Rounds
Capital One's software engineering process in candidate reports starts with a CodeSignal online assessment of four tasks in 70 minutes, sometimes with a recruiter or hiring-manager call around it, and ends in a Power Day of four rounds for most experienced-hire loops: a case study, a coding round, system design and a behavioral round. In the reports that give timing, Power Day results came from the next day to about a week later, and candidates who passed went on to team matching. Where candidates struggled, it was mostly the case study, which several found hard to finish, and running out of time in the coding and system design rounds.
Part of the full catalog of Capital One interview questions, covering every round.
AceOffer is not affiliated with, endorsed by, or sponsored by Capital One. Questions are reconstructed from interview experiences candidates shared, not from Capital One materials.
Key facts
- •6 distinct round types
- •38 questions reconstructed from 108 candidate reports
- •Reports span Oct 2025 – Oct 2026
- •Refreshed monthly · last updated October 2026
The Capital One loop, from candidate reports
Capital One's software engineering process usually starts with a CodeSignal online assessment of four tasks in 70 minutes, mostly array, string and matrix problems. It is followed by a Power Day of several rounds. The coding round is most often a banking system class built in three parts that the interviewer gives one at a time, and candidates write their own harness to run the interviewer's test operations. The case study is the most widely reported round, appearing in SDE, Lead, ML Engineer, Applied Researcher and intern loops: it is about virtual credit card numbers and moves from a product discussion to applying validation rules and then debugging code. System design is most often a credit card system, sometimes a banking app. The behavioral round is a short behavioral round, and some loops add a hiring-manager chat. ML Engineer loops add ML technical rounds, Applied Researcher loops add a panel talk and research rounds, and some 2026 intern and TDP loops add an AI-assisted coding round.
Capital One interview timeline
| Step | Typical timing |
|---|---|
| Application to OA invitation | Same day to 3 days (2 reports); several candidates got the OA without speaking to anyone first |
| Time allowed to take the OA | 7 to 10 days from the invitation (3 reports), with email reminders in one |
| OA to result | A few days in the 3 reports that give it; some candidates heard nothing or had to chase the recruiter |
| To the Power Day | About two weeks from the OA to the invitation (1 report); about a month from application to Power Day for one senior candidate |
| Power Day to decision | Next day to 3 days (3 reports); one candidate was told to expect an answer about a week after |
| End to end | About 5 to 6 weeks from application to offer for one intern candidate (1 report) |
Few reports give dates, so treat these as rough. The only end-to-end report is an applied research intern loop that went from a late-August application to an offer in early October. The slow cases are mostly silence: one candidate had to remind the recruiter that they had finished the OA before anything moved, another scored full marks and heard nothing, and one candidate heard nothing after the Power Day and took it as a rejection. One staff candidate finished the OA and was told a week later that the role was no longer being filled.
The Capital One interview process, step by step
1. Online assessment
CodeSignal, four tasks in 70 minutes, taken on your own within a 7 to 10 day window, with camera, microphone and photo ID checks.
The same assessment shape appears across software engineer, senior, staff, new grad, data engineer, ML engineer, AI engineer and applied researcher reports. Candidates describe the first two tasks as easy warm-ups and the last two as longer medium-to-hard problems, mostly simulations on arrays, strings and matrices with long written statements. Scores are reported out of 600 in most reports that give one, though one candidate says 1,200. There is no clear cutoff in reports: candidates passed with 534 and with only the first two tasks finished, while others were rejected with 512, 540 and a full score. Several candidates got the link automatically after applying, others after a recruiter reached out, and one only after a coding interview.
- →Do the two easy tasks first, then consider the fourth before the third. Two candidates recommend this order, and a third notes that many people do the fourth before the third, which often eats the clock.
- →Watch for hidden-test timeouts on the harder tasks. Some task statements say an optimal solution is not required, but several candidates still timed out with nested loops on the later tasks.
- →Have a phone photo of your ID ready. One candidate's webcam photo of their driver's license was not recognized, and the ID check is outside the 70 minutes.
- →Expect full-screen sharing. One report says a single tab or window was not enough, and another says paste was blocked in the editor.
2. Recruiter or hiring-manager call (some loops)
Varies: a short recruiter screen, or a 30-minute hiring-manager conversation, before or after the OA.
Several reports go straight from the OA to the Power Day; one candidate answering a question says there was no phone screen in between. Others have a call: one applied researcher had a recruiter phone screen before the OA, and an applied research intern had an HR screen and then a hiring-manager round whose questions were emailed in advance. One experienced candidate had a 30-minute hiring-manager chat after the OA that covered a current project in detail and behavioral questions, and felt the manager judged the scope of their work too small. Some candidates were approached by a recruiter or an agency rather than applying.
- →Ask the recruiter for the Power Day preparation material or a prep call. Two candidates say Capital One provides one or both, and one says the hiring-manager round followed the questions sent in advance.
- →For a hiring-manager chat, prepare one project you can explain in depth, including its scope and your part in it.
3. Power Day: case study
One round; the most widely reported round, appearing in software engineer, Lead, ML engineer, applied researcher, AI engineer, TDP and intern loops.
The most reported case is about virtual credit card numbers and moves through three parts: the benefits and drawbacks of the product for customers and for Capital One, then applying a set of validation rules to transactions and judging each one aloud, then debugging code that implements those rules. Two candidates say the bugs are mostly in logical operators and boundary comparisons, and that the code they were given was messy. The rule details differ between reports. Two loops had a chatbot case instead; in one, it started with business questions, then asked the candidate to explain and improve code and say how they would add new requirements, without writing code.
- →Walk through the rules condition by condition, out loud. Two candidates say a structured explanation is the point of the second part.
- →Leave time for the debugging part. One candidate did not finish it, one Lead candidate ran out of time before the design discussion at the end, and one Senior Lead candidate believes the case is where they failed.
- →Read the rules you are given carefully rather than relying on a remembered version; thresholds and digit positions change between reports.
- →Practise reading unfamiliar code and predicting its output; intern and new grad case rounds lean on this.
4. Power Day: coding
One round on SDE, Senior and Lead loops; in the reports that describe it, the problem arrives in parts, one at a time.
Most reports describe a banking system class built in three parts: accounts and deposits, then transfers, then ranking accounts by activity, with some versions adding withdrawals. Candidates call the problem itself easy, but time is short: the parts arrive one at a time, and one candidate left some methods unwritten. The interviewer's test cases arrive as lists of string operations, and three candidates had to write their own harness to run them, which two say took longer than the class.
- →Ask how the last part defines activity before you code it. Two candidates flag this as the point to clarify.
- →Practise writing a small harness that parses string operations and prints results, so it does not eat into the hour.
- →Keep the class easy to extend, since each part builds on the last.
5. Power Day: system design
One round on SDE, Senior and Lead loops; two design rounds in one senior principal loop.
The most reported topic is a credit card system covering login, payment authorization with fraud checks, monthly credit bureau reporting, spending summaries and real-time credit limit decisions. Others are an online banking app with third-party payments, fraud detection and authentication, and, for a senior principal, a highly reliable account balance system and a cross-region event processing platform. Deep-dive questions in reports include a reasonable latency for payment authorization and how to reach it, how to store sensitive personal data, payment idempotency, choosing between EC2 and Fargate, and why to use a queue.
- →Go broad first: entities, services and the main read and write paths, then ask the interviewer which part they want to go deep on. Two candidates who felt this round went badly give this advice; one had gone straight into payment details and never finished the overall design.
- →Prepare banking concerns you can discuss in depth, such as idempotent payments, authorization latency and protecting customer data.
6. Power Day: behavioral (job fit)
One round of about three questions with follow-ups; several candidates say it ended well before the scheduled time.
Candidates describe standard STAR questions: challenging the status quo, learning something new, a conflict with a teammate or manager, changing priorities, delivering through an unexpected difficulty, and achieving something others thought too hard. Lead and senior loops add leadership and ownership questions. In 2026, two candidates were also asked how they use AI in their daily work and how it raises their output. Interviewers in two reports typed notes or summarized each answer back, and in one the follow-ups stayed general.
- →Prepare three or four projects and fit them to the common questions. Two candidates say that was enough.
- →Have two concrete examples of how you use AI at work, with how you check its output.
How the Capital One loop differs by role
TDP (new grad) and intern
These loops take the same CodeSignal OA and then a Superday of three rounds, an hour each in one intern report. One TDP candidate says the OA bar was not high and the Superday invitation came about two weeks later. The rounds are a behavioral round (why computer science, why Capital One, teamwork), a case round built on reading and explaining code, and a technical round: a transaction class design in one TDP report and a multi-part data matching problem in one intern report. In fall 2026, one TDP and one intern loop instead had an AI-assisted coding round in which candidates used Claude to fix bugs in an existing app, and in the TDP report then add a feature. Both of those loops also had the virtual card or chatbot case. One intern got an offer call three days after the Superday.
ML engineer
Two ML engineer reports describe the same four one-hour rounds: an ML fundamentals round that ends with walking through one of your end-to-end projects, a technical round with a short tree-traversal coding warm-up followed by questions on deploying and monitoring models, the virtual card case, and a behavioral round. One of the two candidates heard they had passed the next day and moved to team matching.
Applied researcher
One Applied Researcher II candidate had five one-hour rounds: a panel talk presenting a project or paper to three senior researchers, the case study, a technical round on their projects with ML coding, an ML engineering round, and behavioral. They were told on the third day that they had not passed, and feedback said their panel talk stayed too high level. An applied research intern had an HR screen, a hiring-manager round on math and LLM fine-tuning, then a Power Day with behavioral, case, ML engineering and a rapid-fire research round.
Lead, senior and principal
Lead and senior loops follow the four-round Power Day, with more leadership in the behavioral round. One senior candidate did all four rounds in one day, about four and a half hours, and one Lead candidate split them over two days. A senior principal loop had two system design rounds, a coding round and a behavioral round about leading projects and people. A Senior Lead AI Engineer loop replaced system design with an AI platform design round and added AI fundamentals to the coding round, and a reply to that report says AI tools were not allowed in any of the four rounds.
Non-engineering roles
Data science, analyst and business manager reports describe their own Power Days built around business cases, which this guide does not cover.
After the final round
Candidates who pass the Power Day go into team matching: two reports describe passing first and then matching with a team, and an applied research intern lists team matching between the Power Day and the offer call. Results came from the recruiter, from the next day to about three days after the Power Day in three reports, and one candidate who emailed their recruiter after three days was told to expect an answer the following Monday. Rejections were also quick in some reports and silent in others. One candidate says the OA email warns of a six-month wait after a failed attempt.
What does Capital One ask in each round?
Capital One interviews span 6distinct round types, shown below. Counts reflect distinct questions per round across the loops we’ve indexed.
- •Asking before coding. On the banking system round two candidates say the last part depends on what activity means, and several OA tasks are told differently from one report to the next.
- •Writing the test harness early. The banking system's tests arrive as lists of string operations, and several candidates say parsing them took longer than the class.
- •In system design, laying out entities, services and the read and write paths first, then asking the interviewer where to go deep. Two candidates who struggled give this advice.
- •Preparing three or four projects for the behavioral round and fitting them to the common questions. One candidate says the HR preparation material lists what is asked.
- •Running out of time on the coding round. The parts arrive one at a time, and one candidate left methods unwritten.
- •Not finishing the case study. One candidate did not get through it and another failed on it.
- •Brute force on the OA. Two candidates report hidden-test timeouts with nested loops.
- •Staying high level in the Applied Researcher panel talk. One candidate was rejected for it.
How to prepare for the Capital One interview
1. Practise CodeSignal simulations on a 70-minute clock
Work through long-statement array, string and matrix simulations, finish the two easy tasks quickly, and practise deciding when to move from the third task to the fourth.
2. Rehearse the case study out loud
Practise discussing a banking product's benefits and risks for customers and the bank, applying a rule set to examples condition by condition, and debugging short code with logic and boundary errors.
3. Build a multi-part class with your own test harness
Write a small banking-style class part by part against string-operation test lists, and time how long the harness takes you so it does not surprise you on the day.
4. Prepare a credit card or banking system design
Lay out the entities, services and read and write paths first, then prepare deep dives on payment authorization, fraud checks, idempotency and sensitive data.
5. Ready three or four stories, including how you use AI
Cover a challenge to the status quo, learning something new, a conflict and changed priorities, and have concrete examples of using AI at work. Ask the recruiter for the preparation material.
FAQ
How long does the Capital One interview process take?▾
What is a Capital One Power Day?▾
How many rounds are in the Capital One interview?▾
Is there an online assessment, and what score do I need?▾
Can I use AI in the Capital One interview?▾
What is the Capital One case study interview?▾
Is there a phone screen before the Power Day?▾
What happens after the Power Day?▾
How fresh is this Capital One interview data?▾
Get the full Capital One catalog
Every question, every candidate-reported follow-up, and what passers actually do. Monthly refresh.