Productboard Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 90 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 90 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Productboard.
Productboard
AI Engineer
Mid Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral
I applied for the job and then got an email from a recruiter asking about my experience with Generative AI (like LLMs or agentic systems) and if I'd worked on NLP features in production. It's funny because my whole CV is about NLP and related projects. It seems like the recruiter didn't even read it. Like, why would companies hire clueless recruiters? It's like asking a Python dev if they know Python.
Confirmed questions1 question
- Do you have experience with Generative AI, such as LLMs or agentic systems, and have you deployed any NLP-based features into production?
Productboard
Account Executive
Mid Easy Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Presentation Panel
Interview formats
Behavioral Presentation Case
The interview process involved a recruiter screen, a hiring manager interview, a mock discovery session, and an interview with the CRO. Overall, the sales leadership team seemed to lack direction, and their mock discovery process was a terrible example of sales hiring. The scenario presented was highly unrealistic, expecting flawless execution from candidates, even though the hiring managers themselves demonstrated poor sales skills during the session.
Confirmed questions1 question
- What motivates your desire to join Productboard?
Productboard
Sales Role
Mid Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Phone screen Presentation Offer
Interview formats
Behavioral Presentation
So the process was pretty standard: Recruiter, then Hiring Mgr, then Peers, and finally a Presentation. The recruiter was super clear about what to expect, who I'd talk to, and the timeline. Scheduling was a breeze, and they were quick to respond to my questions or if I asked for an update. Although I ended up choosing a different path for my next move, they did make a really good offer. I thought the product, the team, and how they ran things were better than average.
Confirmed questions2 questions
- Can you tell me about your experience working with or selling to engineering or product teams?
- Are you willing to travel to client locations for sales purposes?
Productboard
Technical Recruiter
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Take home Presentation Technical screen
Interview formats
Behavioral Technical Presentation
The hiring process was really great and smooth. I liked knowing what was going on and feeling the energy throughout. 1. Screen call - about 30 mins, where I talked about my situation and expectations. I also got info on what's next and who I'd meet. 2. European Talent Lead interview - I was nervous at first, but they made me feel really comfortable. We talked about why I'm switching careers and my choice to get into Recruitment. 3. Assignment - received the day after the second interview. It was to explain how I'd recruit for a tech role. Even though I'm not a big fan of presentations, I actually enjoyed this one (smiles from the audience help!). 4. Head of Global Talent Acquisition interview - some extra questions, focusing on vision.
Confirmed questions4 questions
- Why do you want to pursue a career in Recruiting?
- Which aspects of this role do you anticipate finding less enjoyable?
- Could you outline your approach to hiring for a technical position?
Productboard Interview Questions
Quoted word for word from Productboard interview reports.
“How do you handle keyboard event propagation within a React useEffect?”
Read reports →“Could you design a system for streaming videos, similar to YouTube?”
Read reports →“How do you approach detecting configuration drift in your infrastructure?”
Read reports →“At what point in your design process do you bring in engineering?”
Read reports →“What would be your initial steps to launch our ABM strategy?”
Read report →“Are you open to relocating to San Francisco, or would you prefer to remain remote?”
Read report →“Do you have any LeetCode easy and general JS questions?”
Read report →“Could you outline a plan for implementing new customer onboarding using Productboard?”
Read report →“Given a scenario where you need to build a park catering to various customer needs, how would you approach prioritization?”
Read report →Formats, difficulty and experience
Across all 90 Productboard interview reports.