CAREERS · CN SOLAR LABS

Small teams. Unsolved problems. Nothing between you and the work.

We are building the correlation engine that makes outages preventable, the platform that makes deployment portable, and the coordination layer that makes a launch legible. These are not staffed like feature teams. They are staffed like founding teams, because that is what they are.

What it is actually like

You will own a surface, not a ticket queue. The person who decides how a thing works is the person building it, and the review that matters happens with someone who read the code rather than the summary. There is no product manager translating between you and the problem, because there is no layer to translate through.

The cadence differs by company, on purpose. RACD moves at the speed of a research result and is measured that way. Platform ships weekly. Partner work ships daily, in front of an operator who will tell you immediately whether it helped. Matching the cadence to the problem is one of the six things we hold ourselves to.

If you have ever been the person who fixed it at 03:00 and then rewrote the thing so it could never happen that way again: you already work the way we work.

Figure 1: Shipping cadence by venture type. The wrong speed is as expensive as the wrong direction.

TEAM SHAPE

Founding

Small teams with real ownership and a direct line to the founder.

LOCATION

Remote-first

Overlapping hours matter more to us than a postcode. Hybrid where the work is client-facing.

UPSIDE

Equity

Meaningful ownership in a group whose valuation base is growing.

Open roles

Founding Engineer, RACD

RACD

FULL-TIME · FOUNDING · REMOTE · OVERLAPPING HOURS

Correlation across heterogeneous, high-cardinality signal. You will be arguing about causality, not about dashboards.

▸Time-series, streaming systems, or statistical anomaly detection at production scale
▸A strong opinion about why current alerting fails, backed by scar tissue
▸Comfort with the possibility that the right answer is a research result, not a sprint

Platform Engineer, Scaley

SCALEY

FULL-TIME · FOUNDING · REMOTE · OVERLAPPING HOURS

Build the deploy pipeline, the scheduler, and the edge layer that make one command work identically on bare metal and on someone else's cloud.

▸Containers, orchestration, and networking below the abstraction everyone else stops at
▸Build systems, caching, and the unglamorous parts of making deploys fast
▸You have run infrastructure at 03:00 and formed opinions about it

Product Engineer, Continuum

CONTINUUM

FULL-TIME · REMOTE · OVERLAPPING HOURS

A spatial graph canvas that stays fast at ten thousand nodes and legible to someone who has never opened it before.

▸TypeScript, React, and real rendering-performance work: canvas, WebGL, or virtualised DOM
▸Graph layout, or the appetite to become excellent at it quickly
▸Design taste you are willing to defend in a review

Data Engineer, Consensus

CONSENSUS

FULL-TIME · REMOTE · OVERLAPPING HOURS

Turn a live social product into a research-grade corpus: resolution integrity, calibration scoring, and the schema the whole thesis rests on.

▸Event pipelines, warehousing, and a real instinct for data quality
▸Interest in calibration, scoring rules, or forecasting literature
▸Willingness to defend the integrity of a dataset against product convenience

Solutions Engineer, Gravity Lock

GRAVITY LOCK

FULL-TIME · HYBRID · CLIENT-FACING

Sit with the operator, find the bottleneck, and ship the thing that removes it, usually within the week.

▸Full-stack shipping speed and genuine comfort in front of a non-technical owner
▸Automation instinct: you see a manual process and reflexively cost out its removal
▸Ownership of an outcome rather than a ticket

General Application

GROUP

OPEN · REMOTE OR HYBRID

If you are exceptional and none of the above is the right shape, write to us anyway. We have created roles for people before and will again.

▸Evidence of something you built that did not have to exist
▸A specific reason this group, and not another one

How hiring works

A conversation, not a screen

Forty-five minutes with someone who will actually work with you. We talk about what you have built and what broke. No riddles, no reversing a linked list.

One real problem

Drawn from something we are genuinely working on, scoped to a few hours, paid if it takes longer. You keep the work either way.

Working session

We sit down together on your solution and push on it. This is the closest simulation of the job we can build, and it is the part that decides.

Offer, fast

A decision within a week of the working session. If it is a no, you get the actual reason.

Apply

Name the role, or do not. We have created roles for people before and will again. What we read first is the thing you built and what you learned when it broke.