Founding Technical Marketer

Why this role exists

Oplane already works. Teams like Miro and Tandem Health run it on their own code, and the sales motion converts well once a buyer is in it. What we do not have is an engine that puts more of the right companies into that motion.

You are the first marketing hire, and there is no playbook waiting for you. No positioning document you inherit, no content system that runs itself, no attribution you can trust. You build all of it while it is also expected to produce demos.

It is a technical job before it is a marketing one. Our buyers are security engineers and the people who lead them, and they can tell within a paragraph whether the writer understands the architecture or is repeating a briefing. You have to be the person who understands it.

What you’ll own

Everything between “has never heard of Oplane” and “booked a qualified demo.” The route there is technical depth: research, writing and demonstrations, not campaign volume.

What the job actually is

Know the product well enough to write it

You will run Oplane yourself: connect a repo, read the threat model it produces, watch oplane-bot review a pull request, and be able to say why a finding matters and what the fix costs. Everything else in this job is downstream of that. Marketing here does not get briefed by engineers, it sits with them and then goes and writes.

Technical authority

Oplane’s credibility comes from people who genuinely understand security architecture. You do not just route that into a content calendar, you add to it: original research, teardowns of real vulnerabilities, writing about AI-generated code and agent security that a practitioner would send to a colleague. Then you build the system that keeps it running without depending on any one person’s calendar.

Positioning and ICP

Oplane runs always-on architectural threat modeling across a company’s whole stack, and it drives the fix rather than handing over a report. The hardest thing to beat in this market is not another vendor, it is a cheaper tool that looks sufficient on an audit checklist. You sharpen where Oplane wins, carry the Find, Fix, Prove narrative through everything we publish, and map the buying journey across developers, engineering leaders, AppSec, security leadership, compliance and procurement.

Product marketing and launches

Every release has to arrive as something a security engineer can evaluate: what changed, what it now catches, and what it looks like in their own repository. You own the launch narrative, the demonstration that goes with it, and the material closest to the product, including where marketing meets the docs.

Enterprise proof and enablement

Enterprise buyers arrive with hard questions about scope, cost, data handling and governance, and they have to carry the answers to their own stakeholders without us in the room. You build the customer stories, comparisons, trust material and demonstrations that let them do it.

Inbound demand and distribution

You build repeatable programs around the moments that already earn attention, meaning original security research, customer stories and partner campaigns. That includes co-marketing with lighthouse customers, and being found by the people searching for answers on threat modeling, AI-generated code, MCP and agent security, in traditional search and in AI answers alike.

Community and partners

Security engineers trust other security engineers long before they trust a vendor. You build the programs, partnerships and material that earn a recommendation from the people our buyers already listen to.

Events and stage

You pick the rooms worth being in and make sure we arrive with something to say, and can take the stage yourself when the talk is yours to give. Europe today, and increasingly the UK and US.

Funnel and measurement

Qualified demos, demo to pilot, and pilot to customer. Those are the numbers that count here, along with knowing which programs produced them. Traffic and content volume are inputs, not results. The CRM and the pipeline sit with the Head of GTM, so your time goes into demand.

Who this is for

• At least 4 years marketing a technical product to technical buyers. Security, devtools, infrastructure or developer platforms. A purely corporate marketing career does not fit here.
• You are technical enough to work in the product yourself: repositories, pull requests, CI and the coding agents your readers use every day, without a translator. You use agentic systems in your own work, and you can write credibly for the people building them.
• You have written the words yourself, recently. If the last two years were spent briefing an agency and running a team, this is the wrong role.
• You are comfortable with enterprise reality, meaning long cycles, procurement, security review, and a champion who has to sell internally without you in the room.
• You can sit with an expert and come away with something publishable in their voice. This single skill matters more here than any other.
• You have held a real publishing cadence for months, and you can say what you cut in order to hold it.
• Working language is English, and you are comfortable across markets rather than one home market. UK or US reach is a strong plus.
• Ex-founder is a real advantage, as is anyone who has built a function from nothing before.

How we work

What you get

• A product with paying customers and a sales motion that converts, so no search for product-market fit. Teams like Miro, Tandem Health, Remotive Labs and Lightbringer already run Oplane, and we are SOC 2 certified.
• Full ownership of marketing.
• 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.