Core Developer applicants have rated the interview process at Virtu Financial with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 50% positive. To compare, the company-average is 39.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Core Developer roles take an average of 14 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at Virtu Financial overall takes an average of 23 days.
Common stages of the interview process at Virtu Financial as a Core Developer according to 2 Glassdoor interviews include:
Skills test: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
I applied through college or university. The process took 2 weeks. I interviewed at Virtu Financial in Aug 2016
Interview
I sent resume to a recruiter. I got a link to finish a online coding test. It was 75 min test with 5 coding problems. Not so hard. After a week, I had a skype interview. My skills did not match the position very well. I was rejected after one day.
Interview questions [1]
Question 1
Some normal questions but also some aggressive questions about my resume.
I applied through a recruiter. The process took 2 weeks. I interviewed at Virtu Financial (Singapore) in Oct 2015
Interview
First round was an online coding test at Codility. I was informed a week before about this online testing website and was told that I would need to answer 4 questions in 1.5 hours (90 mins). I was given a week to take the test at any time anywhere. Once the test is started it has to be finished within 90 mins.
After the Codility test, I got a call next for second round interview. It was 90 mins of MCQ (an IQ test), followed by brainteaser/puzzle interview with a finance (non-tech) person.
I got an offer elsewhere, so I did not take the 2nd round or further pursue Virtu.
Interview questions [1]
Question 1
The 4 problems in Codility were of medium difficulty. I answered them in C++. I answered 3 problems well, but ran out of time on the 4th one. I could only write a brute-force solution for the last one.