Embedded finance hiring playbook: the 7 roles every fintech needs, and where to find them
The seven roles that distinguish an embedded-finance team that ships from one that stalls — what each role actually does, the seniority that works, and the European markets where each is most reliably sourced.
Embedded finance hiring playbook: the 7 roles every fintech needs, and where to find them
Embedded finance has moved decisively from "interesting hypothesis" to "the default integration pattern for any non-banking company that wants to monetise a payment flow." The 2024 a16z fintech outlook called this consolidation explicitly, and the operational data backs it: nearly every B2B SaaS company of meaningful scale now either offers embedded payments, lending, or banking, or is actively scoping it.
But staffing an embedded-finance product is a distinct problem from staffing a vertical neobank or a payments processor. The team composition is non-obvious. Companies that fund their embedded-finance roadmap with two backend engineers and a PM and assume that suffices, do not ship. Companies that build the seven-role shape below, ship.
This piece is that shape.
The seven roles
The team composition we consistently see succeed for embedded finance in 2026 is a seven-role function. Not seven people — several of these roles can be combined or fractional at smaller scale — but seven distinct capabilities that must be present.
- Embedded-finance product lead — owns the roadmap and the BaaS-partner relationship
- Payments / banking-rails engineer — implements the actual money movement
- Identity, KYC, and KYB engineer — implements onboarding and ongoing customer due diligence
- Risk and underwriting engineer — implements credit, transaction, and merchant risk decisions
- Compliance officer (or MLRO) — owns the regulatory posture and reporting obligations
- Fraud operations specialist — runs the real-time fraud monitoring and case investigation
- Payments operations specialist — owns settlement, reconciliation, disputes, and partner ops
Below: what each role does, the seniority that works, the realistic Balkan / EU market for sourcing each, and what a junior-vs-senior split typically looks like.
1. Embedded-finance product lead
The single role that most determines whether the function ships. The product lead translates between three constituencies whose vocabularies do not naturally align: the company's existing product organisation, the BaaS partner (Stripe Treasury, Adyen, Marqeta, Galileo, ClearBank, Modulr, Solaris), and the regulator (through the compliance officer).
Seniority: senior PM with payments background or ex-fintech founder. A junior PM, however capable, lacks the regulatory and partner-relationship instincts to manage the role.
Where we source: Lisbon, Belgrade, Zagreb, and the wider operator pool that has graduated from Wise, Revolut, and Adyen. Single-market depth is limited; this is typically a curated search rather than a bench draw. See product specialisations on /services.
2. Payments / banking-rails engineer
Implements the integration to the BaaS partner: account opening, transaction initiation, webhook handling, reconciliation hooks, customer-facing balances. This is the most technically substantive engineering role on the team.
Seniority: senior backend engineer with prior payments integration work. The pattern matters more than the specific rail — an engineer who has integrated Stripe Treasury will be productive against Adyen Embedded in two weeks; an engineer who has only built CRUD APIs will be productive against either in 90 days.
Where we source: Belgrade, Lisbon, Warsaw, and Berlin. The senior payments-engineering bench across the Balkans (covered in our Serbia hiring guide) is genuinely strong here.
Senior-junior split: at any reasonable scale, one senior plus two mids. The senior owns architecture and partner-facing decisions; the mids ship features against a clear technical pattern.
3. Identity, KYC, and KYB engineer
Implements the integration to the identity provider (Onfido, Veriff, Sumsub, Trulioo) and the orchestration around it: liveness, document capture, watchlist screening, KYB (Know Your Business) for merchant onboarding, ongoing CDD. Frequently combined with role 2 at smaller scale; should be a distinct role above ~50 onboardings per day.
Seniority: senior backend engineer with KYC/KYB pipeline experience.
Where we source: Bucharest and Belgrade are particularly strong here, partly because of the operator pool that came through Bitstamp, eToro Europe, and Trayport.
4. Risk and underwriting engineer
The role that determines whether the product survives contact with adverse selection. Implements transaction risk decisions, merchant underwriting (where applicable), credit decisions (where applicable), and the feedback loops that update each. Increasingly, this role is an applied-ML role.
Seniority: staff or senior engineer with applied ML and a fraud / credit context. This is the hardest single role to fill in Europe.
Where we source: Belgrade has surprising depth here, as does Bucharest. Berlin and Vilnius are options at substantially higher cost. See AI specialisations.
5. Compliance officer or MLRO
Owns the regulatory posture: the registration or licensing relationship, the AML programme, the regulatory reporting (transaction reporting, SAR/STR filings), the response to regulatory inspection. For a UK firm operating under the FCA's e-money or payment-services regime, the MLRO is a regulator-approved appointment. For a firm operating embedded via a BaaS partner's licence, the compliance role is non-supervised but functionally critical.
Seniority: senior, with direct regulator-facing experience at a PSP, EMI, or licensed neobank.
Where we source: Berlin, Vilnius, Zagreb, and the wider London / Dublin pool now working remotely. Substantial bench in Berlin and Vilnius; thinner in the Balkans but improving rapidly.
6. Fraud operations specialist
Runs the case queue: investigates flagged transactions, decisions account-level interventions, manages chargeback and dispute responses, refines the rules with data from outcomes. Frequently confused with role 4 (the risk engineer) but distinct — the fraud ops specialist is operations, not engineering.
Seniority: mid to senior, with at least 18 months in a live fraud operations role.
Where we source: Bucharest, Sofia, and Athens have strong depth at this level. Lisbon is competitive. See operations specialisations.
7. Payments operations specialist
Owns settlement reconciliation against the BaaS partner, the chargeback and dispute lifecycle, partner-bank correspondence, and the day-to-day operations that keep money moving correctly. Underrated role; embedded-finance products that have shipped frequently fail at the boundary between product and ops, and this role is the primary defence.
Seniority: mid to senior, with prior payments-operations experience (settlement, recon, disputes).
Where we source: Bucharest, Belgrade, and Sofia.
Team-build sequencing
For a B2B SaaS company adding embedded payments to an existing product, the order in which to hire matters. A common mistake is hiring engineering ahead of compliance, then discovering at month four that the product as designed cannot be operated within the regulatory envelope of the chosen BaaS partner.
The order we recommend:
| Month | Hire | Notes | | --- | --- | --- | | 0 | Product lead | Owns the BaaS partner selection alongside the compliance hire | | 1 | Compliance / MLRO | Pulled in early to scope the regulatory envelope | | 2 | Payments-rails senior engineer | Anchors the implementation team | | 3 | Risk engineer + KYC engineer | First wave of implementation specialists | | 4 | Two mid backend engineers | Scales implementation throughput | | 5 | Fraud ops + payments ops | Pulled in ahead of beta launch |
A team of nine at month six, sequenced this way, ships an MVP embedded-banking product to first revenue in approximately seven months from kick-off. A team of nine assembled in a single hiring sprint typically takes twelve to fifteen months because the upstream-downstream dependencies were not respected.
What this costs in the Balkans
Indicative monthly loaded cost, sourcing seven of the nine seats from the Balkans (the two seats we recommend keeping local or in Berlin/Vilnius are compliance and the senior risk engineer):
| Role | Seat count | Sourcing | Loaded EUR/month | | --- | --- | --- | --- | | Product lead | 1 | Belgrade or Lisbon | €9,500 | | Compliance / MLRO | 1 | Berlin or Vilnius | €11,000 | | Payments-rails senior | 1 | Belgrade | €8,500 | | Risk engineer (staff) | 1 | Vilnius or Berlin | €12,000 | | KYC engineer (senior) | 1 | Bucharest | €7,000 | | Backend mid | 2 | Belgrade or Bucharest | €11,000 | | Fraud ops specialist | 1 | Sofia | €5,500 | | Payments ops specialist | 1 | Bucharest | €5,500 | | Total | 9 | | €70,000/month |
For comparison, the same nine-seat function in London prices at €170,000–€200,000 fully loaded. In New York, USD 220,000–280,000.
Where this goes wrong
The two most common failure modes we see, listed so you can avoid them:
- Underweighting compliance until too late. The product lead and the compliance officer should be hired in the same fortnight. If compliance arrives at month four, the engineering work to date is at risk of substantial rework against the regulatory envelope the BaaS partner will accept.
- Hiring "full-stack" rather than role-specific. Embedded finance is the wrong product for generalist senior engineers. The integration patterns, the partner constraints, and the risk surface reward specialisation. A team of five role-specific seniors will out-ship a team of seven generalists, every time.
For a deeper view of where to source each role at the right seniority, see the Croatia / Romania / Serbia comparison and the European operations talent piece. For commercial structure, engagement models. To scope a specific build-out, contact us.
