Clio logo

Clio Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 65 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
58.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Clio.

Showing 3 of 65
Clio logo
Clio

Software Developer

Engineering · a year ago

Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Coding System Design

Applied via Linkedin. Got a standard rejection, but the recruiter reached out later saying it was a mistake on their end and proceeded. The first round was a recruiter chat, followed by a live coding assessment. The coding question was about permutations and combinations, which would be average if prepared, but I couldn't finish on time. The third round, on the same day, was a system design interview that lasted an hour. I found the system design question easy because I'd seen it before. Both interviewers were nice.

Confirmed questions2 questions
  • Practice DSA coding challenges
  • Practice system designs
Clio logo
Clio

Software Engineer

Engineering · more than a year ago

Intern Average Positive experience Accept offer 4 rounds
Interview process
Take home Recruiter call Technical screen Onsite
Interview formats
Coding Behavioral Technical Behavioral

So the interview process had 4 parts. After they screen your resume, if you make the cut, you do an online coding assessment. You can use whatever programming language you want. If you ace that, you get to have an HR interview. Then, if that goes well, you do a paired programming interview with a senior dev or manager to see how you think and solve problems. The last part is a culture fit interview, where you meet and chat with someone higher up. This part isn't really about your technical skills anymore, since those were already checked, but more about you as a person and if you'd fit in.

Confirmed questions1 question
  • What makes you want to join Clio?
Clio logo
Clio

Software Developer

Engineering · more than a year ago

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Group
Interview formats
Coding Technical Behavioral Behavioral

The whole thing took about two weeks. First, I had a quick phone call with the recruiter. Then, I did a virtual on-site which was four parts and took about 3 hours and 15 minutes. It included a 45-minute pair programming session where I had to write a console app to parse a file. After that, there was a 1-hour technical deep dive where I discussed a past project and my technical knowledge. Then, a 1-hour session on technical leadership. Finally, a 30-minute culture meeting to talk about values. The recruiter was really nice and responded within 2 business days.

Confirmed questions4 questions
  • Can you write a console app to parse a CSV file of names and shuffle them so that no name ends up in its original position?
  • Could you discuss a significant project you were involved in, focusing on the technical aspects?
  • Tell me about your experience with technical leadership.

Clio Software Engineer Interview Questions

Quoted word for word from Clio interview reports.

Is there a question about verifying if a DNA strand is valid based on given rules regarding letter sequences?

Read reports

Could you create a Secret Santa randomizer that makes sure no one gets a gift from someone they are also giving a gift to?

Read reports

Can you write a console app to parse a CSV file of names and shuffle them so that no name ends up in its original position?

Read reports

Could you write a program with a UI that draws a path on the screen given start and end coordinates (x1,y1 to x2,y2)?

Read reports

How would you read file contents and manipulate an array of objects with duplicate data so that each value appears only once?

Read report

Which office location, Calgary or Vancouver, would you prefer to work in?

Read report

Can you share a real-time challenge you faced with an Azure migration?

Read report

Could you share the values that guide you both personally and professionally?

Read report

Formats, difficulty and experience

Across all 65 Clio interview reports.

Interview formats

Behavioral 34.1%
Coding 25.3%
Technical 25.3%
System Design 11.5%
Presentation 1.6%

Interview difficulty

Easy 12.3%
Average 76.9%
Difficult 10.8%

Candidate experience

Negative 23.1%
Positive 58.5%
Neutral 18.5%