Straightforward: They initially require an which is logic based. You must answer as many questions as you can in 15 mins. The following round is a recorded interview. You are allowed two attempts per questions, note that internet issues may waste one of those attempts. The questions themselves are not very difficult and often featured in many interview prep books. The next round is either a phone screen with a recruiter or a rejection letter. I believe the next round consists of a on-site interview, which is the last.

I was contacted very quickly to do a online skills test. Then around 4 to 5 days later there was an phone interview. A week after I was notified that I was not selected for the position. During the phone interview I was told I was being interviewed for Entry-Level Quality Assurance (QA) Engineer position. Which I then notified the Interviewer that I applied for Entry Level Software Engineer position and he said it was fine and the Interview went on as normal. Wasn't anything too hard, but it was my first professional interview being fresh out of University and I don't think I did enough homework. I did searches afterward and there where references to similar questions and how to answer them effectively and I kinda dropped the ball. I take that as a learned lesson for future endeavors. Overall, what turned me off to the Company was how during the process I just felt like another number. Not knowing what position I applied for, not giving simple feedback, just going through the motions. I understand some interviewee's can be hard to deal with and a lot of the generic responses we get are to protect the company from lawsuits. I don't think it wouldn't hurt to tell failed candidates how they can improve on future interviews if they ask.