Forward Deployed Engineer

edenity.; Amsterdam; On-site; EUR 85,000 - 140,000; Full time

Job summary

edenity. is building forward deployed engineering roles to solve complex customer problems at the intersection of product and engineering.

You'll own end-to-end technical deployments, from understanding customer context to delivering working solutions, while maintaining high quality and pragmatism in a scalable platform.

Qualifications

• Strong software engineering foundation and production code experience.
• Experience across product, full-stack or backend engineering.
• Comfort with APIs, integrations, configuration and application logic.
• Ability to debug unfamiliar systems and identify root causes quickly.
• Good technical judgement without over-engineering.
• Clear communication with engineers and customers.

Responsibilities

• Understand customer context and technical environment to identify core problem.
• Build integrations, configure the platform, debug and extend the product in complex environments.
• Abstract common patterns to inform tooling, infrastructure, or core product capability.

Skills

Software fundamentals

Full-stack engineering

Backend engineering

APIs & integrations

Configuration & app logic

Customer-focused debugging

Technical judgment

Communication with engineers and what?

Job description

Business identity is still fundamentally broken.

We’re partnering with one of Europe’s fastest-growing RegTech companies, building the infrastructure that allows businesses to prove who they are, who owns them and whether they can be trusted.

Founded by former leaders from one of the fastest growing fintechs globally, they’ve raised €40m+ from globally leading technology investors and built a deliberately small, high-calibre team with experience across companies including Stripe, Adyen, Google, Apple, Spotify, Miro and Klarna.

They’re already working with sophisticated banks, fintechs and technology platforms, but the ambition goes well beyond better compliance software: build the infrastructure for portable business identity across companies, financial institutions and borders.

It’s a large, technically difficult problem. And as the company scales, solving it increasingly happens at the intersection of product, engineering and the customer.

Why this role exists

As customers become larger and more complex, there is an important technical layer between what the core platform can do and what a specific customer needs it to do.

Every customer brings a different architecture, workflow, policy environment and set of edge cases.

Push all of that complexity into core engineering and you compromise the product. Treat it as implementation or customer success and you lose the technical depth required to solve it properly.

The Forward Deployed Engineer sits in between.

The role

You’ll own complex technical problems from customer context through to working solution.

That might mean building an integration, configuring the platform, debugging unexpected behaviour, writing code on top of the core product or recognising that a customer problem reveals something the product itself needs to solve.

You’ll work across three broad areas:

Understand. Get close enough to customers and their technical environment to understand the problem beneath the request.

Build. Integrate, configure, debug and extend the product to make it work within complex customer environments.

Abstract. Identify patterns across deployments and help determine what should become tooling, infrastructure or core product capability.

This is not technical customer success or solutions engineering with a new title.

As an engineer, you'll still build.

The difference is that you’ll operate with significantly more customer and product context than most engineering roles give you.

What great looks like

We’re looking for someone with a strong software engineering foundation, likely from product, full-stack or backend engineering, who wants to move closer to customers without moving away from building.

You’re comfortable when the problem isn't perfectly defined. You can understand the customer context, get into the technical detail and work out the most pragmatic route forward.

You care about quality, but you're not a perfectionist.

You investigate before you patch.

And other engineers trust what you ship.

You’ll likely bring:

• Strong software engineering fundamentals and experience shipping production code
• Comfort across APIs, integrations, configuration and application logic
• The ability to debug unfamiliar systems and get to root causes quickly
• Strong technical judgement without a tendency to over-engineer
• Product instinct: the ability to question the problem, not just implement the request
• The ability to manage multiple technical workstreams without losing context
• Clear communication with both engineers and customers
• Comfort operating with significant autonomy

Experience in RegTech, fintech, payments, KYC/KYB, identity or similarly complex infrastructure is useful, but not essential.

Technical range, judgement and learning velocity matter more.

Where we think we might find you

We have hypotheses, not a rigid archetype.

• A product or full-stack engineer at a high-growth company who naturally gets pulled into difficult customer problems
• An integration engineer within payments, RegTech, fintech or infrastructure
• A genuinely hands-on solutions engineer who wants to spend more time building
• An engineer already working in a forward deployed model within data, infrastructure or AI
• Someone whose current title doesn't quite describe the combination of engineering and customer work you're already doing

The underlying combination is what matters:

What you'll help build

The interesting question isn't simply how to solve one customer's implementation.

It's:

How do you make a sophisticated product work for increasingly complex customers without building a different product for every customer?

• You'll sit in one of the best positions in the company to answer that.
• You'll see where customers repeatedly struggle, where better tooling could remove complexity, which requirements should influence the product and where deployment should own the solution instead.
• This is an early role in a new function, so you won't inherit a mature playbook.
• You'll help create it.
• And you'll be doing that alongside an engineering team with an unusually high bar. This is a company that has been intentionally selective about who joins, bringing together people from some of Europe's strongest engineering and product environments rather than scaling headcount for the sake of it.

Why now

The product is scaling. The customers are becoming more sophisticated. And the technical problems at the edge of the platform are becoming more interesting.

This is an opportunity to join early enough to help define how forward deployed engineering works here, surrounded by people with an unusually high technical bar, while staying firmly in the work itself.

Close enough to the customer to understand the real problem. Technical enough to solve it. Experienced enough to know what should be solved differently next time.