Exness Interview Questions
& Process

There were 4 rounds in total. The first was a TA round lasting about 40 minutes where they asked general questions about my experience, why I was interested in Exness, my notice period, salary expectations, and my reasons for a career switch. Then there was an English test and a capability test, followed by a verbal capability test. The final round was with the Team Leads and the HR Manager. You really just need to prepare well for the interview, get familiar with Exness and customer support roles. I received an offer, but unfortunately had to decline it due to some documentation issues. I'm hopeful our paths might cross again in the future, as I was quite keen on joining.

I went through a 6-step interview process for this that was originally stated to include only 3 steps. Expectations changed repeatedly — including an unexpected office visit, an unannounced second assignment, and multiple additional calls. Assignments were abstract and unclear, and the recruiter was unable to provide meaningful clarification. In one case, I explicitly confirmed in writing what was expected — but in the final call, the team criticized the result for not matching a set of expectations that were never communicated. Calls routinely ran over the promised time, and by the final stage, the tone of communication had become dismissive and adversarial. I ultimately left the process with serious concerns about internal communication, team alignment, and respect for candidates' time.

The interview process was pretty standard and took a while. It started with an online application followed by a recruiter screening where they just looked over my resume and asked basic questions like why I want the role and what my current situation is. After that came a technical screening, which felt like a LeetCode challenge. They asked typical algorithmic questions that don't really reflect what I'd do on the job, mostly medium/hard problems on arrays, graphs, or DP. Then there was a system design round where they wanted a full architecture for a vague problem in 45 minutes, with a lot of buzzwords. It felt more like a performance than a conversation. The final round was with the team, where a few engineers asked more technical and behavioral questions, but it seemed like they were just checking off a list. I got a few questions like 'Tell me about a time you had a conflict' and 'How do you handle deadlines?', which wasn't surprising.

The HR was nice and flexible with scheduling, but took over two weeks to respond with feedback. The technical interview was rough. The interviewer didn't seem to read my CV, was late, and frankly, didn't present well. They spent way too long on IP track/SLA, which felt unnecessary given RFC 2544 and ITU-T Y.1564 exist for measurements, and many ISPs don't work with more than these. They also showed a lack of understanding about jitter with real-time traffic. The interviewer expected me to guess the problem and solve it, and got into an argument about MPLS and QoS, even when I explained that some ISPs might not offer those services but they still support them. Overall, a very weak technical interviewer.