Fleetio logo

Fleetio Software Engineer Interview Questions
& Process

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

Based on 7 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
42.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Fleetio.

Showing 3 of 7
Fleetio logo
Fleetio

Software Engineer

Engineering · nearly a year ago

Senior Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Offer
Interview formats
Behavioral Technical

The hiring manager interview felt less about my resume and more like a generic quiz, asking questions I felt I had already answered. I didn't have high hopes because the role has been open for 3 months and is remote in the US, Canada, and Mexico. It seems like their hiring process is either broken or they're searching for an exceptionally rare candidate.

Confirmed questions1 question
  • Can you describe an instance where you mentored an individual?
Fleetio logo
Fleetio

Senior Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical Coding

It started with a recruiter call, then a behavioral chat with the engineering director. Both went great, and I got to talk about my experience with tech Fleetio wants to use. Next was a take-home test expected to take 6-8 hours. They usually have a follow-up to discuss design choices, but I didn't get that. They pay for the take-home, but their code review is super picky. My advice: add tons of comments and really study their existing code style before you start so you can match it.

Confirmed questions1 question
  • Build an integration with their API within a provided Ruby on Rails project skeleton, incorporating approximately 7 distinct features and bug fixes.
Fleetio logo
Fleetio

Software Engineer

Engineering · more than a year ago

Senior Average Positive experience Decline offer 5 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding Presentation

I applied and they reached out, kicking off the interview process. First, there was a 30-minute chat with the hiring manager and an engineer. It wasn't super technical, but they asked about Rails and general development stuff. After that, I got an email with a take-home assignment, which they actually paid me for. Once I finished it, they set up another call to go over the code with a group of engineers. That seemed to go well, and the feedback was pretty good. The final stage was a meeting with the CEO and CTO, mainly to talk about culture and the offer details. I ended up declining the offer because I had another one that fit me better, but Fleetio seems like a really cool place to work.

Confirmed questions1 question
  • Any questions about databases, Rails, and some DevOps topics?

Fleetio Software Engineer Interview Questions

Quoted word for word from Fleetio interview reports.

Build an integration with their API within a provided Ruby on Rails project skeleton, incorporating approximately 7 distinct features and bug fixes.

Read reports

Any questions about databases, Rails, and some DevOps topics?

Read reports

Can you describe an instance where you mentored an individual?

Read reports

Can you tell me about a project you worked on recently that involved React?

Read report

Formats, difficulty and experience

Across all 7 Fleetio interview reports.

Interview formats

Technical 33.3%
Coding 33.3%
Behavioral 26.7%
Presentation 6.7%

Interview difficulty

Easy 0%
Average 71.4%
Difficult 28.6%

Candidate experience

Neutral 14.3%
Negative 42.9%
Positive 42.9%