WeightWatchers Software Engineer Interview Questions
& Process

The recruiter asked about async/await, API experience, TypeScript, microservices, React Hooks, and Docker/Kubernetes. Salary info was vague and seemed low. They asked multiple times why I'm job searching. The hiring manager was unclear about the team and role details. It sounds like they have a modern tech stack and good work-life balance. There were two technical rounds: one focused on React, the other on algorithms. During the algorithm round, the interviewer's interruptions made it hard to think. Zoom links were sometimes sent last minute. Everyone was friendly and I got a good impression of work-life balance, but the overall candidate experience needs improvement.

The recruiter called and started asking syntax questions right out of a book. It was my first time interviewing after college, which was 13 years ago. I was a bit caught off guard by the syntax-based phone interview, and it took me a few questions to figure out what was going on. I suggested we have a discussion about problem-solving approaches and technical solutions to showcase my experience, but the HR person said they didn't have enough time for that level of detail. Right then, I knew it wasn't a company I'd join. I told him I wasn't interested in proceeding, and we ended the interview. The questions were about ECMAScript, something I've never worked with or even listed on my resume. I suspect he was just looking at an ECMAScript book and didn't know what else to ask for a Node.js role.

I had a recruiter call first, then a technical screening over the phone where they got pretty deep into the questions. After that, there were 3 rounds on site. The phone technical person was really detailed, asking me to talk about creating a project and how I'd hook up a REST API to the UI.