I applied online. The process took 2 months. I interviewed at FDM Group (Singapour) in Mar 2017
Interview
Quick interview. Very easy questions. After being told I was in the program and not given a contract, the hiring manager cut all contact.
The Singapore recruiter would not reply to any emails at all regarding start dates/pay specifics. Did not answer direct calls, until I called the company and someone sitting next to the recruiter picked up and handed her the phone. She told me she would not be able to answer my questions and will call upper management and then ring me back. I never received any communication back until weeks later when she emailed asking if she could call the next day. I said ok. She never called the next day... A week later I get another email asking when I could be called, I replied but again never got a call.
Very unprofessional hiring process.
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
