J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez FDM Group (Toronto, ON) en sept. 2018
Entretien
Interviewer called 20 minutes later after the scheduled phone interview, quizzed me on things that were not part of the job description, chewed me out for "not knowing enough about the company" despite giving me no new information except that training is 16 weeks long. Incredibly awkward interactions every time. Passed their logic and video interview. Then calls telling me, "how do you think it went?" before letting me know I passed the previous stage and now they would like an on-site interview from 8;45 to 2;30 while I am in another city. No offer for traveling expenses.
Questions d'entretien [1]
Question 1
20-21 Multiple choice question to see if you can follow logic. No specific language.
Video interview asking generic questions like, 'What would you do if you were behind in a project' 'what would you do if someone else knew more about the project you are working on'
Phone interview asked stuff like, "what does Final do in Java", "What are the differences between an inner and outer join", "difference between public and static", "how does polymorphism work in Java"
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.
