R-18 · CONTINUUM

LIVE

Founding Developer Marketing, Continuum

The audience is engineers, who can tell inside a paragraph whether you have used the thing. So you will use the thing.

FULL-TIME · FOUNDING · REMOTE · OVERLAPPING HOURS

Apply for this role

OPENINGS

1

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

BASE SALARY

£170,000 to £300,000

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

EQUITY

0.30% to 0.75% of Continuum

Founding equity in the company you would actually work on.

01

The problem this role exists for

Continuum is sold to people who have been marketed at their entire careers and have an unusually good detector for it. What works with this audience is documentation that is genuinely good, technical writing that respects them, an honest comparison against the tools they already pay for, and a public presence that would survive them reading the source.

You would own the technical surface of how Continuum reaches people: docs, guides, launches, the changelog, conference talks, the community, and the writing that makes the graph argument land with somebody who has heard three vendors make similar noises this quarter.

More on the company itself: Continuum

A board versus a dependency graphColumns of cards hide the relationships between work items. The same work drawn as a directed acyclic graph exposes the critical path and the blast radius of a delay.WHAT A BOARD SHOWS YOUPosition without structure.WHAT THE SAME WORK ACTUALLY ISCritical path in red. Delay one node and the rest is computed.
Figure 1: A board reports position; a graph reports consequence. The same work, drawn two ways. Only one of them tells you what happens if something slips, and almost nobody has heard the argument yet.

02

Your first week, and a normal Tuesday

Week one you use the product properly, on a real project, and write down every place you got stuck. That list is worth more than any content calendar, and it becomes your first piece of work: fixing the documentation where you personally got lost.

A normal Tuesday: writing in the morning, because that is the job. Then a launch to prepare, a conversation with an engineer about what a feature actually does as opposed to what the ticket said, and time in whichever community is currently arguing about project management tooling. Roughly a day a week goes on documentation, permanently.

WHAT YOU WOULD BE WORKING IN

Documentation tooling, the marketing site, analytics, and working knowledge of git, because you will open pull requests against the docs yourself. Comfort in a terminal is a real requirement here rather than a nice-to-have.

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 documentation

Good enough that it is the reason somebody adopts.

02

Launches

What shipped, why it matters, in language an engineer respects.

03

The comparison

Honest, including the places the other tools are better.

04

Presence

Talks, community, and the public argument for the graph model.

04

What we are looking for

MINIMUM

What we would need to see

  • You can write, and there is published technical writing of yours we can read
  • You have marketed a technical product to a technical audience and it worked
  • You are comfortable in a terminal and can use a developer tool without hand-holding
  • You have owned documentation rather than commissioned it

PREFERRED

What would move you up the pile

  • A background as an engineer, or close enough that you read code to answer your own questions
  • Developer relations, technical writing or open-source community work
  • You have given conference talks and would like to give more
  • Familiarity with the project management tooling landscape and honest views about it

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

£170,000 to £300,000 base, plus 0.30% to 0.75% of Continuum, 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.