Productboard Software Engineer Interview Questions
& Process

First, I had a call with HR for some general questions. Then, a call with the department head to discuss my experience and the product. Finally, a technical call involving Javascript pair programming and an easy DSA question. The interviewers were friendly and the vibe was chill, even though they thought I was inexperienced for using a for loop. It felt pretty easy overall.

I was reached out to for this role via a job platform and then had a casual chat after hours with the CTO. We discussed the company's history, future plans, tech stack, and culture over a beer. This informal cultural interview led to a technical interview. The technical interview involved about two hours of probing my skills with two engineers on various topics, including a review of code from one of my public GitHub projects. This was followed by lunch with some of the engineering team, which also served as a cultural interview. They made me feel comfortable despite covering a lot about my technical background. There was no arbitrary whiteboard coding. I could have started working immediately, and they made the process very fast.

The interview process was pretty standard, though it's been a while. It started with a recruiter phone screen, then moved to either a manager or technical screen. After that, there was an onsite interview which included system design, a manager/behavioral interview, and two coding exercises. One coding exercise was domain-specific, and the other was a general DSA/leetcode style problem. The recruiter contacted me a few hours after the onsite on a Friday, saying the feedback was positive and we had a casual chat about a potential offer. I decided not to accept the offer due to personal reasons, like my interest in the product and thoughts on the business model, but overall, I had a great experience talking with everyone, including the recruiter, engineers, and managers. They were all smart, articulate, collaborative, and professional.