Application Process & Interviews at IMC Trading Australia

As usual, it starts with an online application where we upload a resume and cover letter. Then, HR will contact you for further online assessments such as coding challenges, cognitive test, phone and video interviews. After that we get to go to the office for a couple of interviews: in-person coding test, technical and behavioural interviews.

Interview process is standard for the field. A short, more casual initial interview followed by behavioural and skills-based interviews, plus some tests to see performance under pressure.

First few assessments are a mix of technical and behavioural. After that there is a programming assessment done with another interviewer and then a super day

An programming online assessment followed by a series of technical and behavioural interviews

I applied as an intern, which involved an online coding test, a video interview which involved answering pre-written questions, and a set of five interviews.

Several (>5) stages ranging from coding problems, behavioural interviews, and what seemed like IQ tests (cognitive challenges assessing things like memory, problem solving, thinking under pressure).

Quite thorough, but always communicative and definitely sold me.

Online coding assessments, followed by a HR screening. Then moved to a 2hr technical interview. Afterwards, was flown to Sydney to complete a technical and behavioural interview on site. No group interviews.

Resume, coding screen, phone interview, video interview, final round in person interview

There were a lot of steps in the interview process. An online coding test, an online aptitude test, introductory phone interview, recorded interviews, pair programming exercise then in person behavioural and technical interviews.

Six stages of rounds. Both puzzle and in person behavioural and technical interviews

Aptitude test - SRE Hacker Rank - Video Interview - Technical Interview 1 - Technical Interview 2 - Behavioural Interview

It depends on the type of interview. For the technical interviews, the questions assess my technical skills and experiences related to the role that I applied for. For the behavioural interviews, the questions are more about why I applied for this role, how I react in different difficult work scenarios, my strengths and weaknesses, and other common behavioural questions.

You are described a game with certain rules and a point system. Learning that certain actions result in a certain number of points, how many points would be scored if the actions were weighted differently?

Trading, math, probability related questions.

Primarily questions that tested my development skills and problem-solving ability. One interview was a behavioural interview, where I was asked about my experiences working in a team and solving specific problems.

In the main technical station, I was given a system to design data structures for, and asked to talk through my design decisions.

In depth technical interview to find out how I'd approach a practical problem. Other questions to gauge my general technical knowledge too.

Mostly focusing on sofware engineering proficiency and data structures and algorithms, as well as the standard STAR style behavioural questions.

Standard technical computer science problems

Quite a few programming exercises that were focussed on algorithms and data structures. They wanted to get to know me as a person, there is a fairly specific type of person that fits into the IMC culture and there is quite a bit of effort put into identifying if you are that type of person.

Just be your genuine self during your interviews, people want to assess you as you. Don't worry too much if you don't meet a few of the qualifications listed, just give it a go if you think you're going to be a good fit for the company. Also always remember that you're also assessing the company during your interviews as you get the final say of whether to accept or reject the job offer.

Learn about the company, the field it operates in AND its particulars. Learn about the products so you have a working knowledge of the basics. It'll give you a huge head start because you'll know what's going on as soon as you walk in the door.

Prepare for probability questions.

I would recommend to review computer science basics like data structures and algorithms

Have a good understanding of the fundamentals of development. Learn and practice an approach to solve problems.

Revise data structures thoroughly, and practice whiteboarding your design ideas. Being able to talk through your process is more important.

Have a strong understanding of the language you are interviewing in (C++ or Java) as well as the data structures and algorithms.

Be personable and not robotic in the interview. Show that you are quick to learn and easy to work with.

From a technical perspective, study up on your algorithms and data structures (and maybe revisit how to interpret statistical graphs). From a behavioural perspective, just be yourself, and try your best to get along with everyone.