Produce Pay logo

Produce Pay Interview Questions
& Process

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

Based on 21 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
57.1% Positive experience

Which role are you interviewing for?

11 roles · 21 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Produce Pay.

Showing 4 of 21
Produce Pay logo
Produce Pay

Product Manager

Product · more than a year ago

Mid Easy Positive experience Accept offer 3 rounds
Interview process
Recruiter call Presentation Technical screen
Interview formats
Behavioral Presentation Technical

So, I was on a tech job site, and the hiring manager, who's the CPO, reached out. My first interview was a Zoom call with him, mostly just general background stuff. Then I had a panel interview where I had to present a case study I'd worked on. After that went well, I had two more interviews, back-to-back, focused on product sense, kind of like what you see at Google or Facebook, but not as intense. These were with the CPO and the Head of Design. They originally planned for three, but they decided two were enough.

Confirmed questions1 question
  • Can you design an app for a bike shop located in Los Angeles?
Produce Pay logo
Produce Pay

Frontend Developer

Engineering · more than a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen
Interview formats
Behavioral Technical Coding System Design

First, a 30-minute call with HR. Then, a 45-minute meeting with the project manager to discuss technologies, the team, and current projects. We also talked about my background and past projects. The third stage involved three 90-minute technical interviews, each with live coding. It seemed like interviewers didn't coordinate on the challenges, as each presented a different one. One challenge was a JS/HTML exercise focusing on DOM manipulation, another on asynchronism. The third interview was more architecture-focused: they presented a scenario and assessed how I'd approach it, what questions I'd ask the client, and what data I'd need. A week after the last technical interview, I emailed to ask about my status since nobody had contacted me, despite their promise to do so. Overall, very little commitment and professionalism from recruiters and the company.

Confirmed questions4 questions
  • Tell me about your experience, the technologies you've used, and the projects you've worked on.
  • A practical exercise in JavaScript and HTML, focusing on DOM manipulation.
  • A practical exercise involving asynchronous JavaScript.
Produce Pay logo
Produce Pay

Software Engineer

Engineering

Entry Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
System Design Coding

First one of the engineering management people reached out, then a 30 minute call with recruiter, a 30 minute system design interview, and a time-boxed take home interview question -- all within a week. It is nice that the process is fast. The people seem nice, and it's likely a good place to work, but from the outside you just can't really tell what kind of company it is. There are rumors (either from the company or actual hires) that compensation is good, but there's no data to back that. Both tech portions of the interview felt informal and not finely structured. Either this is intentional because they want to see how you respond to ambiguity (see googliness) or they don't have their interview process polished and locked down yet. In my opinion, they don't know how to most efficiently find what they are looking for yet.

Confirmed questions3 questions
  • A system design question based on the book, evaluating alignment with their project selection.
  • A take-home coding question presented in a PDF, with a two-hour time limit.
  • Interpret a grid annotation task and provided doc-formatted test examples to grasp the take-home problem.
Produce Pay logo
Produce Pay

Administration

Operations

Entry Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel
Interview formats
Behavioral Technical

The process was EXHAUSTIVE, 5 Interviews! First interview went well for the second interview scheduled I got stood up and the recruiter DID NOT contacted me back until almost 2 hours after my scheduled time, has the second interview where the lady had kids talking in the background and was not a pleasant talk, then comes a 3rd interview with someone that seemed to be in a rush, and 4th interview that I believe was the only one worth it. For the 5th interview the manager showed up late, during the 30 minute talk he probably looked me in the eyes maybe twice, his non-verbal language was very rude, he did not take time to interact with me as a human being I would say that this probably was at a certain Level one of the worst interviews I have attended. I was interested in the company and that was the reason I continued with the process however after a week of doing this round of interviews I asked for feedback and it took them another week to just reply that they would give feedback soon. Very disappointed with their level of respect for other people’s time and lack of professionalism from the recruiter.

Confirmed questions1 question
  • What were 3 areas of opportunity?

Produce Pay Interview Questions

Quoted word for word from Produce Pay interview reports.

Is a loan with a high APR and short term better than a loan with a low APR and long term?

Read reports

What's your estimate for the number of elevators needed in a typical office building?

Read reports

Imagine you're the CEO of Lego. What new product line would you propose to boost revenue?

Read report

Can you design an app for a bike shop located in Los Angeles?

Read report

Formats, difficulty and experience

Across all 21 Produce Pay interview reports.

Interview formats

Behavioral 38%
Technical 30%
Coding 12%
Presentation 10%
System Design 6%

Interview difficulty

Easy 19%
Average 57.1%
Difficult 23.8%

Candidate experience

Positive 57.1%
Negative 38.1%
Neutral 4.8%

Reports by job function

Engineering 6
Product 4
Operations 3
Sales 2
Marketing 2
Finance 2