Me postulé a través de una facultad o universidad. Acudí a una entrevista en FDM Group
Entrevista
The interview felt a bit sketchy. I applied through my campus and received an invitation for phone interview a while ago. A few red flags with the interview. First, the interviewer requested a last minute schedule change, which is totally unexpected. I agreed to the schedule change, but had to actually call in to remind the interview. Second, the recruiter seemed she knew nothing about the position. I noticed that because there were a lot of awkward silences / waiting for her to respond. A strong feel that she was reading questions off a piece of paper. Also had to end up explaining to her the summary of the job and requirements. Third, when the interview was over, the recruiter reached out days later requesting the exact same interview. Had to explain to her the interview was already finished, which she realized it upon double checking. Still can't believe a recruiter from some consultant company lacks basic skills as an interviewer. Overall, the interview felt very bland and unprosessional.
Preguntas de entrevista [1]
Pregunta 1
Explain to me the position and why you are interested.
Me postulé en persona. Acudí a una entrevista en FDM Group (Toronto, ON) en jun 2026
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Tell me about a time you've had a disagreement with a colleague, how did you resolve this?
Me postulé en persona. El proceso tomó 2 semanas. Acudí a una entrevista en FDM Group (Toronto, ON)
Entrevista
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.