Help Scout Interview Questions
& Process

I started with the VP of CX, which was great, then moved to a team interview that also went well. The recruiter checked in to make sure we were on the same page. After that, I got an assignment to do and present. I presented it to the team, and then I had a final interview with the CEO and COO. That's when things went wrong. They apparently reviewed my presentation and decided not to hire me without even meeting me. The COO canceled last minute, so it was just me and the CEO, who seemed to be just going through the motions. A few days later, I got feedback on my presentation that honestly didn't make sense given what they asked for. They said my writing style didn't fit their brand voice (which I wasn't given a guide for), that my 10-minute presentation wasn't detailed enough, and that it didn't show skills I'd already demonstrated in earlier rounds and weren't even asked for in the assignment.

So, first there was a recruiter call to get to know each other. Then I had a technical interview with two engineers. After that, I was given a take-home project, which I actually liked because it felt more like the actual job than some leetcode questions. Help Scout also values the time you put into the assignment, and they actually pay you for it. Finally, I got some feedback and had a last call with a technical leader or director to sort out any remaining details. It was a really friendly and respectful process overall.

So I had a few initial interviews and then they hit me with a take-home project. They mentioned upfront that the time wasn't enough, and they just wanted to see the code and then talk about it in the next interview. The instructions even said not to spend more than 6 hours on it, and to add notes in a readme if I couldn't finish. The project used a language not on my resume, and learning it took extra time, but I did learn it a bit for the project. I set up the structure with data, business, and API layers, plus some tests. I added comments for the unfinished parts, as instructed. The feedback was that the code didn't meet their standards and didn't fully run, which was weird since they said it was okay if it wasn't finished. It seems like they expect full production-level code with specific tech and languages in just a few hours, even though just setting up the dev environment takes ages. It was a total waste of my time. I saw a similar review from someone else, which I wish I'd read first. Interviews should be about checking thought process and problem-solving, not expecting perfect production code without a chance to discuss it. If they want specific tech, they should check resumes better and only interview people who've recently used that tech. Also, the whole process took about 2 months because they were slow to get back to me at each step. It really wasn't a fair or reasonable interview process.

A recruiter from Help Scout reached out and we started the process. First, I had a video chat with the hiring manager. Then, I interviewed with two team members. After that, there was a project that required a presentation. This was followed by a panel presentation with about 6-7 people from the wider team, and finally, they made an offer. It was a straightforward process, but the project really let us dive into the actual work and how we approach things. I especially appreciated that they compensated for the project, which is a great practice that should be more common. Everyone I interacted with was fantastic, very helpful and knowledgeable. My main advice is to ask a lot of questions to get a good sense of the company and the people there – interview them too.