Owner.com logo

Owner.com 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

4 Rounds average
Easy Typical difficulty
38.5% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Owner.com.

Showing 3 of 13
Owner.com logo
Owner.com

Software Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Onsite Onsite Phone screen
Interview formats
Behavioral Technical System Design

The interview process involved a recruiter call, a call with the CPO, a tech interview, an application design interview, a teamwork and collaboration interview, a project deep dive interview, and a final call with the CEO. Even though it was a lengthy process, it was the best software engineering interview experience I've had. They didn't ask any LeetCode problems or generic system design questions like 'design Twitter'. Instead, the interviewers seemed genuinely interested in understanding my skills, how I think, my past experiences, and my personality. Everyone I spoke with was nice, supportive, and really considerate of how I was feeling, which helped me do my best. I'd totally recommend this process!

Confirmed questions1 question
  • Can you share an instance where you navigated disagreements about technical architecture?
Owner.com logo
Owner.com

Senior Software Engineer

Engineering · a year ago

Senior Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation Background check Offer
Interview formats
Technical Coding Behavioral System Design Presentation

Recruiter and coordinator were super friendly and responsive. Started with a recruiter call, then a one-hour technical round. After that, a virtual onsite which included a values interview with a Product Manager, a project leadership/experience interview with the VP of Eng, and a system design interview. The recruiter texted me a few hours after the onsite, excited to move me to the next step which was a 45-minute chat with the CEO. Since it was just before Thanksgiving and I was really interested, I went ahead and did a prep call for it. We planned to schedule the CEO chat for the next week or the one after, as I was still interviewing elsewhere, which the recruiter asked about nicely. The next week, the recruiter texted me that they wouldn't be proceeding with my application. My advice to potential interviewees: keep things professional and over email, and know that the process might not be super well-defined.

Confirmed questions2 questions
  • Could you compute the cost associated with food orders and inventory consumption?
  • Design a database schema that can handle flexible menus and orders, akin to systems like Doordash and UberEats.
Owner.com logo
Owner.com

Software Engineer

Engineering

Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding

The interview process was great until the final stages. The questions were practical, and everyone I interacted with, from the interviewers to the recruiter, was really nice, helpful, and supportive. However, my impression changed when I interviewed with the CTO, Dean. It seemed like he was doing other things during our conversation because he kept looking away and his follow-up questions were things I had already covered. This significantly impacted my view of the company. I was considering withdrawing from the process, but then they stopped responding, so it kind of worked out mutually.

Confirmed questions2 questions
  • Asked simple questions about procedural programming.
  • Asked questions related to semi-realistic use cases.

Owner.com Software Engineer Interview Questions

Quoted word for word from Owner.com interview reports.

Design a database schema that can handle flexible menus and orders, akin to systems like Doordash and UberEats.

Read reports

Could you compute the cost associated with food orders and inventory consumption?

Read reports

What data structure would you use for a restaurant menu, and can you write some functions to implement it in CoderPad?

Read report

Could you determine if there's sufficient pizza topping inventory to fulfill all given orders based on requirements and timestamps?

Read report

How would you determine the best strategy for accepting or rejecting store orders to maximize profit?

Read report

Can you share an instance of difficult feedback you received from a manager?

Read report

Formats, difficulty and experience

Across all 13 Owner.com interview reports.

Interview formats

Behavioral 28.9%
Technical 23.7%
Coding 21.1%
System Design 18.4%
Presentation 7.9%

Interview difficulty

Easy 38.5%
Average 38.5%
Difficult 23.1%

Candidate experience

Negative 38.5%
Neutral 23.1%
Positive 38.5%