Treatwell logo

Treatwell Software Engineer Interview Questions
& Process

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

Based on 8 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
62.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Treatwell.

Showing 3 of 8
Treatwell logo
Treatwell

Senior Software Engineer

Engineering · nearly a year ago

Senior Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

The hiring process was pretty simple. It had three interviews. First, an HR interview. Then, an interview with an Engineering Manager and a Product Manager where they asked behavioral questions about task prioritization, stakeholder relationships, handling team conflicts, and best practices. It felt more like a chat than a formal interview. Finally, a technical interview. This was a live coding session with two engineers, followed by technical questions. The coding exercise involved drawing shapes in the console, which wasn't hard, but they cared about good practices, testing, and clean code. The technical questions covered the usual backend stack, including OO, REST, Spring, and some system design concepts. They were really talkative and supportive during this.

Confirmed questions5 questions
  • What's your approach when a deadline is at risk of being missed?
  • Describe how you'd manage a team disagreement.
  • What criteria do you consider important during a code review?
Treatwell logo
Treatwell

Software Engineer

Engineering

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

The interview process was well-organized and gave a good sense of the role. It started with a CV review, then a chat with the Engineering Manager, followed by a coding challenge and a review with team members, and ended with an interview about collaboration and situational questions. Each step felt important and the people were friendly, open, and professional. It was one of the best processes I've seen. Maybe better communication during longer breaks between stages would be good, but I get that internal changes were happening, so it was fine. All in all, it was a great experience.

Confirmed questions1 question
  • What would you do if a teammate's performance suddenly declined?
Treatwell logo
Treatwell

Software Engineer

Engineering

Entry Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

I had a 30-minute video call with a recruiter first, then a technical interview with a manager. The manager was late and didn't apologize. During the interview, he just read questions and wrote my answers. I heard back the next day with a rejection, no feedback given.

Confirmed questions1 question
  • Tell me about an accomplishment you are most proud of.

Treatwell Software Engineer Interview Questions

Quoted word for word from Treatwell interview reports.

Could you explain the difference between equals() and hashcode()?

Read reports

Can you explain REST and demonstrate creating a Spring endpoint?

Read reports

What would you do if a teammate's performance suddenly declined?

Read reports

How would you approach this using Test-Driven Development?

Read report

What criteria do you consider important during a code review?

Read report

Walk me through the entire flow from a user clicking an interface button to receiving a response.

Read report

Formats, difficulty and experience

Across all 8 Treatwell interview reports.

Interview formats

Behavioral 39.1%
Coding 26.1%
Technical 21.7%
System Design 13%

Interview difficulty

Easy 25%
Average 62.5%
Difficult 12.5%

Candidate experience

Positive 62.5%
Negative 25%
Neutral 12.5%