Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso FDM Group (Houston, TX) nel mese di apr 2022
Colloquio
Three stages after application:
1. Phone interview with recruiter
- they want to make sure you understand the company and want to know a little about you and your interest in the job.
2. Online assessment -
This consists of two parts a technical assessment, mine was 20 questions and 45 minutes to complete. Basic OOP, SQL, problem solving, and Unix.
The second portion consists of 5 video recorded questions that are strength based. They are looking for you to not only give an answer but provide a personalized example of an experience related to the question.
3. Assessment day- either virtually (which I had) or in person. They give you a presentation and then you complete another technical assessment and behavioral assessment. However if you do well enough on the online assessment you only have to do the behavioral.
Domande di colloquio [1]
Domanda 1
When is a time you had a setback and how did you overcome it?
Ho presentato la mia candidatura di persona. Ho sostenuto un colloquio presso FDM Group (Toronto, ON) nel mese di giu 2026
Colloquio
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.
Domande di colloquio [1]
Domanda 1
Tell me about a time you've had a disagreement with a colleague, how did you resolve this?
Ho presentato la mia candidatura di persona. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso FDM Group (Toronto, ON)
Colloquio
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.
Le migliori aziende per "stipendio e benefit" vicino a te