When are Square performance reviews? (2026)
Square serves small merchants who lose money the moment payments stop, so reliability at the point of sale outranks nearly everything. Cycle dates vary, so record uptime and merchant outcomes.
Once a year
No specific review month is published for this company, because none could be sourced from the company's own material. What follows is the cycle shape, which is what is actually knowable. Your own manager is the authority on this year's dates.
How the cycle works
Square's customers are largely small merchants: a café, a salon, a market stall. When the payment terminal fails, that merchant cannot take money, and there is no fallback department to route around it. This produces the sharpest reliability expectation in consumer fintech, because the cost of failure is immediate, visible, and borne by a small business that feels it.
It also means the product spans hardware, in-person software, and backend payment processing, and that people are evaluated inside quite different disciplines against a shared standard of merchant impact. A hardware engineer, a mobile engineer and a risk analyst are all ultimately assessed on whether merchants could transact.
The other defining constraint is that this is regulated financial infrastructure. Risk, fraud and compliance are not a separate department's problem; a product decision can create regulatory exposure, and understanding that is part of competence here.
Confirm cycle dates with your manager rather than assuming a schedule.
What actually gets weighed
Point-of-sale reliability leads, measured in transactions that completed and merchants who never noticed a problem. Degradation during a busy period costs more than the same degradation at three in the morning, and evaluation reflects that weighting.
Merchant economics come second. Anything that reduced the cost of accepting a payment, shortened settlement time, or removed a step from opening an account is directly on the value line, because those are the things a small merchant actually feels.
Fraud and risk outcomes are the third axis, and they are two-sided: catching bad activity matters, and so does not blocking legitimate merchants. A model that improved detection while reducing false declines is a strong result; one that improved detection alone is an incomplete story.
Hardware and software co-design is the fourth, since the terminal and the app have to work as one product.
What to have ready
- Transaction success rates, weighted toward peak trading hours.
- Merchant-facing economics: cost, settlement speed, onboarding time.
- Fraud outcomes reported on both sides, detection and false positives together.
- Incidents during high-volume periods, with what you did and what changed after.
- Anything that required hardware and software to be designed against each other.