Candidatei-me por meio de uma faculdade ou universidade. O processo levou 3 meses. Fiz uma entrevista na empresa FDM Group.
Entrevista
Very proactive recruitment - they call you, send emails. They clearly have experience recruiting a large number of graduates. They had an organised structure to the day - welcome talk, interviews, and then tests.
The interviews were 'competency' based, but felt quite impersonal because they would ask scripted questions and give no indication of how detailed your answer should be.
The tests were typical of psychometric tests, but also had a multiple choice test more specific to the role.
Overall I got the impression (along with other candidates I spoke to) that we were just one of the thousands of graduates they recruited for and were not individual.
Their pay offer is poor for a graduate scheme, basically keeping you stuck with them for two years even if you're working for a high profile client. If you want to leave within that time they threaten to charge you for the 'training' you received. Not a great impression. You are also NOT guaranteed a job even when you accept their offer because they need to find you a placement and so you may be stuck for months without pay waiting for them. You also do not get paid during their months of training.
In short, they are a recruitment company tying down desperate graduates for two years with the chance that they get to work with a top employer on a low salary.
Candidatei-me pessoalmente. Fui entrevistado pela FDM Group (Toronto, ON) em jun. de 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.
Perguntas de entrevista [1]
Pergunta 1
Tell me about a time you've had a disagreement with a colleague, how did you resolve this?
Candidatei-me pessoalmente. O processo levou 2 semanas. Fiz uma entrevista na empresa 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.
As melhores empresas na categoria “Remuneração e benefícios” perto de você
