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.
London, United Kingdom
Actively hiring, first seen by us 3 days agoNot 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 type in the employer’s posting: ContractFrom the employer’s 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
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
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.
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
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.
1 open job
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume to compare the role’s scope, tools and requirements with your experience.
Complete your application on join.com. The employer’s form will show what is required.
Already applied? Track this application
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)
Client-facing (roughly half the role)
Product and engineering (the other half)
Nice to have:
What this role is not:
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:
New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
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
- 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.
No clear work-authorization passage found. Eligibility is unconfirmed.