The interview process is a 3-step process, as mentioned elsewhere:

1. Initial screen with a recruiter who interfaces with you on behalf of Capital One.

2. CodeSignal technical assessment. This assessment is 70 minutes long with 4 questions. It's strategized to go 1, 2, 4, 3 as the third question is longer. I scored 710/1200, and I believe I still passed.

3. POWER DAY. This consists of 4 50-minute sessions: one behavioral, one case study, one software design, and one coding. They provide documents detailing each session and have YouTube videos outlining them, which I found helpful. My software design interview was unlike anything I'd experienced before, as it involved designing for 5 features in 45 minutes.

Basic Behavioral:

• Time you learned something new.
• Time you had a disagreement.
• Time you experienced a shift in priorities on a project.

Case Study:

A Capital One feature, exploring its benefits and drawbacks, and then interacting with some basic code.

Coding Exercise:

I wish I had practiced this more with others. I had to revise my criteria 5 times before understanding the desired input. Next time, I should be more comfortable with silence and working the input to understand the ask. In the end, my code ran but with one embedded for-loop. I was asked to clean that up even though the embedded for-loop could only contain a size of 3. Honestly, my bad for not having a better response.

Software Design:

Design an MVP for the following features:

1. CC application
2. Posting transactions
3. Viewing transactions
4. Viewing daily, weekly, and monthly stats
5. A last feature that I didn't get to.

I have no idea how I'm supposed to design an architecture with each of these features in mind and optimized in 45 minutes.