Integration Engineers

Sherpas; Santiago de Compostela; Presencial; EUR 48.000 - 64.000; Jornada completa

Descripción de la vacante

Sherpas is seeking a Backend engineer with real integration scars — you have worked with third-party APIs that were undocumented, inconsistent, rate-limited, or all three, and you think about failure modes first: retries, partial data, silent schema changes, reconciliation breaks.

You will build and maintain connectors for custodial data, CRM and financial planning tools, using Python and SQL to turn bespoke onboarding into a configurable, self-serve product and ensure data remains reconciled.

Formación

• Must have backend experience with third-party APIs (undocumented/inconsistent/rate-limited).
• Experience focusing on failure modes: retries, partial data, silent schema changes, reconciliation breaks.
• Strong Python and SQL skills.
• Experience turning bespoke onboarding into a self-serve product.

Responsabilidades

• Build and maintain connectors for custodial data, CRM, and financial planning tools.
• Configure onboarding workflows to reduce engineering time per firm.
• Ensure data reconciliation and resilience against external system issues.

Conocimientos

Python

SQL

APIs

Backend engineering

Descripción del empleo

Every firm we onboard arrives with its own custodian, its own CRM and its own back office app. Today each of those is bespoke work. Your job is to make it configuration — so the eleventh firm takes hours rather than the days the first one took.

The role

The real deliverable is not connections built. It is connections a non-engineer can configure. You succeed when you are no longer needed for the standard case — which is an unusual thing to ask of a role, and the reason it is interesting.

What you will own

The connectors: custodial data, CRM, financial planning tools — building them, maintaining them, and making them resilient to the ways external systems misbehave. Data that reconciles. In wealth management a wrong number is a regulatory problem, not a bug, and your connectors are upstream of every figure the platform produces. Turning the bespoke into the standard: configuration over code, so onboarding stops being an engineering project.

Protecting the roadmap

Without this role, onboarding work lands on whoever is nearest and product development stops.

What we are looking for

Must have Backend engineer with real integration scars — you have worked with third-party APIs that were undocumented, inconsistent, rate-limited, or all three. You think about failure modes first: retries, partial data, silent schema changes, reconciliation breaks. Strong Python and SQL. You build tooling for other people instinctively rather than keeping the knowledge in your head. Strong plus Financial data — custodial feeds, positions, transactions, performance. If you have handled these, say so early. Experience turning a services-heavy onboarding into a self-serve product. You do not need ~ Frontend skills. Someone else builds the configuration UI; you make it possible.

What success looks like

Engineering hours per firm onboarded trend down, onboarding after onboarding. A growing share of new firms are served by connectors that already exist. Time to first reconciled data set shrinks to something we can promise a client.

How we hire

# A conversation about the worst integration you have dealt with and what you did about it. # A paid practical exercise against a realistic messy data source. # A working session with our engineering team.

Send your CV or GitHub,

plus a paragraph on the worst third-party API you have integrated and what you built to survive it.