The first thing you need to do is an old-school test on the HackerRank platform, where you have 21 questions to answer and 4 code challenges to develop, all within 90 minutes.
Most of the questions are quite extensive for such an amount of time, so at least 50% of the time is spent reading the questions. This means you have around 45 minutes to find the answers to the 21 questions and develop the 4 codes.
The questions range from very easy to quite difficult, but some of them are wrong. Once you put the same code in the compiler, it just gives you an answer that is not an option.
For the code challenges, they are quite hard due to the time remaining. At the end, I had only 5 minutes to find a solution and code each of them.
The HackerRank platform is bugged. For the questions, you know how much time you still have, but not for the code part, making that really challenging to manage.
If the test was 90 minutes for the questions and another 90 minutes for the code, that would be an average level of difficulty.
It's not allowed to share the questions, but you can expect deep knowledge of memory allocation and auto-casting type definition. Most of the questions are about these subjects.
An example of an easy question would be:
`geek = make_tuple('a', 10, 15.5); auto a = get<0>(geek) auto b = get<1>(geek); auto c = get<2>(geek)
What kind of type is a, b, c?`
Or maybe they could ask, what is the result of a+b+c?
The following metrics were computed from 1 interview experience for the Flow Traders C++ Software Engineer role in Amsterdam, Netherlands.
Flow Traders's interview process for their C++ Software Engineer roles in Amsterdam, Netherlands is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Flow Traders's C++ Software Engineer interview process in Amsterdam, Netherlands.