
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
Candidate interview experiences
First-hand accounts from people who interviewed at Owner.com.
Software Engineer
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!
- Can you share an instance where you navigated disagreements about technical architecture?
Senior Software Engineer
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.
- 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.
Software Engineer
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.
- 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.
“Write Typescript code to handle an online order.”
Read reports →“How would you design a database table for an online menu?”
Read 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 →“Could you design a restaurant menu?”
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.