Clio interview:

I applied online.

First off, the HR is really bad. They blindly send coding challenges without viewing your resume. I had a friend submit a blank resume, and they sent a coding challenge because they were pleased with their "experience and other qualifications." Another friend of mine applied, failed the coding challenge, and got rejected. They reapplied with a different email and the same resume and got sent another coding challenge, and then got an interview after successfully completing it again. The HR does not do their job, and you certainly can't count on them to help you while you work there.

Coding challenge:

• 1 question on dice rolling (use brute force)
• Simple SQL question (use joins and things like that)
• A simple debugging an array problem

HR Interview (phone, 30 min):

• Tell us about your last workplace.
• Why did you apply to Clio?
• Do you want to work in the Calgary or Vancouver office?
• Do you have any questions for me?

Coding interview (on-site, 90 min): This is a "pair programming" exercise (although it's not truly pair programming). Make an interactive tictactoe game, or make a mars rover game (simple game that moves a ship around on an xy axis and has a direction it is facing). After you are done, there are questions: "If you had more time, what would you change?" Then they will offer you suggestions on things you could add to your code and design approaches, even if they are useless/not applicable. If you don't implement any of the changes they suggest, they will not give you an offer.

Exec interview (on-site, 30 min):

• Tell me your "story."
• What team are you most interested in/what part of the product are you interested in?
• Why Clio?

The HR will ghost you if you get rejected, unless you follow up with them.

The pay for the co-op is $25/hr.

Tell me about yourself.