R-11 · CONSENSUS DATA TERMINAL

PILOT

Founding Product Engineer, Consensus Data Terminal

One screen that has to hold a market, a counterparty and somebody's own launch at once, without turning into a dashboard.

FULL-TIME · FOUNDING · REMOTE · OVERLAPPING HOURS

Apply for this role

OPENINGS

1

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

BASE SALARY

£200,000 to £340,000

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

EQUITY

0.50% to 1.10% of the Terminal

Founding equity in the company you would actually work on.

01

The problem this role exists for

The Terminal's competition is two categories of software people already know: one that resolves messy internal data into entities, and one that puts a live market on a screen and lets an analyst interrogate it. Both are dense, both are learned rather than intuited, and both are held to a standard of craft that most enterprise software never goes near.

You would own the surface: the interaction model, the information density, the keyboard path an expert eventually lives inside, and the ruthless editing that keeps it from becoming a dashboard with tabs. This is a product and design role held by an engineer, because there is no layer here to translate through.

More on the company itself: Consensus Data Terminal

One surface over the corpusA question typed into the Terminal is answered from three joined sources: the belief corpus, the organisation's own records, and public market data, with entity resolution and learned models in between.JOINED AT QUERY TIMEBelief corpusconviction · outcomeYour recordswhatever you holdMarket datapublic, liveCONSENSUS DATA TERMINALLIVE>what is our exposure to the Q3 capacity cut?RESOLVED ENTITIESACME LOGISTICS PLCCOUNTERPARTY412 resolved mentionsPORT OF FELIXSTOWENODEof 3 in the chainQ3 CAPACITY CUTEVENTresolved · 71% expected itMODEL OUTPUTTwo tiers of exposure, one of which nobody flagged. Confidence is stated, not implied.Illustrative. The Terminal is in early pilots.
Figure 1: One surface over the corpus. A question answered from three joined sources, with entity resolution and learned models in between. Illustrative: the Terminal is in early pilots, and the screen is a sketch of the shape rather than a product shot.

02

Your first week, and a normal Tuesday

Your first week is watching. Pilot sessions, recorded and live, including inside CN Solar Labs Capital, with one instruction: write down every moment somebody hesitated. Hesitation is what this role is graded on, and the list you produce becomes the backlog.

A normal Tuesday: a long morning building, an afternoon with a pilot user, and an argument with somebody about whether a feature earns its place on the screen. In some weeks you will delete more than you ship, and that counts here as progress rather than against you.

WHAT YOU WOULD BE WORKING IN

TypeScript and React, a serious approach to state and data fetching, and canvas or WebGL where the DOM gives up. Design tooling if you want it. Broad and negotiable: the constraint is the standard, not the library.

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

The interaction model

How an expert moves through this, including the keyboard path.

02

Density

Everything that matters on one screen, without it becoming a dashboard.

03

The hesitation list

Every moment a pilot user paused. You keep it, and you shorten it.

04

What gets cut

The editing. Most of the quality here comes from what is not on the screen.

04

What we are looking for

MINIMUM

What we would need to see

  • You have built an interface experts used daily, and you can point at the craft in it
  • Strong TypeScript and modern React, with opinions about state and data fetching you can defend
  • You have sat with users rather than reading research about them
  • Taste, and the willingness to argue for it in a review

PREFERRED

What would move you up the pile

  • Financial terminals, professional tools, IDEs, or anything with a keyboard-first expert mode
  • Canvas or WebGL rendering where the DOM was not enough
  • A formal design background, or self-taught to the same standard
  • Accessibility on genuinely dense interfaces, which is the hard version of that problem

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

£200,000 to £340,000 base, plus 0.50% to 1.10% of the Terminal, 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.