
Own Company Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Own Company.
Software Engineer
The interview process started with a quick 15-minute chat with the recruiter to go over some basic stuff about me. Then there was a 30-minute tech assessment, which was pretty intense with a really tight time limit for each question, so no mistakes allowed. After that, I had an hour-long interview that was split into two parts: the first 30 minutes was a coding assessment with one interviewer, and the next 30 minutes was with another person where we talked about a puzzle and I had to come up with an algorithm for it. The final round was a 30-minute behavioral interview. The recruiter kept in touch after each stage.
- Can you share an instance where you had a disagreement with a teammate and explain how you resolved it?
Software Engineer
We started with about 15 minutes of introductions about me, the company, and the role. Then, we spent 10 minutes discussing my previous work experience. Following that, there was a 30-minute technical exercise. Finally, we wrapped up with a short discussion about my career aspirations and my motivations for seeking a new opportunity.
- Can you outline the high-level design for a library system that allows librarians to categorize books and provides search functionality for guests, including the necessary services, components, and data model?
- How would you ensure the security of this library system?
- What is the expected performance of the described solution, and how can it be analyzed?
Software Engineer
This NJ-based Software Engineer role had a few interview stages. First, I spoke with the hiring manager, then a senior software dev. The final stage was an onsite interview with two team members. There wasn't any coding, system design, or 'tell me about a project you built' questions. Most interviews were vocab trivia and pretty easy, except for one. One team member, Dan, conducted a super tough interview. He was kind of like that disliked professor from college, very opinionated. If your answer wasn't good enough, he'd push for a better one. Everyone else was really nice though. The office itself is nice, but it's in a NJ suburb, so you'll definitely need a car to get around.
- Can you explain the distinction between high availability and fault tolerance?
Own Company Software Engineer Interview Questions
Quoted word for word from Own Company interview reports.
“How does the garbage collector function?”
Read reports →“Can you explain the distinction between high availability and fault tolerance?”
Read reports →“Can you explain heap and stack memory?”
Read reports →“Tell me about manipulations of strings in array”
Read reports →“How would you ensure the security of this library system?”
Read report →“What is the expected performance of the described solution, and how can it be analyzed?”
Read report →“What are your thoughts on DB”
Read report →“Can you outline the high-level design for a library system that allows librarians to categorize books and provides search functionality for guests, including the necessary services, components, and data model?”
Read report →“Tell me about multi-threading.”
Read report →Formats, difficulty and experience
Across all 12 Own Company interview reports.