J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez FDM Group
Entretien
At first it's phone calls, they'll ask you about your experience and then set up a video interview where you record your answers and then have those reviewed. You'll also do a fairly easy test where you'll be asked to look at flow diagrams and code, but mostly it's just logic puzzles. At the end you have a live interview over video chat like Skype, and you'll receive an offer soon thereafter if you made it. What you really need to know is that you shouldn't waste your time with them. They survive by preying on insecure devs looking for a first job out of school or boot camp. They have some months of training which is largely described as something you could find on your own online, but they lock you into a 2 year contract where you'd have to pay them back some tens of thousands of dollars. It's a scam that you should avoid no matter how insecure you might be, these people aren't even guaranteeing you a job writing software. If they can't find someone to rent you out to, they'll force you to be a bank teller or something. Their salary offerings are half of the bare minimum of most entry level positions. I cannot express to you just how bad of a move it is for you to chain yourself to such an abusive company. Look elsewhere, find a part time job while you work on personal projects and build a portfolio, do anything other than signing up with FDM.
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.
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.
Questions d'entretien [1]
Question 1
Tell me about a time you've had a disagreement with a colleague, how did you resolve this?
J'ai postulé en personne. Le processus a pris 2 semaines. J'ai passé un entretien chez FDM Group (Toronto, ON)
Entretien
OA then HR then a group interview. Not very technical. The OA is easy. The HR call is basiclly just going over your resume, The group interview is like a case study.