FNZ Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 48 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at FNZ.
FNZ
Software Developer
Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Take home
Interview formats
Technical Coding
The recruiters were kind of rude and didn't use a calendar for scheduling, just told me when they'd call. My initial phone screen got cancelled last minute, and then they called the next day when I couldn't talk. I reached out to another recruiter who then set a time to call. After a 20-minute chat, I got a test invite, though I didn't do too well on it.
Confirmed questions2 questions
- There was a Codility test with easy to lower intermediate questions.
- Also, an SQL task involving joins and aggregate functions was given.
FNZ
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Technical Coding
It was a pretty bad experience. I was contacted by two recruitment agencies and their own recruiter, and they all had different info on the salary. Lots of unwanted calls during the day and incorrect meeting links. Then, a really disappointing interview happened. They didn't ask anything about architecture, DDD, distributed systems, microservices, testing, development processes, scaling, maintenance, deployment, logging, or monitoring. No advanced .NET questions either. Instead, they asked basic questions like the difference between inner and left join, which didn't really help them find qualified candidates.
Confirmed questions1 question
- Could you explain what a left join is and how it differs from an inner join?
FNZ
Software Engineer
Mid Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Take home Recruiter call Phone screen Background check Offer
Interview formats
Behavioral Technical Coding
The whole thing was pretty quick, from first interview to offer was about 1.5 weeks. There were 2 interviews total, each about an hour long, done over Microsoft Teams. They hit me with a bunch of scenario-based questions to see if my work attitude matched what they were looking for and if I'd be a good fit. Between the interviews, I had to do a technical coding exercise on Codility and also the Thomas International GIA test. For the coding test, if you can handle easy-to-medium LeetCode questions, you'll be fine. The interviewers were super professional and answered all my questions well at the end, so it was a good experience overall.
Confirmed questions1 question
- How would you manage disagreements when collaborating with teammates?
FNZ Software Engineer Interview Questions
Quoted word for word from FNZ interview reports.
“Given the length and breadth of an Olympic pool, estimate the time an average person would take to drink it dry.”
Read reports →“How long would it take to drink a 50m olympic pool?”
Read reports →“What is the quantity of ice required to elevate the ocean's level by a specified measure?”
Read reports →“What distinguishes a clustered index from a non-clustered index?”
Read reports →“What is the difference between PATCH and PUT in a REST API?”
Read report →“Write a function to divide a by b without using the division operator.”
Read report →“What's the difference between an interface and an abstract class?”
Read report →“What is the difference between a struct and a class?”
Read report →“What's the difference between the GET and POST methods?”
Read report →Formats, difficulty and experience
Across all 48 FNZ interview reports.