J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez FDM Group (Toronto, ON) en juin 2017
Entretien
First, they will give a brief idea about the company and then will let you know the flow of whole hiring process.
Followed by a variety of aptitude, Maths, set and van diagram test. The test is easy if you know pretty basic stuff and have good aptitude skills. When several candidates were interviewing others were assigned a group task of solving different situation based problems.
Questions d'entretien [1]
Question 1
1.Multithreading and about object oriented programming.
2.What is the class?
3. Some problem on array and pointer and will tell how to solve.
HR:
1. First, introduces themselves and then asks us to introduce ourselves.
2. Why do you want to join the company?
about 7 min technical and 7 min HR interview.
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
J'ai postulé en personne. J'ai passé un entretien chez FDM Group (Toronto, ON) en juin 2026
Entretien
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.
J'ai postulé en ligne. J'ai passé un entretien chez FDM Group en juin 2026
Entretien
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.
Questions d'entretien [1]
Question 1
In the behavioral, they asked me to describe background and history.