Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Capital One (Maryland City, MD) nel mese di gen 2023
Colloquio
3 hour power day, had a hard time since they rescheduled my meeting date and time. Overall a good experience though. I believe that the questions were easy but I had a hard time answering the case study questions, since they were very open ended
Ho presentato la mia candidatura di persona. Ho sostenuto un colloquio presso Capital One nel mese di mar 2025
Colloquio
When I first signed up for the Capital One online coding assessment, I wanted to know exactly what to expect. The process starts with a setup where I had to show my face, my ID, and share my screen, camera, and microphone. This step helps CodeSignal make sure everyone follows the rules. I had to close all other tabs and apps before the timer started. Once I finished the setup, the real challenge began.
The assessment gave me 70 minutes to solve four coding questions. All the questions appeared at once, so I could pick any order. I could switch between them as much as I wanted. The CodeSignal interface let me choose my programming language, like Python or JavaScript, unless Capital One set limits. I liked that I could change languages during the test if I needed. The online coding assessment ran in CodeSignal’s own IDE, so I could not use any outside tools.
Here’s a quick breakdown of the format, I've shared the full version of my interview experience on my homepage Linkjob. Hope it helps everyone.
Four coding questions, all visible from the start.
70 minutes total to finish.
Remote proctoring with camera, microphone, and screen sharing.
Choice of programming language (unless restricted).
All work done in the CodeSignal IDE.
Domande di colloquio [1]
Domanda 1
Here are the most common types I faced:
Array Manipulation: Sorting, searching, or changing data inside arrays. These data manipulation tasks showed up a lot.
String Pattern Matching: Finding or changing patterns in strings. Sometimes I had to check if a word was a palindrome or count certain letters.
Dynamic Programming: Breaking big problems into smaller ones and solving each part. These algorithmic challenges tested my problem-solving skills.
Debugging Exercises: Finding and fixing errors in code. These questions checked if I could spot mistakes quickly.
System Design: Rare, but sometimes I had to think about how to build a simple system or explain my approach.