FreshBooks logo

FreshBooks Software Engineer Interview Questions
& Process

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

Based on 29 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
65.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at FreshBooks.

Showing 3 of 29
FreshBooks logo
FreshBooks

Software Engineer

Engineering · more than a year ago

Senior Easy Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

I went through two out of four interviews before being turned down. The two interviews I participated were pretty standard for an experienced software engineering position: 1) a screening call with a recruiter, 2) a one-on-one conversation with a technical lead on the team I was applying for. Both people I spoke to were warm and easy to speak to, and left me with a positive impression of FreshBooks, even though I didn't get an offer. Additionally, both people were _very_ forthcoming about the culture and challenges facing their company - much more so than you would usually get this early in the interview process.

Confirmed questions1 question
  • Can you explain the circumstances under which you would opt for a NoSQL database instead of a relational one?
FreshBooks logo
FreshBooks

Technical Lead

Engineering

Lead Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Group Presentation Background check Offer
Interview formats
Technical Coding System Design Behavioral Presentation

I thought I was ready for this interview, but I knew Freshbooks wouldn't hire me. This is because I had another interview with them in 2014 and they asked me the exact same questions, following the same interview path. I found the questions on Glassdoor back in 2014, and they hadn't changed a single one! I don't know if Freshbooks genuinely wants to hire people or if they're just using interviews to improve their own skills. I must admit, their skills have improved significantly since 2014 when they seemed quite beginner-level; by 2017, they were at least more professional. I won't be applying again for any position at Freshbooks (I've already tested my chances twice with them!) and I think there are better places to work. Their interview process took a lot of time (you'd think they were working on rocket science!), but I suspect the company founders are making a fortune, so they've left the company to some 'just graduated' folks to use as a sandbox. I asked them why they switched their technology from PHP to Python, and they said it was because many people in the company advocated for Python. To me, this sounds more like a decision made by junior people right out of university who want to experiment without worrying about the consequences for the company. I'd recommend applying if you have the time (and be ready for 4 rounds of interviews, yes, they have 4 rounds!), but don't expect to be hired. It's mostly good for gaining more interviewing experience, after which you can apply to a better company for your dream job.

Confirmed questions3 questions
  • Could you design a UML diagram for a parking lot?
  • Can you suggest some book titles for me to read?
  • Please discuss your experiences with Scrum.
FreshBooks logo
FreshBooks

Software Developer

Engineering

Mid Average Neutral experience No offer 3 rounds
Interview process
Phone screen Onsite Technical screen
Interview formats
Technical Behavioral Coding

The Freshbooks staff seemed very friendly, though perhaps a bit sleepy, but overall it was a good experience. What threw me off is why they've been hiring for over 2 years. With the reviews off Glassdoor and their hiring time, it seems a lot of people have been leaving and they've been struggling to replace them. The process included: 1) A phone interview, 2) A face-to-face personality interview, and 3) A technical interview.

Confirmed questions7 questions
  • Can you explain what is sent in a header request?
  • Could you list and describe the different types of REST protocols, like PUT, DELETE, POST, etc?
  • Where do you envision yourself in a few years?

FreshBooks Software Engineer Interview Questions

Quoted word for word from FreshBooks interview reports.

Can you explain what happens when you type google.com into a browser, including details about DNS and HTTP?

Read reports

Could you list and describe the different types of REST protocols, like PUT, DELETE, POST, etc?

Read reports

Describe a strategy for migrating an existing API to a new system without causing disruptions for external users.

Read report

Formats, difficulty and experience

Across all 29 FreshBooks interview reports.

Interview formats

Behavioral 34.7%
Technical 31.9%
Coding 18.1%
System Design 12.5%
Presentation 1.4%

Interview difficulty

Easy 34.5%
Average 55.2%
Difficult 10.3%

Candidate experience

Neutral 17.2%
Positive 65.5%
Negative 17.2%