I applied through other source. The process took 4 weeks. I interviewed at FDM Group in Aug 2025
Interview
They sent me an ridiculous assessment, where I have to unlock a safe by clicking numbers and solving puzzles for an hour. Nonsense.
Then one of their recruiters sent an email to schedule a initial interview. I provided the times I'm available, he sent me a google invite for 5AM est in the morning stating we will meet in a teams meeting at 10am est... AND there was no teams link either!
I tried to reach out via email no luck until the day before the interview. He responded saying he will call me 10am est today. I'm waiting before going to work, delaying my personal life and chores and nothing.
This is ridiculous. Don't give people hope and then do nothing.
Waste of time.
1
Other Software Engineer Interview Reviews for FDM Group
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.
Screener Call with a recruiter, very basic technical assessment with programming challenges, then a video interview. Quick review of your resume and projects, very straightforward. Recieved a call from the recruiter about a week later saying the team wanted to hire me but couldn't confirm a start date yet, but probably could in the coming weeks.
For the next 6 months I received a call from FDM once per month asking me if I was still interested in the role, and informing me that they could not confirm a start date. While waiting for FDM I applied, interviewed, and received an offer for another company, which I accepted.
Interview questions [1]
Question 1
Tell me about a time you've had a disagreement with a colleague, how did you resolve this?