Own the boundaries
Design explicit contracts between the engine, merchant surfaces, payment providers, identity, and infrastructure.
Commerce
Intelligence
Infrastructure
Why institutions choose Box
Keep the brand, records, rails, and merchant relationship.
Start here
By merchant activity
By deployment
See it running
OlivePay licensed Box. The tills are already in the field.
We are building the commerce layer institutions run on. 8 roles are open across 2 teams.

The work
The difficult work is not another checkout screen. It is making commerce deployable, observable, and adaptable across merchant types, providers, and regions.
Design explicit contracts between the engine, merchant surfaces, payment providers, identity, and infrastructure.
Turn architectural claims into working deployments, repeatable tests, visible output, and documentation another team can follow.
Give operators and merchants clear tools without exposing the machinery required to keep every channel consistent.
Vancouver, BC or New York City
Full-time
Vancouver, BC or New York City
Full-time
Vancouver, BC
Full-time
Vancouver, BC
Full-time
Vancouver, BC
Full-time
Vancouver, BC
Full-time
Vancouver, BC
Full-time
Vancouver, BC
Full-time
How we work
Important trade-offs should survive the meeting and remain understandable to the next person who touches the system.
A claim is not finished until it works through the interface, command, deployment, or operating workflow a customer will use.
Teams stay close to the result across product, engineering, design, operations, and the institution deploying Box.
Free to run your business. You pay for what you use.
Free to run your business. You pay for what you use.