On logo

On Software Engineer Interview Questions
& Process

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

Based on 13 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
46.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at On.

Showing 3 of 13
On logo
On

Software Engineer

Engineering

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

This was a great interview process, super professional and the recruiter was awesome, keeping me updated and making sure I was good to go. They even set up extra chats with team folks so I could feel good about my choice. Everyone was nice and it felt more like a chat than a typical interview, which was cool. The process itself was pretty standard: First, a recruiter chat. Then, a call with the engineering manager. After that, a technical interview with an algorithm challenge and some technical questions. Finally, a 2.5-hour session with different people from the team, including the head of engineering, product folks, and a software engineer, where they asked questions about situations, behavior, how I'd fit in, my soft skills, and values.

Confirmed questions8 questions
  • Could you tell me why you're interested in On?
  • Tell me about your thoughts on backend architecture.
  • What's your experience with our tech stack?
On logo
On

Software Engineer

Engineering

Senior Easy Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen
Interview formats
Behavioral Coding

Started with a 30-min recruiter intro call. Although I no longer use the tech On is using, the recruiter suggested me to continue. Then 45 minutes with the hiring manager. He ran out of questions after 20 minutes but I guess we both felt comfortable and happy with each other. Once again, he mentioned they don't care about the language as much and wanted me to proceed. Then it was a 90-minute live coding with two engineers. I chose to use the language I currently focus on instead of my previous main language (which On is using now). The interview went rather smoothly and the interviewers were super helpful and friendly, I felt like they could be great teammates to work with. However, I did say that I'm only willing to switch back to the previous tech stack if the offer is irresistible. After a week of waiting, another HR contacted me on a Thursday to book a quick call the Tuesday after. With another 5 days of waiting, she called me for 3 minutes telling me they wanted someone willing to code in their current language and rejected me. I simply do not understand why they insisted on carrying on with the process even if I asked many times about the tech stack and, more importantly, for booking an appointment of a 3-minute-worth rejection call with a 5-day gap (as if they were waiting for someone first?).

Confirmed questions2 questions
  • Can you explain how to design an LRU cache?
  • What are your thoughts on the comparison between programming language A and B?
On logo
On

Software Engineer

Engineering

Entry Easy Negative experience Accept offer 1 round
Interview process
Recruiter call Offer
Interview formats
Behavioral

The interview was nice and pretty straight forward. They sent me an offer for a freelance contract few days after. I was in discussion with another company and they urged me to give them a reply right now. I accepted 24 hours after their original offer. They just said after to the headhunter they changed their mind. It was truly disrespectful toward me and really showed a princess attitude.

Confirmed questions1 question
  • Can you tell me about your most recent experience with Typescript?

On Software Engineer Interview Questions

Quoted word for word from On interview reports.

Given a string with various types of brackets, determine if the brackets are balanced.

Read reports

What are your thoughts on the comparison between programming language A and B?

Read report

How would you approach debugging issues in a live production environment?

Read report

Formats, difficulty and experience

Across all 13 On interview reports.

Interview formats

Behavioral 44.8%
Coding 24.1%
Technical 24.1%
System Design 3.4%
Presentation 3.4%

Interview difficulty

Easy 23.1%
Average 69.2%
Difficult 7.7%

Candidate experience

Negative 38.5%
Positive 46.2%
Neutral 15.4%