I applied online. I interviewed at FDM Group (Sydney)
Interview
(Note: I was based in Auckland, NZ throughout the recruitment process).
I got a phone call a couple months after I applied and it was just a casual chat; just the recruiter wanting to get to know you better. After the call, I as emailed resources on how to prepare for the interviews to follow.
This was followed shortly by a Video Interview with the same recruiter. No technical questions; purely behavioural and very doable considering the resources given prior.
Once I passed the Video Interview, there was an Assessment Centre which included one other NZer on the call and a recruiter. We were individually taken into breakout rooms. Here, we had an interview with an Account Manager followed by a Technical Interview shortly after.
The questions asked by the Account Manager is very much the same as those in the Video Interview. The Technial Interview was very very simple; I was asked about arrays.
Interview questions [1]
Question 1
Overall, the questions revolve around how you are driven, adaptable, resilient, curious, etc. OWTTE and should be answered using the STAR framework.
I applied in-person. I interviewed at FDM Group (Toronto, ON) in Jun 2026
Interview
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.
Interview questions [1]
Question 1
Tell me about a time you've had a disagreement with a colleague, how did you resolve this?
I applied in-person. The process took 2 weeks. I interviewed at FDM Group (Toronto, ON)
Interview
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.
Top companies for "Compensation and Benefits" near you