R-26 · SCALEY

LIVE

Founding Commercial Strategy, Scaley

The pitch is bare-metal economics with a managed-platform experience. Somebody has to keep that arithmetic true, and pointed at the right customers.

FULL-TIME · FOUNDING · REMOTE · OVERLAPPING HOURS

Apply for this role

OPENINGS

1

One. When it is filled, this page comes down.

BASE SALARY

£180,000 to £320,000

The band, published. The offer is the same whether or not you push for more.

EQUITY

0.30% to 0.80% of Scaley

Founding equity in the company you would actually work on.

01

The problem this role exists for

Scaley's argument is a cost argument wrapped in a portability argument: the same developer experience, on metal you choose, at something close to the underlying cost of compute. That claim only holds if somebody works on it continuously, because hyperscaler pricing moves, our own cost basis moves, and a comparison that was true last year becomes a liability this year.

You would own the commercial case: unit economics, pricing and packaging, which segments the argument actually lands with, and the honest competitive position against both the managed platforms and the do-it-yourself alternative. Portability is deliberately the product here, so the commercial strategy cannot rest on switching costs. It has to rest on being right.

More on the company itself: Scaley

Cost against scaleManaged platform cost rises superlinearly with traffic and team size; Scaley tracks underlying compute cost and stays close to linear.SCALE · TRAFFIC × SURFACE × TEAM →TOTAL COST →managed platformScaleyMARGIN RECLAIMEDWHERE TEAMS START ASKINGWHAT SCALEY REMOVESNo SRE hire.No certification path.No lock-in.Bare metal · AWS · colo.
Figure 1: Total cost against scale. Managed platform pricing compounds with traffic, surface and headcount. Scaley tracks the underlying cost of compute, on whatever metal you choose.

02

Your first week, and a normal Tuesday

Week one is the cost model, rebuilt from the bottom. What a workload genuinely costs us on each substrate, what the customer would pay elsewhere, and where our current pricing is either leaving money on the table or promising something we cannot hold. Expect the first version to be uncomfortable.

A normal Tuesday: model maintenance, a conversation with the architect about what a substrate decision does to unit economics, a customer call about why they have not moved yet, and a written memo. Once a quarter you rebuild the competitive comparison from scratch, because it decays faster than anybody expects.

WHAT YOU WOULD BE WORKING IN

A model you built rather than inherited, SQL against usage data, and the pricing calculators of several vendors who would rather you did not read them carefully. The deliverable is a written argument with arithmetic behind it.

We do not screen on tools. Nothing above is a requirement, and a stack list is a poor proxy for whether somebody can do the work. If you have gone deep in something else and would arrive with a view about why half of this is the wrong choice, that is an argument we would like to have.

03

What you would own

Not a ticket queue and not a slice of somebody else’s roadmap. Four things with your name against them in the decision log, from the first fortnight.

01

Unit economics

What a workload costs us, per substrate, kept true as both sides move.

02

Pricing

What we charge, what is bundled, and the case for each.

03

The comparison

Against managed platforms and against doing it yourself, honestly.

04

Segment

Who this actually lands with, and who we should stop pursuing.

04

What we are looking for

MINIMUM

What we would need to see

  • You have owned pricing, unit economics or commercial strategy where a real decision followed
  • Genuine financial modelling ability, built rather than inherited
  • Enough technical fluency to reason about compute, bandwidth and storage costs without a translator
  • You can argue against the company line with evidence and be listened to

PREFERRED

What would move you up the pile

  • Cloud, hosting or infrastructure as a market, and views on how it is priced
  • Consumption or usage-based pricing models
  • You have spoken to infrastructure buyers and know how they actually decide
  • A background technical enough that engineers do not simplify things for you

Nothing in the preferred column is a filter, and neither list is applied before a human reads you. No degree is required for anything on this page, and we have hired people with doctorates and people with no degree at all into the same rooms. If you meet most of the minimum and not all of it, write anyway and say in the first paragraph which part you do not meet.

05

Pay, and everything around it

£180,000 to £320,000 base, plus 0.30% to 0.80% of Scaley, reviewed upward annually without you having to ask. The band is published here rather than discovered three conversations in, and the offer is the same whether or not you negotiate, because the band is the band.

Everything else is what the whole group gets and is not negotiated per offer: a holiday floor rather than a ceiling, health and dental and vision for your family, sixteen to twenty weeks of parental leave for every parent, a funded setup, monthly paid group meetups somewhere in the world, one required funded trip abroad each year, a protected day a week on the research ventures, and no non-competes.

The full list, the salary band chart and the visa sponsorship map are on the careers page. We sponsor without qualification across seventeen jurisdictions and publish exactly which.

06

Apply for this role

Four steps: a conversation with somebody who would actually work with you, one real problem drawn from work we are genuinely doing, a working session on your solution, and a decision within a week of that session. The problem is paid if it runs long, and you keep the work either way.

Or write to careers@cnsolarlabs.com.

What you send here reaches us and no one else. We use it to reply to you, we do not add you to any list, and you can ask us to delete it at any time. See the privacy policy.