I applied through college or university. I interviewed at FDM Group (Toronto, ON) in Jun 2017
Interview
I was first contacted to schedule a phone interview. The phone interview was the first stage and was for about 15mins. It wasn't difficult, He asked basic interview question like what do you know about FDM, Why would you like to work here and about your experience. After the questions, I was invited for the interview day which was about a week later. The interview took place in Toronto and went on from 9am to about 2pm. It was made up of 2 short interviews, each for about 15 mins (one technical and one personal) and 3 test which were on programming, math and set notation. The questions on programming and set notation weren't difficult and the math test was mostly to test how quick you are. The next day, they let you know whether or not you got it.
The entire process was pretty simple. Initially you will get an arctic shores assessment which tests your analytical and problem-solving skills. Post that, you will be scheduled for an initial screening call for 20 mins with your recruiter. You will be given a hackerrank test which includes coding+sql based on the role. If you have cleared the round,, you will be invited for a final interview with the account manager
I applied in-person. I interviewed at FDM Group (Toronto, ON) in Jun 2026
Interview
I honestly feel like the first Java coding question in this OA is designed in a very frustrating way.
The issue is not just that the question is hard. The real problem is that the provided starter code seems to contain some very hidden trap that makes the solution fail to compile, and the platform gives almost no useful compiler feedback. You only have around 20 minutes, but you are expected to not only write the actual logic, but also somehow identify the intentionally confusing issue inside the provided code without a proper IDE or clear error message.
That makes the question feel less like a Java coding assessment and more like a blind debugging challenge. Unless you are very strong at debugging Java syntax and environment issues under pressure, it is extremely easy to get stuck forever even if your actual idea is correct.
I understand that companies want to test attention to detail, but hiding a subtle compile issue in the source code and giving no clear feedback feels unnecessarily punishing. In a real development environment, nobody debugs this way. You would normally have IDE hints, compiler logs, stack traces, or at least enough information to locate the problem.
For an entry-level or graduate-style OA, this feels especially rough because the assessment is supposed to test basic coding ability, not whether you can reverse-engineer a hidden trap in a broken template within 20 minutes.
I applied online. I interviewed at FDM Group in Jun 2026
Interview
You have an initial call with recruiter about background, schooling and experience, Then technical assessment on coding platform to test programming and Java knowledge. Then behavioral interview with questions about soft skills.
Interview questions [1]
Question 1
In the behavioral, they asked me to describe background and history.
