
Owlet Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 26 interview experiences · FREE TO READ
Which role are you interviewing for?
16 roles · 26 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Owlet.
Software Engineer
It was a nice process overall. It started with a recruiter call, then a hiring manager chat that didn't involve any coding. After that, there was a 4-hour virtual onsite, which included a system design discussion, two coding tests, and a session focused on leadership and behavioral aspects. The process concluded with a background check and an offer.
- Can you share some details about your past projects?
- What was your specific contribution to those projects?
- What obstacles did you encounter while working on your projects?
Software Engineer
Overall was a pretty pleasant interview experience, everyone seemed pretty happy in their job. They could set expectations for the individual sessions more clearly. The sessions went Recruiter screening, technical screening, technical session, architecture session, and cross functional session. A few days after the final session, I got a random call asking for my salary expectations. The next day I received a canned rejection email with no feedback. I'm assuming my expectations were too high for them. After going through the entire interview process they could have at least called.
- Do you have any behavioral questions?
- Do you have any technical questions?
Director of User Experience
Applied online after seeing a post on LinkedIn. Reached out to the recruiter who posted the role to let her know I applied and within 2 minutes got an invitation to speak with a more senior recruiter. That call went well and she set up an interview with the product director. That call got rescheduled the day of because of some meeting. I finally met with him and had what I thought was a good call. He asked if I had any experience launching a physical product as the others he had interviewed did not. I do. I helped launch a whole line of products. Fast forward a week. Heard nothing back so I reached out to the recruiter. She said she had no news, good or bad. So I waited another week and reached out. Same reply. Then 6 days later she wrote to tell me they were putting the role on hold till November. But 6 days later (October 26th) she wrote to tell me that the role was given to another candidate. I feel there was deception in her replies to me.
- Tell me about your experience launching physical products, as opposed to digital ones.
Marketing
This interview experience was similar to others around the same time. It felt very unprofessional; the interviewer seemed unprepared and was unprofessional in responding to emails or following up. I even tried reaching out to the recruiter on LinkedIn, but they read my message and ignored it. I was kept waiting for months, and then they put the whole role on hold. There were too many red flags, especially for a company that appears so promising from the outside. Perhaps it's just the marketing team, but they really need to get organized. It was a mess and frankly rude to treat people this way.
- Tell me how you perceive our brand.
Owlet Interview Questions
Quoted word for word from Owlet interview reports.
“Can you explain the difference between ISO 27001 and NIST?”
Read reports →“Describe concurrency”
Read reports →“Could you tell me the time complexity of this specific method?”
Read reports →“Build a web application using a specific API.”
Read reports →“Can you list the three core components of an FMEA?”
Read report →“What is ARC?”
Read report →“How do you collect customer feedback?”
Read report →“Tell me how you perceive our brand.”
Read report →“How do you manage conflicts or differing opinions within a team?”
Read report →Formats, difficulty and experience
Across all 26 Owlet interview reports.