DEV Community

Cesar Vega
Cesar Vega

Posted on Edited on

My Capital One Interview experience. - Full-stack staff engineer.

My experience with Capital One started with a recruiter call (They found me through LinkedIn - Canada based). The process took about four weeks. The first step was a ~10-minute screening with the recruiter, then a CodeSignal assignment with 4 questions:

  1. neighborSum - Pass: +300 points
  2. alternatingSort - Pass: +300 points
  3. I didn't even see this problem.
  4. 1D Obstacle Placement & Collision Check - completed with the brute-force: +100 points

Total points: 700 points. Enough to pass to the second round.

The second round was a video call system design interview. The question was, "Design a URL shortener." The interviewer was very professional and gave me the non-functional requirements up front:
URL shortening system

New system, internal only for internal employees
- Low volume of new URL creation 
- 2000 new URLs within the first 2 days   
- 500 new URLs per day steady state
- 5000 redirects per day, steady from day one
- North America only for MVP implementation
- 50,000 internal users
Enter fullscreen mode Exit fullscreen mode

The interviewer made it clear that they wanted me to dive deep into how the short URL would be created, stored, and retrieved. He also asked me to explain my choice of database (SQL vs. NoSQL).

I didn't pass this interview because I fumbled the short URL creation details: e.g., sequential ID using Redis and then Base 10 ID to Base62. Or a truncated Hash function with collision checking. Plus, I couldn't explain the differences between SQL and NoSQL other than the classic "SQL is for structured data and strong consistency, and NoSQL is for unstructured data and massive scale"

After the interview, I decided to dive deeper into URL shorteners, and I wrote this article with lessons I read.

About the author:
I'm a Frontend Senior / Staff engineer. I'm currently exploring new engineering opportunities. connect with me on LinkedIn or check out my work on GitHub.

Top comments (0)