
Wyze Labs Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 41 interview experiences · FREE TO READ
Which role are you interviewing for?
27 roles · 41 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Wyze Labs.
User Experience Researcher
First, had a hiring manager screen, then a phone screening with HR. The final round was a full-day on-site in Kirkland. It started with a 1-hour UX research portfolio presentation and Q&A, followed by 5 separate 1:1s with stakeholders: Head of Design, two product people, CPO, and the HM. Some hiccups happened: HR rescheduled our meeting 3 times, and tech setup for my presentation wasn't checked beforehand, causing a 15-min delay. However, the biggest surprise was the leadership's interaction; the CPO didn't greet or introduce himself, just asked 'Why did you leave your last company?' This was a huge red flag. The questions from product and CPO after my presentation suggested they didn't fully understand UX research, yet acted like they did.
- Tell me about why you left your previous companies.
- Given this hypothetical research scenario, how would you proceed?
- You mentioned testing hypotheses, so why did you label this "exploratory" research instead of "evaluative research"?
Technical Product Manager
Started with a recruiter call, then I had to do a presentation about my past projects and a case study. After that, there were four 1:1 interviews. These 1:1s were all about the case study for their subscription product. Sometimes it feels like they're asking for free work and ideas during interviews, which I hope they change and ask for a case study outside their area. The people I spoke with were smart and knew the company's offerings and roadmaps well. In the end, they decided to hire someone internally, making all that time and effort feel wasted.
- Conduct a case study on our subscription product and propose improvements.
- Suggest ways to expand the product.
- Outline strategies to prevent churn.
Data Scientist
The interview process included an initial phone screening, followed by a meeting with the hiring manager. After that, there was a presentation and four separate one-on-one interviews. The people I met were really friendly and happy to discuss the company's business and current challenges, and they paid close attention to what I said. I'm a big fan of their products and was really excited about this job. It was a good overall experience, although they didn't provide feedback after the onsite interviews, which seems to be pretty standard in the industry now. If you don't get feedback, it usually means no offer.
- Questions about case studies
- Behavioral questions
DevOps Engineer
Got contacted by a recruiter on LinkedIn for an initial interview on Thursday, 9/26/2024. The video call was scheduled for the next day. The recruiter was on time, friendly and easy to talk to. She briefly introduced the company and answered my questions. The interview was casual and I was asked about my experience as a DevOps engineer. The interview ended on a good note but the communication went silent afterwards. I didn't know when to hear from them or what to expect next, nor was I responded to when I emailed the recruiter. I had to go back to LinkedIn to message the recruiter to get a response that "the hiring manager was busy but should review your candidacy by Friday." That Friday passed with no words from them. I mean, if I am not a good fit, let me know soon, and I'll understand - just don't leave me hanging... The recruiter was friendly and pressure-free, which was a nice plus, but the lack of communication clarity made this a neutral experience at best. EDIT: One week later I was contacted for a technical screening. The interviewer was respectful of my time and we were able to discuss some real challenges that the team was trying to solve. I understood that people got busy, and I might have left my previous comment a bit rushed. The lack of communication / setting the right expectations after my initial screening was real, so I decided not to change any of that, but I wanted to point out that this process was veering towards the positive side.
- Can you tell me about yourself?
- Could you elaborate on your most recent project as a DevOps engineer?
Wyze Labs Interview Questions
Quoted word for word from Wyze Labs interview reports.
“Could you explain the various accruals that contribute to the margins of our retailers?”
Read reports →“You mentioned testing hypotheses, so why did you label this "exploratory" research instead of "evaluative research"?”
Read reports →“What are your thoughts on short-form video streaming marketing within the United States?”
Read reports →“Can you explain what a closure is?”
Read reports →“How familiar are you with State-of-the-Art papers and deep learning research for computer vision?”
Read report →“Could you code a table and a UI in React and demonstrate how to bind data using props?”
Read report →“What draws you to WYZE?”
Read report →“What's your approach to redesigning the Apple Watch?”
Read report →“Tell me about basic Machine Learning concepts.”
Read report →Formats, difficulty and experience
Across all 41 Wyze Labs interview reports.