Why this role exists
Oplane is not a tool people buy and forget. It runs inside the coding loop, it finds real architectural risk in code that is still being written, and it only pays off when a customer’s engineers actually change what they do with it. Right now the people who make that happen are two founders and two customer-facing engineers, and there is no owner for what happens after a contract is signed.
You are that owner, and you are building the function from nothing. There is no onboarding playbook, no health model, no renewal motion. You will write all three while running live accounts yourself.
What you’ll own
Everything after “yes.” Pilot, onboarding, adoption, retention and expansion, plus the proof that comes out of happy customers.
What the job actually is
- Run pilots to a real outcome
- Our pilots are short and strict, and success is a customer seeing a genuine finding in their own code and fixing it. You own that path from kickoff to decision.
- Understand the customer’s work better than they expect you to
- How they ship, what their review process actually looks like, where security slows them down, who inside the company is under pressure and why. This is the core of the job. If you are not curious about somebody else’s engineering org, you will not enjoy it here.
- Get Oplane properly embedded
- Into their repos, their CI, their pull request flow and their coding agents. You will be hands-on with technical setup, working alongside our engineers rather than handing it to them.
- Build the retention system
- Health signals, adoption milestones, the difference between a customer who is using it and a customer who is depending on it. Then renewals and expansion, which follow from that rather than from a QBR calendar.
- Turn success into proof
- Customer stories, references, joint sessions with our marketing and sales work. Our buyers trust other practitioners far more than they trust us, so the accounts you make successful become the reason the next ones sign.
- Feed the product
- You will see every place the product creates friction before anyone else does, and we expect that to reach the engineers directly rather than through a quarterly summary.
Who this is for
- At least 4 years owning customers in a technical B2B product. We are looking for someone who has already done this well, not someone learning it here.
- You can point at retention and expansion numbers you personally influenced, and explain what you did to move them.
- You have genuinely spent time in the field with customers, in their tools and their meetings, making somebody’s job measurably easier. This is not a role for someone whose experience is ticket queues and renewal reminders.
- You are technical enough to talk about repositories, pull requests, CI pipelines and coding agents without a translator.
- You understand agentic systems at a level that lets you hold a real conversation with the engineers you are serving.
- Startup or scale-up background. A purely corporate career does not fit here.
- Your network and comfort zone extend beyond one home market. UK and US experience is a strong plus.
- Ex-founder is a real advantage, as is anyone who has built a function from nothing before.
- Working language is English.
How we work
Small team, ten of us today, real autonomy, and nothing between deciding something and doing it. We are honest about what is hard, including in this ad. We grow through agents rather than headcount, so the job is always to build the system that does the work rather than do the work by hand forever. Nobody here asks permission first. If you see it, do it, and tell us afterwards.
Our mission is to fix software for good. Security expertise should be software rather than a person you book time with, and that is a big enough problem to spend a career on.
What you get
- Real enterprise customers already live, so you are keeping and growing accounts rather than waiting for the first one. Teams like Miro, Tandem Health, Remotive Labs and Lightbringer already run Oplane, and we are SOC 2 certified.
- Full ownership of customer success.
- Backed by Seed Capital and Icebreaker.vc, with angel investors from Neo4j and Google, including Emil Eifrem. $5.2M seed.
- On-site five days a week, in either Stockholm or Malmö. This is an in-person team by design, not a distributed one. Most of the team sits in Malmö and we get everyone in a room regularly.