Very lengthy (expect it to take around 8 hours plus scheduling time). The gates at each step should stop you sinking too much time into it unless you get rejected after the final step like I was. - Recruiter screen - Take home test (very minimal feedback when evaluated suggests they either do pass/fail, or just do a cursory inspection of your code) - Psych eval and discussion - Panel interview (weirdly, unrelated to your technical test submission or the niche skill they were looking for) I've selected easy for "interview difficulty" but don't interview with them unless you're set on working for a consultancy. In which case, make sure you find out exactly what they're looking for before interviewing. Interview went pretty well, but rejected due to not having experience with a niche skill they didn't specify was a core requirement for the job. The gates at each level don't help you out if this is the case. They're going to market to get engineers to fit into specific roles, but aren't being up front with candidates about it due to a very rigid interview process. Not a complete waste of time, but the lack of transparency was disappointing.

Had around 4 interviews and in the end got declined after the meeting the team where they were asking dump questions just because they have been asked to do so and they didn't seem interested in interviewing engineers. and the excuse was the team didn't find me suitable for the job which I have many certs qualifies me. It was totally waste of time and will never apply again.