TP ICAP logo

TP ICAP Software Engineer Interview Questions
& Process

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

Based on 13 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
61.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at TP ICAP.

Showing 3 of 13
TP ICAP logo
TP ICAP

Software Engineer

Engineering · nearly a year ago

Mid Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

It's a two-part process. First, we'll have an initial chat to see if you meet the basic requirements, if your experience lines up, and how you communicate. Then, we'll dive deeper to check your technical skills, how you solve problems, and if you'd be a good fit overall.

Confirmed questions1 question
  • Tell me what you know about our company.
TP ICAP logo
TP ICAP

Principal Software Engineer

Engineering · a year ago

Staff Easy Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical

The first round was supposed to be a technical interview, but the interviewers weren't technically skilled and one seemed disinterested. It was quite disappointing. Hopefully, they'll use competent interviewers in the future to avoid wasting time and receiving discouraging feedback.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

TP ICAP logo
TP ICAP

Senior Software Engineer

Engineering

Senior Easy Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Coding Technical

It was a 2 stage interview process. First up was a MS Teams call with a principal and senior engineer who are based in Belfast. It kicked off with some questions about my competencies, then we moved onto a straightforward pair programming exercise. They wanted me to review a method for calculating different discount rates on an order and suggest improvements verbally. The second stage was another MS Teams call, this time with the project lead in London. This stage began with a coding exercise. I had to download some source code and run it on my IDE. The task was to implement a small feature based on a description in a readme file. This involved figuring out where in the existing codebase the new feature would fit best and then adding it. Although it wasn't explicitly stated, it seemed like the time and space complexity of my solution was important, so I'd suggest reviewing data structures before this interview. After the coding part, we had a short chat about my past experience and how I'd fit into the role.

Confirmed questions1 question
  • Can you share an instance where you had to challenge a product manager's requirement and explain the outcome?

TP ICAP Software Engineer Interview Questions

Quoted word for word from TP ICAP interview reports.

Could you explain the difference between dynamic variables and vars?

Read reports

Could you create a class model given a brief functional specification?

Read reports

Could you answer various C++ questions and write some code?

Read report

Could you share an instance where you made good use of your network?

Read report

Can you share an instance where you had to challenge a product manager's requirement and explain the outcome?

Read report

Formats, difficulty and experience

Across all 13 TP ICAP interview reports.

Interview formats

Technical 50%
Behavioral 33.3%
Coding 16.7%

Interview difficulty

Easy 23.1%
Average 61.5%
Difficult 15.4%

Candidate experience

Positive 61.5%
Negative 15.4%
Neutral 23.1%