Forward-Deployed Engineer

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

Originally posted on Himalayas