Integration Engineer

Sherpas; Lugo; Presencial; EUR 70.000 - 110.000; Jornada completa

Descripción de la vacante

Sherpas is seeking a backend engineer who can transform bespoke onboarding into configuration by building and maintaining connectors between custodial data, CRM and financial planning tools, resilient to external system quirks.

Success means onboarding time drops and the platform serves standard cases with minimal engineering effort. You will design for failure modes, implement robust retries, and help protect the product roadmap while enabling lean internal tooling.

Formación

• Backend engineer with real integration scars: worked with undocumented, inconsistent or rate-limited APIs.
• 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.

Responsabilidades

• Build, maintain, and harden connectors for custodial data, CRM and financial planning tools.
• Ensure data reconciles; upstream data quality is critical.
• Turn bespoke onboarding into standard configuration over code.
• Protect the roadmap by preventing onboarding from landing on ad-hoc teams.

Conocimientos

Backend engineering

API integration

Python

SQL

Tooling for others

Descripción del empleo

Role

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.

Responsibilities

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

1. A conversation about the worst integration you have dealt with and what you did about it.

2. A paid practical exercise against a realistic messy data source.

3. A working session with our engineering team.