Product Manager, Core

In just five years, Stora has become the platform behind more than 30% of UK self storage locations, and we're scaling globally from here. Operators have processed over £150m in automated payments through us, and see an average of 32% business growth after they switch.

We're doing this in a market that's wide open. Europe has over 10,000 self storage sites and is growing fast, yet it sits years behind the US on maturity and is still barely touched by good software. The UK is our stronghold. The rest of Europe is where we're heading next.

Stora is the operating system for modern self storage: online bookings, payments, facility management, reporting, and automation in one platform. We started as operators ourselves, and that's still how we think. If you want to own a product operators depend on every day, in a company genuinely rethinking how it builds, this is it.

We have a strong product team, great engineers, and a growing product. The bottleneck isn't ideas or execution capacity. It's people who can hold the full picture at once.

What the business needs, what the customer actually experiences, what's technically feasible, what to cut when time is short, and knowing when to slow down. Making good calls across all of it. That's the job.

We've shortened the loop between insight and shipped product by stripping out the layers that slow good judgement down. The quality bar didn't move. This role exists to keep doing that. It carries real ownership from day one, and the scope grows as Stora does.

This is the product operators live in every day, and the storefront their own customers book through. You're designing for two users at once: the operator running the business, and the end customer renting the unit. Getting that B2B2C experience right is a genuine craft problem. It's a broad, central surface, and it's heavy on UX.

Concretely, the surface includes:

• Core workflows: customers, units, tenancies, access

• Roles, permissions, account structure

• Operational reporting: occupancy, utilisation, activity

• The internal data layer: event tracking, core models, metric definitions

• The growth surface: storefront, checkout, the lead → booking funnel

If an operator uses it daily, or relies on it to understand their business, it sits with this team.

We've changed how product gets built s is how we operate now.

Designers work directly in the codebase. Engineers and product people work closely together from the start. We use AI genuinely: to explore, prototype and move faster. The work gets closer to reality, sooner.

If you're at a company that talks about moving faster but runs the same process it did three years ago, this will feel different. We're not done evolving how we work, and this person will have real scope to shape that.

• Own a problem space end-to-end, from understanding the customer need to something live in the product

• Work across both sides of the experience: operator back office and end-customer storefront

• Work directly with engineering leads. Close collaboration, not handoff

• Make scope calls. Know what to cut, what's fundamental, what can wait

• Work with or without a designer, depending on the problem. What matters is the outcome

• Stay close to customers, talk to operators, understand how they run their businesses, bring that into every decision

• Shape how we work. The process isn't fixed. If something's slowing things down, fix it

• Real product experience at a SaaS company. You've owned features or problem spaces end-to-end and shipped things people use. Roughly 2+ years, though we care more about the evidence than the number

• A builder by instinct. You make things: side projects, tools, a company you tried to start.…