Productiv logo

Productiv Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 28 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

13 roles · 28 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Productiv.

Showing 4 of 28
Productiv logo
Productiv

Full Stack Engineer

Engineering · nearly a year ago

Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
System Design System Design System Design

I had an initial chat with the hiring manager. Then, I went through three rounds of technical interviews. They didn't ask any LeetCode questions. Instead, the three technical interviews involved collaborative discussions on system design and product design.

Confirmed questions1 question
  • Can you describe the direct impact of your contributions?
Productiv logo
Productiv

Engineering Manager

Engineering · a year ago

Manager Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Technical Coding Behavioral

The interview process started with a great first round with the hiring manager, where I felt totally in sync. However, the second round with the engineers was terrible. They asked a coding question that wasn't relevant to the job, and then when we tried to have a conversation, it was barely a conversation. What they did communicate felt totally different from what the hiring manager had said. It's important to get everyone on the same page about what you're looking for.

Confirmed questions1 question
  • Could you reverse a palindrome using a non-standard linked list implementation and explain how you would construct such a linked list?
Productiv logo
Productiv

Business Development Representative

Sales · a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Presentation Onsite
Interview formats
Behavioral Presentation Technical

This interview process spanned from late January to mid-March. It started off pleasant, but the communication and scheduling really went downhill towards the end. I was told by the head of sales to use their scheduler. I reached the final round and confirmed my interview SEVEN DAYS before with their scheduler via email. She put it on the calendar. I prepared for the sales mock presentation, which required me to commute to the office. Then, the DAY before my final round interview, they canceled it saying I didn't confirm. I messaged the Head of Sales on Linkedin, showing him the email confirmation from 7 days prior. He said he'd sort it out, but instead sided with the scheduler, saying the cancellation was due to me not accepting the Google Calendar invite. They pointed out a small detail to deflect blame, which seemed like a red flag. They didn't send a follow-up reminder about needing to accept the invite in the 7 days between my confirmation and the cancellation.

Confirmed questions1 question
  • What are some challenges you've encountered in your current role?
Productiv logo
Productiv

Software Engineer

Engineering · a year ago

Senior Easy Neutral experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

I had an initial screening call with the recruiter which went well, and then I was scheduled for a call with the hiring manager. The questions were mainly about my current role, the projects I’ve been responsible for, and what I’m interested in. I thought the conversation went pretty well overall. But I got feedback that I was rejected because they wanted more technical details and some insights into the business model and system design. I guess I assumed those topics would be covered in the system design interview, so I gave a high-level overview of my projects instead of diving deep into technical specifics. Since it was only a 30-minute interview, I focused on giving a brief summary of my work. Looking back, I really wish they had communicated the interview expectations more clearly beforehand so I could have adjusted my answers.

Confirmed questions1 question
  • Could you tell me about a project you were in charge of?

Productiv Interview Questions

Quoted word for word from Productiv interview reports.

Could you reverse a palindrome using a non-standard linked list implementation and explain how you would construct such a linked list?

Read reports

Design a better airport experience for passengers, acting as the airport authority.

Read reports

How would you approach dealing with pay transparency legislation?

Read report

Considering our current gaps and startup priorities, what would be your top priorities for the Customer Success organization?

Read report

On your first day, how would you get started with your assigned territory?

Read report

Tell me about a time you had to deliver unwelcome news to a client.

Read report

How would you prioritize your existing client portfolio?

Read report

Formats, difficulty and experience

Across all 28 Productiv interview reports.

Interview formats

Behavioral 40.6%
Presentation 26.6%
Technical 12.5%
Case 6.2%
System Design 4.7%

Interview difficulty

Easy 7.1%
Average 67.9%
Difficult 25%

Candidate experience

Positive 50%
Negative 39.3%
Neutral 10.7%

Reports by job function

Sales 14
Engineering 7
HR 2
Product 2
Operations 1
Analytics 1