Square Product Manager (PM) Interview Guide

tl;dr

The interview loops at Square are designed to feel as authentic as possible to your day-to-day work, primarily asking questions about real Square features and data, so your interviewers are assessing if you’re someone they can work with at every step in the loop.

The key factor to success in Square’s PM interview process is being able to clearly explain your unique and strong strategic thinking. If you bring a specific vision, and can clearly explain your unique reasoning for launching features, you’ll be a good fit for Product at Square. Compared to Product roles at companies like Meta, resources at Square are more limited. Strong candidates for Product roles at Square have to be more adept at persuading stakeholders with competing priorities, and understanding problems to maximize ROI.

Square tends to prefer product managers with proficiency in at least some of the following:

• Product analytics
• Experimental design and A/B testing
• User-centric feature planning

What does a Square Product Manager do?

As a product manager at Square, you’ll serve as the intersection of customer needs and business objectives. You’ll define strategy for product, collaborate with teams across the company, and be expected to communicate persuasively and clearly with stakeholders from these teams.

Square’s product managers are hired based on specific team needs. An advantage of being a Square Product Manager is the end-to-end autonomy you’ll have over your features and releases. Unlike at Meta or Google, where team boundaries are relatively porous and PMs can be pulled in many directions, at Square, you can see your feature through. As a potential bonus, you’ll also have mobility between other companies under the Block umbrella, like Afterpay and Cash App.

The average total compensation across product management levels at Square are:

• Product Manager 4: $233K
• Product Manager 5: $310K
• Product Manager 6: $411K
• Product Manager 7: $581K

Before you apply

• Be ready to talk through a recent project, stressing measurable business impacts.
• Check out the Square tech blog to make sure you know about the latest initiatives.
• Research recent interview questions asked at Square.
• Try out as the Square app. Specifcially, try out the version the team you're intervieiwng with is connected to (for restaurants, for retail, etc.)
• Check out Square’s latest earnings statements. That way, when you’re in your experimentation and product case interviews, you can tie your answers to relevant company goals and metrics.

Interview process

Square’s interview process is, relative to other comparably-sized tech companies, heavy on business analytics and cross-functional impact.

Square doesn’t have a dedicated culture interview, or specific traits they look for, like at Amazon. Instead, Square operates more like Microsoft: their "culture fit screen" is basically searching for red flags.

Square hiring loops are fairly standardized between teams. The process typically takes between 4–6 weeks. Interviewers generally describe three stages for the interview loop at Square:

1. Recruiter phone screen to ensure you meet the minimum requirements for the role
2. Hiring manager interview, focused on your work history
3. Onsite interviews, which are multi-hour and assess your practical skills

1. Recruiter phone screen

This call typically focuses on behavioral questions, verifying your background and experience, and asking generally about products you’ve built. Don't be surprised if you get a question like: “What’s your experience like with APIs?”

Be ready to talk about your previous work history and skills as they relate to the job description and why you’re passionate about supporting businesses and customers in the field of payments (aka “Why Square”).

Sample questions include:

• Walk me through your resume.
• Tell me about a product you built that met the most resistance. How did you overcome it? Include challenges, methods, and results.
• Why Square?
• What’s your experience with APIs?
• Tell me about a time when you needed stakeholder engagement to implement a new process.

2. Hiring manager interview

This call will assess your work history, rather than traditional product sense. The hiring manager will assume your basic technical competency, so don’t expect too many in-depth technical questions. They’ll want to see if you’re someone who can fit their team’s culture, and make sure you know what you’re talking about when you mention your approach to product strategy.

Sample questions include:

• How would you develop strategies for the Food and Beverage division within Square?
• How do you strategize about customer needs and pain points?
• Walk me through the most complex technical project that you've been a part of.
• How would you keep developers working on a product motivated and turning out quality work?
• How do you prioritize features?

3. Onsite interviews

These all take place within one day, generally at a Square office if you’re within reasonable travel distance, though many candidates are able to take advantage of Square’s robust remote culture to do these over Zoom.

💡 IC6 and higher levels of product managers also have an additional leadership interview, with a potential skip-level manager round at the end of their onsite interviews to assess management style in greater detail.

a. Product sense and design interview

This 45-minute interview will give you a fairly open-ended question, and expect you to get granular strategically, like a systems design interview would for a software engineer. As with system design interviews, your interviewer will want to see how you manage scope creep. In product sense at Square, it’s more important to show how you’d maintain scope and manage segments and strategy more than offer perfect solutions.

You’ll be asked to design a feature for Square, and your interviewer will be looking to see your understanding of Square’s strategy, and how that is distinct from the company mission, especially in the short term.

Strong junior PM candidates have read Square’s most recent earnings statement and can use specifics from it before launching right into design. Senior-level candidates can do that, and are able to define specific market segments before launching into pain points and solutions, explaining why they focus on different segments in their answers.  Interviewers observe that staff-level (and above) candidates can also sub-segment Square’s known segments, like Food and Beverage, into smaller (more relevant) segments during this interview, demonstrating that they’re more immediately ready to implement.

Interviewers are looking for candidates who can show a strong sense of user empathy. Knowing the high-level segments of Square is a huge plus, but you also want to make sure you can show you understand user needs, especially for customization and pain points. Many of Square’s customers are small businesses, not just consumers, and you want your solutions to reflect that. Candidates that offer more blanket solutions at this stage are often disqualified.

b. Product analytics interview

This 45-minute call prioritizes business acumen and real-world experience, especially with conversion funnel exercises and ROI considerations. This interview will be much less ambiguous than the product sense round, with a clear correct answer, and more information gradually reviewed by your interviewer. You’ll be guided a lot more than a comparable interview at Meta, with your interviewer providing you with data and helping you course-correct if you go too far off.

Unlike at companies like Google, where candidates are allowed to answer product analytics questions with hypothetical or made-up numbers, Square interviews at this stage are designed to assess how you collaborate with your interviewer, including how you ask questions, and what data you ask for. Candidates who don’t ask questions and just jump into problem-solving at this step are usually disqualified.

Case study of a sample question

A common question asked at this stage is to analyze a conversion funnel in the context of Square’s debit cards. You might be asked what the ideal conversion funnel is for activating them, and how to drive that conversion level as a PM, i.e., get more customers to activate their cards.

Strong candidates at this stage generally structure their response by:

• Identifying the parts of the funnel
• Asking for more information
• Recognizing where the drop offs are in each part
• Making recommendations

Your interviewer will be judging not just that you ask for more information, but what information you ask for. For example, a strong candidate might understand that the funnel at this stage has multiple parts (requesting the card, mailing the card, activating the card, and making a purchase) but will know which part of the funnel to ask for more information about. If you can get enough data from them to prioritize the most valuable part of the funnel (i.e., people signing up for the cards), then you’ll be able to make recommendations.

Identifying the parts of the funnel

Weaker candidates at this stage focus on the wrong part of the funnel (often, the moment of first transaction, which is further down the funnel and may skew your proposed solution) or else don’t talk about prioritizing the moment of activation. If this happens, a good fix would be noticing the lowest conversion rate is when someone activates the card, and wondering why that might be the case. This is the area of most substantial dropoff, so a candidate noticing this would work to prioritize solutions here.

Asking Questions

The biggest and most often-disqualifying mistake for candidates at this stage is not asking questions before launching into solutions. Another common mistake is not being clear about why activation is the most important (because it leads to future repeat spending) rather than the first transaction, which will happen naturally after activation anyway. Smart candidates can see the relationship between these data points and articulate them.

Identifying Drop Offs and Making Recommendations

At this point in your solution, you should be able to design an experiment, specifically an A/B test, to get more data about why you’re seeing these drop offs. You can describe the experiment clearly, and figure out its ROI to ensure your recommendation is efficient and will provide maximum business impact. You can also make recommendations for what should happen after the experiment, and why.

c. Product strategy interview

This 45-minute call is more open-ended than the product analytics interview, and feels more like the product sense interview. You’ll be asked a question about a feature for Square, but rather than designing the feature itself, you’ll want to prioritize your strategy for this design, thinking metacognitively about the process.

You’ll want to demonstrate your user empathy here, since a commonly-asked question is to think about designing a messaging platform for Square sellers to connect with their customers. Strong candidates at this stage can think about who the feature is for (small businesses, mid-market, or upper-market customers) and how that would affect feature design and rollout.

A good structure for your answer to follow is:

• Start with the mission of the feature, ecosystem, and context it would be built in.
• Localize the users and differentiate Square from other platforms that might already do this.
• Identify points of monetization (in this context, think about how to build a messaging platform that drives growth).
• Segment by who is the buyer and seller.
• Consider the developers you’d be working with, both in terms of team and timeline.
• Develop a roadmap and strategy to potentially build this feature.

Sample questions include:

• Square recently launched a product that helps sellers train their staff. What is your strategy for increasing the revenue of this product by 5x in the next year?
• How would you create a strategy for a messaging platform for Square?

d. Cross-functional chats

You’ll have at least one 45-minute cross-functional chat, either with an engineering manager or a designer, and many candidates are scheduled for both conversations. These calls are more informal, and assess your culture fit across teams, since that’s a huge part of your role at Square. This is typically the least-standardized part of the Square interview loop, but you can expect to talk about communication style, managing conflicting priorities, tech debt, and how you work with engineers and designers.

A sample question:

• Your engineering manager wants to work on a new feature and you absolutely have no bandwidth. How will you handle it?

e. Panel interview

This hour-long conversation is typically the hardest round in the Square interview loop. You’ll be given an open-ended prompt in advance by your recruiter, and will be expected to bring in a presentation. You can make a Powerpoint, use Canva, or even whiteboard on the spot (though it’s not recommended) to address it. Generally the prompt is a variant on “You’re a PM at Square, and can develop any product for the restaurant or retail teams. What do you build?”

Candidates who pass this stage and get the job offer typically demonstrate that they’ve researched the company. Interviewers say that candidates often want to overthink their answer, but you don’t need to over-engineer a solution, or use new technology if you have a researched, user-relevant solution. There are huge communities of Square users on various social media platforms, like Reddit, where the best solutions are already being asked for by Square users and business owners. Strong senior+ candidates know how to leverage a user base like this.

Additional resources

• Take our Product Management Interviews course to level up your product management skills.
• Get coaching and actionable feedback from product managers at the level you aspire to land an offer for.
• Practice with mock interviews on the most common types of problems.

FAQs about the Square Product Manager interview

What can I expect from my interview at Square?

For your product manager interview at Square, you can expect a 4-6 week process of three main rounds: a recruiter screen, a hiring manager screen, and an intensive onsite process that will assess your analytic and strategic abilities as well as your skills in product management and design. You’ll also be expected to do a panel presentation and chat cross-functionally with developers and designers.

On average, how much do Square Product Managers typically make?

The average total compensation across product management levels at Square are:

• Product Manager 4: $233K
• Product Manager 5: $310K
• Product Manager 6 : $411K
• Product Manager 7: $581K

How long is the typical Square interview process?

Typically, interview loops at Square take 4–6 weeks.

How should I prepare for a product manager interview at Square?

• Be ready to talk through a recent project, emphasizing its business impact.
• Check out the Square tech blog to make sure you know about their latest projects.
• Research recent interview questions asked at Square.
• Try out multiple versions of the Square app so you can speak to features.
• Check out Square’s latest earnings statements.

Will I have in-person interviews at Square?

Square is a globally-situated company with a strong remote culture, but if you live near a Square office, you may be asked to come in for your onsite interviews.

Can I interview for more than one PM team at once?

Yes, you can interview with more than one Square team at once.