Ho presentato la mia candidatura online. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso FDM Group (Toronto, ON) nel mese di nov 2021
Colloquio
The overall interview process was quick and easy, though the person doing the behavioural was pretty rude (their audio kept cutting off and they didn't even turn on their video! When I said I couldn't hear them you can hear they got pissed. They were very dismissive and you can tell that they didn't want to be there)! The rest of the interviewers and the recruiters pretty nice and helpful. The recruiter send you emails frequently about any updates and also what sort of Qs you should study for the interviews. The tech interviewer helps you out if you forget a question or don't know it.
I got the first call for an interview a day after I applied for the role online. You have 1 telephone interview, 1 technical assessment, 1 pre-recorded interview, 1 behavioural interview, and 1 tech interview respectively.
After the initial phone interview, they schedule you for a technical assessment and a pre-recorded interview , if you pass that you're scheduled for a behavioural interview (20 mins) and a technical interview (30 mins) on MS Meets/Zoom.
Domande di colloquio [1]
Domanda 1
Initial Phone Interview:
- When can you start?
- Are you open to relocation?
- When did you graduate?
- What was your GPA?
- Tell me about yourself and your background/work experience
- Tell me about a project you've worked on
- Tell me about a problem you came across during work, and what did you do you fix it?
- Why are you interested in tech/IT?
Technical Assessment (60 mins, 50Qs):
Questions on SQL, Java, Data Structures, Unix/Linux
Pre-recorded Interview:
- What do you do if you are close to the deadline and still have a few tasks left? What you do if you have a deadline and you are behind?
- How do you deal with a new situation? How do you adapt to a new situation?
- When was the last time that u had a set back and how u took it positively?
- What is your hobby? Tell us about it.
Behavioural Interview (Video call):
- What role did you apply for?
- Why did you choose IT/the role you applied for?
- Where do you see yourself in 3-5 years?
- What is your biggest weakness?
- What languages, tools, and software have you used?
Technical Interview (Video Call with tech instructor):
- Pillers of OOP
- walk me through creating a code for storing a list of items
- method overloading vs method overriding
- bash commands/unix commands
- select statements and creating a relational db (e.g. table called customers, table called orders)
- cloud computing Qs (BUT only because I mentioned in knew it in my resume - otherwise they don't ask them unless you apply for DevOPs position)
- SDLC, Scrum, Agile environment, Networking Qs
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
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?
