Capital One's coding assessment for software engineering candidates is commonly reported to be CodeSignal's General Coding Assessment: four tasks in 70 minutes, scored from 200 to 600 and usually proctored with camera, microphone and screen sharing. The tasks climb from a short warm-up to an algorithm problem, partial credit counts, and CodeSignal itself says almost no company expects you to finish all four. If you already know basic data structures, two focused weeks of array, string, matrix and hash-map practice under a real 70-minute clock is a realistic prep window.
This guide separates documented facts from candidate reports and covers preparation only: the assessment itself is done on your own, under the rules Capital One and CodeSignal show you before you start.
The format at a glance
| What | Details | Where it comes from |
|---|---|---|
| Platform | CodeSignal | Candidate reports (Capital One's student interview page does not name a vendor) |
| Assessment | General Coding Assessment, built on CodeSignal's General Coding Framework | Candidate reports; CodeSignal documentation |
| Length | 4 coding tasks, 70 minutes | CodeSignal's framework spec; matches most Capital One reports |
| Task order | All four visible once the timer starts; you can work them in any order | CodeSignal's GCA help article |
| Score | 200–600, with partial credit | CodeSignal |
| Proctoring | Camera, microphone, screen share and a government photo ID | CodeSignal requirements; Capital One candidates report it proctored |
| Passing score | Not published | — |
Reports are not uniform. Some candidates and prep guides describe other question counts or a 90-minute limit, at least one guide says the test can come through HackerRank instead, and some internship candidates report a separate multiple-choice role-fit exercise. Your invitation is the final word: it states the platform, length, rules and whether the session is proctored.
Where it sits in Capital One's process
Capital One's student interview guide says the steps vary by position. It lists a possible automated assessment, a recruiter phone screen, an hour-long virtual exam and a 30-minute hiring manager pre-screen for some roles, and finally a Power Day of job-fit, behavioral and case interviews. For software engineering roles, candidates commonly describe this sequence:
- Application.
- The CodeSignal assessment, often sent automatically after you apply. Some intern candidates report a role-fit questionnaire as well.
- A recruiter screen, plus a hiring manager pre-screen for some roles.
- The Power Day: several back-to-back virtual interviews, typically live coding, a business case and behavioral, with system design reported for some roles.
The assessment is the gate to the Power Day, so the goal is a solid score, not a perfect one. For the rounds after it, see our Capital One coding interview questions and Power Day guide.
What each of the four tasks tests
CodeSignal's published brief for the framework behind the General Coding Assessment defines four modules, one question each, with an expected code size and solve time:
| Task | Expected size and time | What it covers | What it leaves out |
|---|---|---|---|
| 1. Basic Coding | 5–10 lines, ~10 min | Basic operations on numbers, strings and arrays; usually one loop with a couple of conditions | Spotting patterns, algorithms, optimization |
| 2. Data Manipulation | 10–20 lines, ~15 min | Splitting numbers into digits; splitting, comparing, reversing and joining strings and arrays; one or two nested loops | Spotting patterns, algorithms |
| 3. Implementation Efficiency | 25–40 lines, ~20 min | Everything above, plus 2D arrays (traversal orders, transposing), hash maps keyed by strings or integers, custom comparators and merge functions | Graphs, number theory, dynamic programming, advanced structures |
| 4. Problem Solving | 25–35 lines, ~30 min | Greedy, divide and conquer, two pointers, hash maps and sets to speed up lookups, discrete math basics | Brain teasers; specialized algorithms such as Dijkstra, Kruskal or FFT |
Two details matter. The expected times add up to 75 minutes, five more than you get, so the clock is tight by design. And task 3 rewards careful implementation over clever algorithms: the brief's sample is a falling-block simulation on a grid, where the logic is simple and the index handling is where points slip away.
Capital One candidates describe the same arc: two quick string and array tasks, a heavier matrix or simulation task, then a harder fourth. The brief says the spec exists to generate variations of questions, so treat it as the usual shape, not a promise of what you will see.
What task 4 looks like
CodeSignal's published Problem Solving example asks you to count index pairs in an array of up to 105 integers whose sum is a power of two. The nested-loop answer is obvious and too slow at that size. The intended idea is to walk the array once, keep a hash map of counts, and for each number check every power of two up to the largest possible sum. That is the flavor of task 4: an obvious brute force, plus a hash-map, sorting or two-pointer idea that is fast enough.
How scoring works
- The range is 200 to 600. CodeSignal's framework brief gives that range. Older posts that cite a 300–850 range refer to an earlier CodeSignal scale, so those numbers are not directly comparable.
- Partial credit counts. CodeSignal's CEO has said that correct parts of an unfinished task still earn points, and that the tasks are not weighted equally because they differ in difficulty.
- Finishing everything is rare. In the same interview, CodeSignal says only about 1% of test takers finish all four tasks, and that almost no company expects it.
- Some tests are hidden. Candidates commonly report visible sample tests plus hidden ones, so passing the visible cases does not guarantee full credit; hidden tests tend to probe edge cases.
- Capital One's cutoff is not public. Candidate guesses vary widely, and the bar may differ by role and hiring cycle.
The practical target: fully solve tasks 1 and 2, get task 3 working, and bank whatever correct cases you can on task 4.
A 70-minute game plan
CodeSignal's CEO recommends working the questions in order and using spare time at the end to review; the company's assessment checklist adds that it can make sense to move on from a question that is eating your time and return later. Two rules from CodeSignal's GCA help article shape the plan: your code is saved only if you submit before leaving a task, and each task is graded on your highest-scoring submission, so submitting early never costs you. Then follow a time budget:
| Minutes | What to do |
|---|---|
| 0–3 | Read all four prompts. Note the input sizes; they tell you whether a brute force will pass. |
| 3–12 | Task 1. Write it plainly, run the tests, add one or two edge cases of your own, submit. |
| 12–27 | Task 2. Same routine. Once it passes the visible tests, submit and move on. |
| 27–47 | Task 3. Write the steps as comments first, then fill them in. Most bugs here are off-by-one indexing. |
| 47–67 | Task 4. Submit a correct brute force first, then optimize and resubmit if time allows. |
| 67–70 | Check that every task you touched has been submitted. |
If a task runs five minutes past its slot, submit what you have and move on. On task 4, a slow solution that passes the small tests beats an elegant one that does not run.
A two-week prep plan
This plan assumes you already know arrays, strings, hash maps and sorting. If you don't, start with our new grad online assessment guide and add a week of fundamentals first.
| Days | Focus | What to do |
|---|---|---|
| 1 | Baseline | Use CodeSignal's practice page to learn the editor and test runner (companies do not see that activity). Then do four problems of rising difficulty in 70 minutes and note which one cost you the most time. |
| 2–3 | Tasks 1–2 speed | Six to eight easy string, array and digit problems a day. Goal: a correct easy problem in under 10 minutes on the first run. |
| 4–6 | Task 3: grids | Matrix traversal (row, column, diagonal, spiral), transposing and rotating, grid simulations, hash maps keyed by strings, custom sort comparators. |
| 7–9 | Task 4: problem solving | Hash-map counting (pair sums, frequencies), two pointers, sliding window, prefix sums, greedy with sorting. Brute force first every time, then optimize. |
| 10 | Full mock #1 | Four problems, 70 minutes, no notes, no pausing. Grade yourself only on tests passed. |
| 11–12 | Fix the weakest task | Re-solve missed problems from a blank editor. Drill edge cases: empty input, one element, duplicates, negatives, a 1×1 grid. |
| 13 | Full mock #2 and setup check | A second timed set, then check your camera, microphone, browser, connection and photo ID. |
| 14 | Rest | Light review only. CodeSignal's own checklist recommends taking the test when you are rested. |
For the task 4 patterns, our 15 LeetCode patterns guide covers two pointers, sliding window and prefix sums with templates. For task 3, drill a few grid helpers until you can type them without thinking:
def neighbors(grid, r, c):
rows, cols = len(grid), len(grid[0])
for dr, dc in ((1, 0), (-1, 0), (0, 1), (0, -1)):
nr, nc = r + dr, c + dc
if 0 <= nr < rows and 0 <= nc < cols:
yield nr, nc
def transpose(grid):
return [list(col) for col in zip(*grid)]
def rotate_clockwise(grid):
return [list(col)[::-1] for col in zip(*grid)]Setup, proctoring and the rules
The assessment must be done on your own, under the rules Capital One and CodeSignal set. Those rules are shown before the session starts; follow them exactly. CodeSignal reviews each proctored session to confirm your ID and that the rules were followed before it verifies the result, so breaking a rule is a far worse outcome than a middling score.
CodeSignal's support pages list what a proctored session needs:
- A computer with a working camera and microphone, and the ability to share your screen.
- A valid, unexpired, government-issued photo ID showing your full name.
- A current version of Chrome or Firefox and a stable connection (CodeSignal lists at least 500 Kb/s).
- A quiet room. Close other apps and tabs, silence notifications and plug in your laptop.
The timer starts only after setup, so the ID and screen-share steps don't eat into your 70 minutes. Test everything the day before anyway.
Retakes and reusing a past score
CodeSignal results can travel between employers. The invitation in your CodeSignal Assessment Hub may let you share an eligible verified past result, or retake if you are outside the cooldown (for the GCA, CodeSignal allows two attempts in 30 days and three in 180 days). Know these rules from CodeSignal's help center before you click anything:
- If you retake, the company receives the new result once it is validated, even if it is lower.
- A company that already received an earlier result keeps access to it.
- Declining an invitation removes it; after that, only the company can reactivate it.
Capital One does not publish whether it accepts a shared past score, so go by the options your invitation shows. If your portal shows an assessment pending but no invitation arrived, check spam, then contact your recruiting team. Our CodeSignal assessment guide covers the platform in more depth.
After the assessment: getting ready for the Power Day
Pass the assessment and the format flips: you solve in front of people and explain as you go. Capital One's student page says Power Day interviews can include job-fit, behavioral and case interviews, and that video is required for virtual interviews. Engineering candidates commonly add a live coding round and, for some roles, system design.
Start the talking practice during assessment prep: on a few problems each day, narrate your approach and the Big-O out loud. A free AI mock interview in CoPilot Interview covers the spoken side: paste the Capital One job description and your résumé, pick a mix of behavioral and coding questions, answer out loud, and get each answer scored with what worked and what to improve.
Practice the rounds that come after the assessment
CoPilot Interview's AI mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer, then gives you a report with likely next-round questions and practice drills. The free plan is 15 minutes a day, with no credit card.
Try a free AI mock interviewFAQ
How long is the Capital One CodeSignal assessment?
Candidates commonly report CodeSignal's General Coding Assessment: four coding tasks in 70 minutes, which is the length CodeSignal documents for that framework. Some older reports describe other configurations, so check your invitation, which states the length and the rules.
What score do you need to pass the Capital One CodeSignal assessment?
Capital One does not publish a cutoff. CodeSignal scores this assessment from 200 to 600 with partial credit, and CodeSignal says almost no company expects candidates to finish all four tasks, so aim to fully solve the first two and get as far as you can on the last two.
Is the Capital One CodeSignal test proctored?
Candidates commonly report that it is, with camera, microphone and screen sharing plus a photo ID check. Your invitation states the conditions; complete the assessment on your own and follow those rules exactly.
What topics should I study for the Capital One CodeSignal assessment?
Focus on string, array and digit manipulation for the first two tasks, 2D-array traversal and simulation for the third, and hash maps, two pointers, prefix sums and greedy techniques for the fourth. CodeSignal's framework excludes specialized algorithms such as Dijkstra, Kruskal and FFT, though question pools change, so expect some variation.
What comes after the Capital One CodeSignal assessment?
Candidates who pass are commonly invited to a Power Day of back-to-back virtual interviews. Capital One says these can include job-fit, behavioral and case interviews, and engineering candidates usually also report a live coding round.