Skip to content

Square PM interview: what to expect and how to prepare

Square's PM loop tests whether you think like a seller, reason fluently in payments metrics like GMV and take rate, and ship simple products, so here is how the interview works and how to prepare for each round.

Square's interview structure

Square runs a PM loop that looks familiar to anyone who has interviewed at a payments company, but the bar lives in the details. The process starts with a recruiter screen. This call covers your background, your reasons for wanting Square, and a quick read on your communication. Recruiters want to know you can explain a product decision in plain words without jargon.

Next comes the hiring manager round. The hiring manager owns the team you would join, so the questions get specific to their surface. Expect a product sense prompt tied to their domain and an end-to-end walk through one project where you were the lead. They probe for ownership. Vague "we" answers land with a thud. Bring decisions you made and tradeoffs you owned as the PM.

The panel loop has four to five interviews. These split across product sense, execution, analytics, and behavioral rounds. Some loops add a cross-functional round with a design or engineering partner. Each interviewer files an independent write-up.

Last is the hire committee. A group of Square leaders reads the written feedback and decides without ever meeting the candidate. This matters for your prep. Interviewers take notes during your session and turn them into a case for or against the hire. Clear structure helps them produce a strong write-up. Ramble, and the notes get muddy, which hurts you in committee.

What product sense looks like at Square

Square sells to sellers. The whole company orbits the merchant, from a food truck taking its first card payment to a 80-location chain like Purdys Chocolatier. Seller cohorts who adopt Square's full software ecosystem see about 9% higher sales. That number shapes how Square thinks, and your product sense answers should reflect the same instinct.

Square pairs hardware and software in a way matched by few competitors. From payment processing to point of sale, hardware to software, business financing to payroll, Square built one connected commerce system for sellers. A product sense prompt at Square often asks you to improve a piece of that stack. Think Square Terminal, Square for Restaurants, or the new Square Handheld. Your answer needs a clear user, a sharp problem, and a solution that fits a busy merchant with no time for setup.

Square aims further down market than most rivals. The free POS plan and low upfront hardware cost target small and micro businesses. When you critique or design, keep that user in mind. A feature that delights an enterprise buyer may confuse a solo baker. Shreyas Doshi, a former product leader at Stripe, Twitter, and Google, calls product sense the ability to make good product decisions even in the absence of a clear answer. At Square, the first meaning of "good" is good for a small seller.

Execution and metrics for payments and SMB tools

Execution rounds test whether you can ship a product and measure the outcome. Payments adds its own vocabulary, and Square expects fluency. Three numbers come up in round after round.

Gross merchandise value, or GMV, is the total dollars flowing through a seller's Square account. Take rate is the slice Square keeps from each transaction. Take rate is platform revenue divided by GMV, the percentage of each transaction the platform captures as revenue. Attach rate tracks how many sellers add a second or third product, like payroll or capital, on top of payments.

You should reason about these out loud for the interviewer. Say a prompt asks how to grow revenue on the seller business. You can pull the lever of more sellers, higher GMV per seller, or a higher take rate through software attach. A 1% increase in take rate on a $10M GMV base adds $100,000 in annual revenue, which can outweigh chasing raw GMV growth. Show that you know which lever fits the situation.

Metrics questions also test guardrails. If you push attach rate by bundling features, what happens to seller churn? If you raise hardware price, what happens to new seller signups? Square wants a PM who chases a goal without breaking the seller relationship.

Behavioral themes Square cares about

Square's behavioral bar centers on customer obsession, and the customer is the seller. Prepare stories where you dug into a real user problem and changed course based on the findings. April Dunford, author of Obviously Awesome, suggests sitting with the sales team and listening to confused customers to find where a product breaks down (Dunford, Obviously Awesome). That same habit of getting close to the user is what Square wants to hear in your stories.

Bias for simplicity runs deep at Square. Square built its brand on a tiny white reader that simply did its job. In your stories, show moments where you cut scope to ship a clean product. A PM who adds five settings to solve one problem reads as a poor fit.

Cross-functional partnership matters more at Square than at a pure software shop. Hardware and design sit at the same table as engineering. Square contrasts itself with rivals that force sellers to stitch together hardware, software, and payments from many vendors. Building that connected system takes tight work across teams. Have a story about a hard call you made alongside a design or hardware partner.

Concrete preparation steps

Start with the seller stack. Sign up for a free Square account, order a reader if you can, and process a test payment. Walk the onboarding through the eyes of a real merchant. Note every point of friction.

Practice merchant-side product critiques. Pick a Square surface, name the seller it serves, and list two changes that would help that seller earn or save money. Do this for three different surfaces so you can move fast in the room.

Drill the money math. Be ready to break down GMV, take rate, and attach rate from memory and connect a product change to each metric. If you want a deeper rep on payments-specific cases, work through these payments PM interview questions before your loop.

Last, prepare three sharp behavioral stories. One on customer obsession, one on cutting scope for simplicity, and one on a tough cross-functional decision. Write them in a structure you can deliver clean, since the hire committee reads only the interviewer's notes.

Square rewards PMs who think like a seller, reason in payments numbers, and ship simple things. Build your prep around those instincts, and the loop becomes a place to show your strongest work.

Works Cited

Doshi, Shreyas. Product Sense Interview Prep. Exponent, 2026, tryexponent.com.

Dunford, April. Obviously Awesome: How to Nail Product Positioning so Customers Get It, Buy It, Love It. Ambient Press, 2019.

"Understanding Marketplace Unit Economics and GMV." Lowcode Agency, 2026, lowcode.agency.

Block, Inc. Shareholder Communication. U.S. Securities and Exchange Commission, 2016, sec.gov.

Browse all guides