You're building for people who are already there
60K+ merchants are running real businesses on this platform right now. There's no cold start, no convincing anyone to try it. The pressure and the reward are both real from day one.
60K+ merchants run their stores on what we ship. No side projects, no shelfware. If it merges, it's live within the week.
No two days are the same, but this is a fair sketch of one.
Async, in a channel. If it can be read in thirty seconds, it doesn't need a meeting.
A webhook retry bug, a new Skill for the Agent Kit, a slow query in the Merchant API. Your call on priority, inside the quarter's goals.
Real support tickets, real error rates. The signal you design against is the same one support sees.
Behind a flag if it's risky, straight to production if it isn't. Either way, it's out before you log off.
60K+ merchants are running real businesses on this platform right now. There's no cold start, no convincing anyone to try it. The pressure and the reward are both real from day one.
Decisions get written down. It's also what makes a Skill for the Agent Kit worth authoring.
Skippable if a written update covers it, and most of them do.
"The distance between writing a fix and a merchant not hitting that bug again is usually one deploy."
Backend Engineer, Platform team
"I spend more time reading support tickets than most engineers I know. It's the fastest way to know what to build next."
Platform Engineer, Webhooks
"Writing a Skill that an agent can actually follow is a different kind of documentation discipline. It's made our own docs better."
Engineer, Partners Agent Kit
° placeholder quotes for layout only. Replace with real, attributed team quotes before publishing.
° needs confirmation from HR/People before publishing.
Placeholder roles below. Wire this list to the real ATS before launch.
° every role link above is a placeholder. Point it at the real careers/ATS listing before publishing.
We're always meeting good people. Tell us what you're good at.