I applied online. The process took 4 weeks. I interviewed at FlexTrade Systems Inc. in Jan 2023
Interview
Ask to solve OA first, then setup technical interview date with HR.
Technical interview is 60 mins where you're asked to finish 3 LC questions(easy, med).
The interview process is very monotonic because you do not receive any feedback/clarification from the interviewee when you directly ask them something.
Also, the questions jumps from topic to topic, like they literally parse entire question from LC.
Eg. After explaining what you're going to do, you ask can you proceed to code.
Interviewee: .......
Manage to solve 3 problems, 1 unoptimized and is rejected 2 weeks after.
Very unprofessional and feels like a waste of time interviewing with them.
I interviewed at FlexTrade Systems Inc. (Milwaukee, WI)
Interview
Exam was very difficult. The hackerank does not allow you to use any outside resources and I was unable to recall syntax for functional programming which was listed as a small requirement on the application.
I interviewed at FlexTrade Systems Inc. (London, England) in May 2026
Interview
First took me through an intro call, which was simple enough explaining my career from start to finish. I'm a junior dev, so I focused mainly on my one previously role, talked about arch, day to day and core language uses and application.
Recieved a private LeetCode link to complete within 7 days, was told 2 hours to complete but the LeetCode timer was set to 3 hours.
Passed 4/5 test cases, took 2h27 to submit the single question. Did a bit of digging after submitting - found this specific problem was not public. Really enjoyed the challenge, but my code must not have been flexible enough (that fifth test case failing caught me so bad and I couldn't get my head round it annoyingly - big fluster). Did not receive next round invite.
I applied online. The process took 2 weeks. I interviewed at FlexTrade Systems Inc. (London, England) in Nov 2025
Interview
Had a quick call with HR about the process, then sent a HackerRank (which could only be done in Java) easy(ish) lc. Then a half an hour behavioural interview with a senior engineer, before on-site which was 2 hours or so, another simple Java problem on the whiteboard, a simple math/data structure problem, and then general behavioural and team experience questions, from engineers on the team and then with the team lead. Rejected a couple days later, said other candidates were a better fit.
Interview questions [1]
Question 1
Do you like working in a small team? Have you ever done a project where you've owned the whole stack end-to-end? What's your process for debugging something? Tell me a time you had to manage conflict.