Forward Deployed Engineer

Oplane; Malmö kommun; On-site; SEK 700,000 - 1,100,000; Full time

Benefits offered by this job

On-site in Malmö

SOC 2 certified

Seed capital backing

Job summary

Oplane is seeking a hands-on engineer to embed our platform inside customer development loops. You will deploy into their environments, build what is missing, and transform lessons into reusable tooling and documentation.

In this role you own the end-to-end path from contract to a live integration, work directly with customer engineers, and help shape the product by surfacing rough edges for the team. English language required; Malmö on-site, five days a week.

Qualifications

• Around 6 years in engineering with real time spent in customer-facing technical work.
• Fluent in English and excellent communication in technical conversations.
• Writes production code, not just configuration; comfortable with being the sole Oplane engineer with customers.
• Proven ability to hold two loyalties – customer needs and product goals – and to discern bespoke requests.

Responsibilities

• Deploy Oplane into environments you do not control, including self-hosted runners and air-gapped setups.
• Build integrations, adapters, scripts, migrations, and bespoke tooling as needed.
• Maintain technical trust in pilots, security reviews, and architecture discussions with customers.
• Provide feedback to product by surfacing rough edges and driving fixes straight to engineering.
• Create reusable tooling and documentation to scale deployments for future customers.
• Collaborate daily with engineers, including in customer-facing contexts, using coding agents.

Skills

Python

TypeScript

Git

CI systems

GitHub

GitLab

Tools

Python

TypeScript

Git

CI systems

GitHub

GitLab

Job description

Go to the customer, make Oplane fit their environment, build what is missing, and bring back what you learned.

Oplane only works when it is inside a customer’s actual development loop: their repositories, their CI, their pull request flow, their coding agents. No two of those look the same. A company with thousands of engineers has a monorepo, a review process, a compliance regime and a set of internal tools that nobody outside it has seen, and getting Oplane to fit that is engineering work, not configuration.

You are the engineer who goes to the customer. You make Oplane fit their environment, you build what is missing, and you bring back what you learned so the next customer needs less of you.

What you’ll own

The path from signed contract to Oplane genuinely embedded in a customer’s engineering org, and the integrations and tooling that make that path shorter each time.

What the job actually is

• Deploy Oplane into environments you do not control. Self-hosted runners, air-gapped constraints, unusual CI topologies, monorepos, GitHub Enterprise and GitLab installations with years of local convention on top. You are hands‑on in the customer’s systems, alongside their engineers.
• Build what the customer needs and we do not have yet. Integrations, adapters, scripts, migrations, whatever stands between them and value. Some of it stays bespoke. The good parts become product, and knowing which is which is part of the job.
• Own technical trust in the room. You are the person their engineers and their security team test their hardest questions on, in pilots, security reviews and architecture discussions. Our Founding Customer Success Lead owns the relationship and the commercial outcome; you own whether the technical answer holds.
• Close the loop back into the product. You see every rough edge before anyone else does, with a real customer attached to it. That goes straight to the engineers who can fix it, not into a quarterly summary.
• Make yourself less necessary each time. The point is not to become the human who onboards every account forever. Every deployment should leave behind tooling, defaults and documentation that make the next one mostly automatic. We grow through agents rather than headcount, and this function has to scale that way too.
• Build the agentic way, because we mean it. This is a deeply agent‑native codebase: our docs are written for coding agents to read, an agent reviews our pull requests, and we build for a world where agents write most of the code. You will plan, build and review with agents every day, including in customer work.

Who this is for

• Around 6 years in engineering, with real time spent in customer‑facing technical work. Forward deployed, solutions engineering, professional services, or the engineer who always ended up on the hardest accounts.
• You are a genuine engineer who writes production code, not a consultant who configures. Python and TypeScript are where our work happens.
• You are fluent in the developer toolchain our customers live in: Git, CI systems, containers, GitHub and GitLab at organization scale.
• You are comfortable being the only Oplane engineer in a room full of somebody else’s engineers, including when the news is bad.
• You can hold two loyalties at once, to the customer in front of you and to the product that has to serve everyone else, and you know when a bespoke request should be refused.
• You use coding agents seriously in your own work.
• Security experience is a real plus, especially anything involving customer code, secrets or access review.
• Startup or scale‑up background, and comfortable owning this function alone at first.
• Working language is English.

What you get

• Real enterprise customers already live, so you are deploying into serious engineering orgs from week one. Teams like Miro, Tandem Health, Remotive Labs and Lightbringer already run Oplane, and we are SOC 2 certified.
• Full ownership of how Oplane gets deployed, building the function from nothing.
• Backed by Seed Capital and Icebreaker.vc, with angel investors from Neo4j and Google, including Emil Eifrem. $5.2M seed.
• Based at our Malmö office, on‑site five days a week. This is an in‑person engineering team by design, not a distributed one.

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.