I applied online. The process took 3 weeks. I interviewed at FDM Group (Londres, Inglaterra) in Jun 2016
Interview
I had a video interview which had 4 questions, tell us about yourself, why do you want to work for FDM and two more I can't remember.
Passed this, got called for assessment centre - there was an hour or so long talk which you could ask questions during, then three 5 minute 4 question interviews, all very quick-fire questions, some weird ones like Apple or Android? Asked about motivation for role is change at a company always a good thing? Then had 3 tests, Venn diagram test, Maths (GCSE level) and IT Aptitude test - 1 immediately after interview, the other 2 after lunch (wasn't provided, had to go out but you're in central London so plenty of places). About 80% of the questions across all the tests can be answered if you just work through the question, only a few in the IT Aptitude test required some background knowledge like what does SQL stand for. There was an office tour between the second and third test. Started 9 am left about 4 pm, so a long day. People there seemed pleasant and having fun whilst they worked. The offered salaries are very low especially if you get work in London where price of accommodation is huge (21.5k first year, 25k second year).
Interview questions [1]
Question 1
Apple or Android?
Is change at a company always a good thing?
What would you describe as a successful outcome of this programme?
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
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?