Block Program / Project Manager Interview Questions

1.Tell me about a project you managed where a change that helped one group of customers created friction or risk for another. How did you navigate that?

2.Walk me through a time you managed a project where a data or financial integrity issue surfaced mid-execution. What did you do the moment you found out?

3.Describe a project where you had to manage work against an external standard, API, or protocol that was actively changing while you were building. How did you keep the project from breaking every time it shifted?

4.Tell me about a time you coordinated a software release that had to roll out to physical hardware or devices already in the field. What made that different from a standard software deploy?

5.You're managing a Square feature that operations wants to monetize with a new fee structure, but early research suggests it could push lower-revenue sellers off the platform. How do you frame the decision for leadership and what do you actually recommend?

6.Tell me about the most consequential financial or transactional error your team shipped. What was your role in catching it, and what did the post-mortem change?

7.Estimate how many Square sellers in the U.S. are actively processing payments on any given weekday. Walk me through your assumptions.

8.Cash App's weekly P2P payment volume drops 8% week-over-week with no product changes shipped that week. How do you diagnose what happened?

9.You're the PM for a program to migrate Square sellers from a legacy invoicing product to a new one. Migration is optional, but leadership wants 60% of active sellers moved in 90 days. You're at 22% after 45 days. What do you do?

10.Square's gross payment volume grew 12% year-over-year, but the number of active sellers grew only 3%. What are the possible explanations, and which would you prioritize investigating as a PM?

11.You're leading a program to launch a new Cash App feature and you've just learned the team that owns the identity verification dependency is being reorganized — their PM is out, their eng lead is moving to a different product, and no one has confirmed who owns your dependency going forward. Your launch is in six weeks. What do you do in the next 48 hours?

12.Block is considering expanding Square's lending product — Square Loans — to a new seller segment that currently has lower average GPV but higher application volume. Finance says the unit economics are marginal. How would you structure the analysis to make a recommendation?

13.How do you typically structure your project status updates so that an engineering lead and a non-technical stakeholder both leave the meeting with what they actually need?

14.Walk me through how you build and maintain a project timeline when your dependencies are spread across multiple engineering teams with their own sprint cadences.

15.A Square seller-facing feature is ready to ship, but the compliance team comes back five days before launch saying they need two more weeks for a review. How do you handle it?

16.You're running a program with three workstreams, and two weeks before a milestone, one workstream lead tells you they're 40% done with what they estimated at 80%. How do you diagnose whether this is a scoping problem, an estimation problem, or an execution problem — and does your response differ depending on which it is?

17.You've been asked to lead a program that will consolidate two overlapping seller onboarding flows across Square — one owned by product and one owned by a growth team that has different success metrics. How do you get to a single roadmap when both teams have legitimate competing claims on the design?

18.You're managing a cross-functional program for Cash App and you're two months from launch when a new regulatory requirement drops that affects your core feature. Engineering estimates it's a six-week lift. You have eight weeks left and three weeks of QA already scheduled. What's your move?

19.You're managing a Cash App feature rollout and a critical bug surfaces in production the morning of launch — it affects only 3% of users but those users can't complete a payment. Engineering says a fix is two hours away. Do you launch, delay, or do something else?

20.You inherit a program mid-flight and discover the previous PM never established a RACI or clear ownership for one of the three workstreams. The team has been operating on assumptions. How do you fix it without derailing momentum?

21.You're managing a Square Banking program — a new lending product for small sellers — and your data team tells you the model they're using to assess loan eligibility has a disparate impact on a specific demographic. Legal says it's not technically illegal. What do you do with that information?

22.You're running a program to launch a new Cash App feature for international markets. Three weeks before launch, you find out that the localization vendor delivered translations that contain factual errors about fee structures — errors that could mislead users about how much a transfer costs. Legal says it's fixable but needs ten days. You have 21 days. What's your call?

23.You're coordinating a large program across six teams, and two team leads come to you separately claiming the other team is blocking their deliverable. Both accounts are plausible. You can't tell who's right from the outside, and the milestone is in nine days. How do you get to the truth and unblock the program?

24.Your program is supposed to ship a new Square hardware integration in eight weeks. Five weeks in, the hardware team tells you a firmware issue means the device can't support one of your three core features at launch — but they can ship a degraded version. Your product lead wants the full feature or nothing. Engineering says the degraded version would still cover 80% of seller use cases. How do you resolve this?

25.Tell me about a time you had to get a team or partner to change how they were working — without having any direct authority over them. What was your lever?

26.Walk me through a time you had to deliver bad news to a stakeholder — a slipped date, a cut feature, a missed commitment. How did you frame it and how did they take it?

27.Tell me about a time you needed buy-in from a finance or legal partner to keep a project moving — and they were slowing things down. How did you build that relationship and what changed?

28.You're running a program with real momentum and a VP two levels above you starts pulling one of your key contributors into ad hoc work that's eating into their committed time. You don't have a direct line to that VP. What do you do?

29.Tell me about the most senior stakeholder you've had to push back on. What was the disagreement, how did you make your case, and what happened?

30.You're the program manager for a Cash App launch that marketing has already announced publicly with a hard date. Two weeks out, engineering tells you they need three more weeks. Marketing is not in your reporting chain and their campaign is already in market. How do you handle the next 48 hours?