Exness Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Exness.
Exness
Software Developer
Mid Average Negative experience No offer 2 rounds
Interview process
Technical screen Recruiter call
Interview formats
Technical Behavioral
The tech interview experience wasn't great. They asked standard checklist questions and focused on memorization rather than collaborative problem-solving. They were also unforgiving if your explanations weren't perfectly clear immediately. It felt like they were looking for a rigid, uncreative, and uninspired developer profile. The only upside was surprisingly good feedback.
Confirmed questions1 question
- Can you explain the garbage collector in Golang?
Exness
Software Developer
Mid Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite Panel
Interview formats
Behavioral Technical Coding System Design
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.
Confirmed questions1 question
- Can you share an instance where you encountered a challenge while working in a team and how you managed to overcome it?
Exness
Software Engineer
Mid Difficult Positive experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design
It was alright. The interview involved questions on advanced Golang concepts, high load systems, and how to manage them. There were also questions about Kafka clusters, specifically how to handle issues when the cluster has problems reading messages and how to manage failures.
Confirmed questions8 questions
- Can you discuss advanced topics in Golang?
- Tell me about high load systems.
- How do you manage high load systems?
Exness Software Engineer Interview Questions
Quoted word for word from Exness interview reports.
“How many bytes does a Go structure take up in memory, including any buffers?”
Read reports →“What are all the synchronization mechanisms available in Go?”
Read reports →“Can you explain the garbage collector in Golang?”
Read reports →“Could you name all the indexes that Postgres has?”
Read reports →“How do you manage failures in a Kafka cluster?”
Read report →“Can you explain the meaning of each letter in the SOLID principles?”
Read report →“Tell me about struct layout in memory”
Read report →“How would you handle a Kafka cluster problem during message reading?”
Read report →“Tell me about concurrency primitives”
Read report →Formats, difficulty and experience
Across all 8 Exness interview reports.