Block Product Manager Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 31 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Block.
Block
Product Manager
Senior Average Positive experience Decline offer 4 rounds
Interview process
Recruiter call Phone screen Presentation Onsite
Interview formats
Behavioral Case Presentation Technical
First, there was a behavioral interview, then a product management scenario question. After that, I had to give a presentation about a project I worked on to the team I would be joining. Finally, they asked some questions and I answered them.
Confirmed questions1 question
- Can you describe the most technical project you have been involved in?
Block
Product Manager
Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Presentation Background check
Interview formats
Behavioral Technical Presentation
The interview process was a major letdown and frankly unprofessional. The interviewers clearly need more training on how to conduct interviews. I had four rounds scheduled: two behavioral interviews, a technical interview, and a presentation. The behavioral interviews were super short, only 30 minutes each, which wasn't much time to really answer things. The technical interview was supposed to be an hour, but the interviewer thought it was only 45 minutes. It followed Amazon's STAR method for the behavioral parts, with standard questions. They stuck to a script and didn't really ask follow-up questions or try to dig deeper into my experience. It felt like they were just going through the motions. The technical interview was pretty bad. The interviewer had a thick French accent, making communication tough. I did get a system design question, but while I was explaining it, he seemed more focused on picking it apart than having a real conversation. Then, when we got to Kubernetes questions, he made them really complex, needing lots of follow-ups just to get clarity. He wanted very short answers to vague, complicated questions and would say things like, 'Maybe I'm not asking this well' when I asked for clarification. His frustration was obvious, but I managed to answer everything. Shockingly, before I even finished the presentation round, the recruiter told me they were canceling the last interview based on the feedback from the earlier ones. This whole thing felt like a huge waste of my time. The interviewers seemed disengaged and the team felt disorganized. The technical interviewer really needs training on how to be professional and conduct interviews properly. Glad I didn't end up there.
Confirmed questions3 questions
- Can you share an example of a time when...
- Describe a system design you've worked on or would design.
- What are your thoughts on Kubernetes?
Block
Product Manager
Lead Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical Case
I applied online, then weeks later, I saw the job ad shared by my connection on LinkedIn and reached out to the hiring manager directly. While we were talking, I got an email saying they weren't interviewing anymore, which was weird since my profile seemed to match. After some confusion between the hiring manager and recruiters, I got a call with the hiring manager, which went well. Then, I got an email to schedule another call with a different person in a week, focused on 'strategy'. I assumed it was about the product strategy for the role I applied for, but it turned out to be more general, about how I choose which products to work on. I was a bit let down because I'd prepared for the specific product. They later emailed saying they found a better match. The recruiters were incompetent and gave misleading info. They should call candidates instead of sending email templates.
Confirmed questions1 question
- What criteria do you use when deciding which products to focus on?
Block Product Manager Interview Questions
Quoted word for word from Block interview reports.
“Consider this scenario: 100 people receive a call, and 100 do not. Out of those who received a call, 75 subscribe. Out of those who did not receive a call, 70 subscribe. Each call costs $50. Should Square implement this calling strategy? How would you make that decision?”
Read reports →“What would you build if you could build absolutely anything?”
Read reports →“We've observed low conversion rates from free trials to paid subscriptions for the Square Appointments app. A hypothesis suggests that incorporating 'a personal touch' might increase conversions. How would you design an experiment to test this?”
Read reports →“Describe your process for building out line item refunds for Square Register.”
Read reports →“When do you choose to partner up versus when do you decide to build something yourself?”
Read report →“Could you describe what you see as the responsibilities of a Product Manager?”
Read report →“How would you approach estimating the size of this opportunity?”
Read report →“What suggestions do you have for enhancing our product?”
Read report →“Imagine Jack tells you today that we need to create 'something for creatives'. What would be your approach?”
Read report →Formats, difficulty and experience
Across all 31 Block interview reports.