Capital on Tap logo

Capital on Tap Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 14 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Capital on Tap.

Showing 3 of 14
Capital on Tap logo
Capital on Tap

Senior Software Engineer

Engineering · a year ago

Senior Difficult Negative experience No offer 2 rounds
Interview process
Technical screen Onsite Presentation
Interview formats
Coding Technical Presentation

The interview process was alright until the final stage. The technical "pairing" test wasn't really collaborative, more like a "staring" contest. They lost interest after a while, lol. 90 minutes isn't enough for backend if you want to follow SOLID and TDD principles, so I only got halfway through. After that, I was supposed to have a 30-minute chat with the CTO or Head of Engineering, but they didn't even show up, lol. It was unprofessional in two ways: 1) The host didn't show up, and HR didn't mention anything. 2) The "pairing" wasn't a real pairing exercise; it was more like doing a task while they muted themselves, haha. The time given wasn't enough to do it properly, so I'm not sure if they even reviewed what they asked us to do.

Confirmed questions1 question
  • Tell me about your experience with microservices and how you've utilized them.
Capital on Tap logo
Capital on Tap

Software Engineer

Engineering · more than a year ago

Entry Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Technical Coding

First there was a video call with a Talent Partner. Then I had a more technical chat with an Engineering Manager, which was a good two-way street to ask questions and learn about the job. The last part was a code pairing with 2 Engineers, which I liked. I had to explain how I'd tackle the task and talk through my actions and reasoning while doing it. Even though I didn't get the job with Capital on Tap, the process felt fair and informative, and I got useful feedback afterwards to know where to improve. I'd definitely apply again, it seems like a great company.

Confirmed questions1 question
  • Can you tell me about your preferred C# feature, explain its functionality, and how it operates?
Capital on Tap logo
Capital on Tap

Software Engineer

Engineering

Mid Average Negative experience No offer 5 rounds
Interview process
Technical screen Take home Technical screen Technical screen Technical screen
Interview formats
Technical Coding

Had 5 interview stages, including a test and then a live coding session. They dropped me at the end with no explanation. A complete waste of time.

Confirmed questions1 question
  • General questions about the .NET domain.

Capital on Tap Software Engineer Interview Questions

Quoted word for word from Capital on Tap interview reports.

Can you define a linked list and explain the difference compared to a doubly linked list

Read reports

Can you differentiate between unit testing and integration testing?

Read reports

Given two user stories, complete them to meet the objective.

Read report

Can you tell me about your preferred C# feature, explain its functionality, and how it operates?

Read report

Formats, difficulty and experience

Across all 14 Capital on Tap interview reports.

Interview formats

Coding 34.2%
Technical 26.3%
Behavioral 26.3%
Presentation 5.3%
Group 5.3%

Interview difficulty

Easy 14.3%
Average 64.3%
Difficult 21.4%

Candidate experience

Negative 50%
Positive 42.9%
Neutral 7.1%