Ontop logo

Ontop Interview Questions
& Process

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

Based on 43 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
67.4% Positive experience

Which role are you interviewing for?

24 roles · 43 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Ontop.

Showing 4 of 43
Ontop logo
Ontop

Android Developer

Engineering · nearly a year ago

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

I was sent an Android challenge to do in Jetpack Compose. It can be done in a day or two. They ask for some silly things like 'you can't use toUppercase functions' among others. Then the engineering lead interviews you and asks more general questions related to work experience. They take forever to respond. The HR interview was bad, zero tact.

Confirmed questions1 question
  • How much experience do you have as a developer and/or technical lead?
Ontop logo
Ontop

Account Executive

Sales · more than a year ago

Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Phone screen Presentation Onsite
Interview formats
Behavioral Technical Presentation

So there were 5 rounds in total. First was a screening with HR, then I had a first round with the hiring manager. After that, there was a second round with the Team head. Then, I had to present a ppt which was given by the hiring manager to the hiring manager and the team head. Finally, the last round was an interview with the Global Sales head.

Confirmed questions6 questions
  • Tell me about your SQL skills.
  • Can you describe your prospecting skills?
  • What is it that we do?
Ontop logo
Ontop

Software Developer

Engineering

Entry Easy Negative experience Decline offer 3 rounds
Interview process
Recruiter call Take home Presentation Background check Offer
Interview formats
Technical Presentation

I was contacted by a recruiter from Ontop. The interview process consisted of a few calls and a take-home exercise. The take-home wasn't complicated but lacked details, suggesting they wanted us to ask for more information. Talking with the team, I learned they don't have a structured engineering setup, with each team working independently on their implementations. Later in the process, the recruiter handling my application suddenly left the company. On her last day, she messaged me saying someone else would be in touch. A few days later, a new recruiter contacted me to schedule a call. During this call, he informed me that the next step would be the contract and a background check, and he mentioned a verbal offer for much less than the initial range communicated by the first recruiter. I inquired if this could be reviewed, as it differed from the original amount discussed, and he promised to get back to me soon, asking about my availability to join. I mentioned needing to give my current employer a two-week notice, and he simply acknowledged this. Today, I received another message stating they are proceeding with a different candidate. Fortunately, I hadn't informed my current employer, as no contract was in place yet. Overall, I wouldn't recommend joining Ontop unless you're actively looking elsewhere. Their processes aren't standardized, and their salary ranges are very low for the current market. They have a new CTO who appears knowledgeable, and hopefully, he can sort out the recruiting issues.

Confirmed questions3 questions
  • What technologies and architecture do you use/prefer?
  • Can you complete a take-home assessment?
  • Can you present your solution to the take-home assessment?
Ontop logo
Ontop

UI/UX Designer

Design

Entry Average Positive experience Accept offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Other

Martha was very polite. She started by asking about my English level. Then she told me about Ontop in English, and we had a fluent conversation. After that, I spoke about my history and experience as a UX designer in English. She noticed I was a bit nervous and offered to switch to Spanish, which we used for parts of the conversation. It was a nice chat. She concluded by saying she'd be in touch regarding the process outcome, and I'm currently awaiting that news.

Confirmed questions5 questions
  • What is your English proficiency level?
  • Can you describe your experience as a UX designer?
  • What is your present salary?

Ontop Interview Questions

Quoted word for word from Ontop interview reports.

Could you explain the criteria for selecting between an SQL and a NoSQL database?

Read reports

What solutions would you propose for an operation dealing with fluctuating request volumes that impact account balances?

Read report

Can you schedule a call with a lead within the Ideal Customer Profile in 24 hours as a challenge?

Read report

What do you believe differentiates a senior developer's capabilities and experience from that of a junior developer?

Read report

Formats, difficulty and experience

Across all 43 Ontop interview reports.

Interview formats

Behavioral 39%
Technical 21%
Presentation 16%
Coding 9%
Case 8%

Interview difficulty

Easy 16.3%
Average 60.5%
Difficult 23.3%

Candidate experience

Negative 20.9%
Neutral 11.6%
Positive 67.4%

Reports by job function

Engineering 16
Sales 13
Design 4
Operations 3
Finance 2
Analytics 2