Back to jobs

Forward-Deployed Engineer

Pay
Pay not listed
Work setting
Working pattern needs review — work setting source
Not pre-sales quota-carrying. You join conversations for technical depth, not to close. Not full-time on-site embedding. Client contact is regular but structured: calls, workshops. Not a support queue. You own outcomes for accounts, not tickets.
Read the full posting
Employment
Contract — employment source
Employment type in the employer’s posting: Contract
From the employer’s posting

What you’ll work on

Full posting
  • Run technical onboarding discussions with client IT teams (architecture, security, SSO)

  • Own client accounts after go-live: adoption, expansion and quarterly reviews

  • Build client-specific configurations, integrations and glue code

  • Turn recurring client requests into structured product requirements

  • Prototype solutions, validate with clients, then hand off generalizable parts to engineering

From the employer’s posting
Run technical discussions during onboarding: architecture reviews, security questionnaires, SSO and data-flow conversations with client IT teams
Own accounts after go-live: adoption, expansion, the quarterly “how is this actually going” conversation
Help build client-specific configuration, integrations, and glue code (SSO, data mappings, API integrations, etc.)
Turn recurring client asks into structured product requirements and argue for them with the product team
Prototype solutions fast, validate them with the client, then hand the generalizable parts to the engineering team

What you’ll bring

All qualifications

Core experience

  • 3+ years in a technical role with client exposure
  • Able to read and write production code
  • Comfortable leading technical discussions with varied audiences
  • Financial services background, or fast absorption of regulated domains
  • Clear writing for requirement docs, runbooks and follow-up emails
Qualification wording
3+ years in a technical role with client exposure
You can read and write production code
You can hold a room
Financial services background, or evidence you absorb regulated domains fast.
You write clearly: Requirement docs, runbooks, and follow-up emails carry most of this job’s leverage.
Apply at Tangible

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
4
Last seen by us
Nov 21, 2026
Employer says posted
Jul 23, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 3

Similar jobs usually come down between day 3 and day 42.

From 633 similar postings that came down. Coming down is not always a hire.

Tangible is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume to compare the role’s scope, tools and requirements with your experience.

Your next step

Complete your application on join.com. The employer’s form will show what is required.

Already applied? Track this application

Job description

View original posting ↗

Tangible Markets builds secondary-transaction infrastructure for private markets. Our clients are banks, fund administrators, and secondaries teams whose workflows are technical, regulated, and specific. You sit between them and our product engineering.

The role blends solutions engineering with customer success, plus real engineering work. You lead technical discussions with clients, shape how the platform fits their workflow, own their success after go-live, and help build configurations and integrations that close the gap. You are not embedded on client sites full-time, and this is not a pure relationship role either. Most weeks split between client-facing work and hands-on technical work.

Full-time · Remote (European time zones preferred)

Tasks

Client-facing (roughly half the role)

  • Run technical discussions during onboarding: architecture reviews, security questionnaires, SSO and data-flow conversations with client IT teams
  • Translate client workflow requirements into product terms, and product capabilities into client terms
  • Own accounts after go-live: adoption, expansion, the quarterly “how is this actually going” conversation
  • Be the trusted technical contact when something breaks or a new requirement lands

Product and engineering (the other half)

  • Help build client-specific configuration, integrations, and glue code (SSO, data mappings, API integrations, etc.)
  • Turn recurring client asks into structured product requirements and argue for them with the product team
  • Prototype solutions fast, validate them with the client, then hand the generalizable parts to the engineering team
  • Write the runbooks and docs that make each client’s setup maintainable by someone other than you

Requirements

  • 3+ years in a technical role with client exposure: solutions engineering, sales engineering, technical account management, or product engineering with heavy customer contact.
  • You can read and write production code: You don’t need to be the strongest or only engineer on the team, but “I’ll build it” has to be a real option, not a handoff.
  • You can hold a room: an SSO deep-dive with a bank’s IT security team in the morning, a product feedback session in the afternoon.
  • Financial services background, or evidence you absorb regulated domains fast.
  • You write clearly: Requirement docs, runbooks, and follow-up emails carry most of this job’s leverage.
  • Judgment about what to build, what to configure, and what to push back on.

Nice to have:

  • Anything fintech, especially on the vendor for banks (or other fintechs) side.
  • Prior work at an early-stage B2B company where you wore several hats.
  • Familiarity with enterprise security and compliance processes (vendor due diligence, DORA, GDPR).

What this role is not:

  • Not pre-sales quota-carrying. You join conversations for technical depth, not to close.
  • Not full-time on-site embedding. Client contact is regular but structured: calls, workshops.
  • Not a support queue. You own outcomes for accounts, not tickets.

Why this role matters:

Enterprise clients in private markets churn because nobody on the vendor side understood their workflow well enough to make the platform fit. This role exists so that someone does, and so that what they learn changes the product.

Process:

  1. 30-minute intro call
  2. Technical conversation around a real (anonymized) client scenario
  3. Working session: scope a solution and present it back
  4. Conversation with the founders

Demand for Forward Deployed Engineer roles

New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.

Weekly new Forward Deployed Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 51, the most 267, and the latest week had 217.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Forward Deployed Engineer, by the work the posting describes.

Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.

Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.

An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

London, United Kingdom

The role blends solutions engineering with customer success, plus real engineering work. You lead technical discussions with clients, shape how the platform fits their workflow, own their success after go-live, and help build configurations and integrations that close the gap. You are not embedded on client sites full-time, and this is not a pure relationship role either. Most weeks split between client-facing work and hands-on technical work. Full-time · Remote (European time zones preferred) Tasks
More source context
- Not pre-sales quota-carrying. You join conversations for technical depth, not to close. - Not full-time on-site embedding. Client contact is regular but structured: calls, workshops. - Not a support queue. You own outcomes for accounts, not tickets.
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.