Integration Engineer

Sherpas; Huelva; Presencial; EUR 60.000 - 90.000; Jornada completa

Descripción de la vacante

Sherpas is looking for a backend engineer who can turn bespoke integrations into standard, self-serve configurations. You will build and maintain connectors for custodial data, CRM, and financial planning tools, focusing on reliability and data accuracy.

You should thrive on failure modes, API integration challenges, and building tooling that others can use. This role emphasizes turning onboarding into an efficient, repeatable process across multiple firms.

Formación

• Experience with undocumented or unstable third-party APIs.
• Designing for failure: retries and reconciliation breaks.
• Strong Python and SQL.
• Build tooling for others, not just yourself.
• Experience with custodial financial data feeds: positions, transactions, performance.
• Experience turning onboarding into a self-serve product.

Responsabilidades

• Own connectors between custodial data, CRM, and planning tools; build, maintain, and make them resilient.
• Ensure data reconciles correctly; upstream data accuracy is critical for regulatory reasons.
• Turn bespoke onboarding into standard, configuration-based processes.
• Protect the roadmap by reducing ad-hoc onboarding work.

Conocimientos

Python

SQL

API integration

Data wrangling

Frontend basics

Testing & reliability

Herramientas

Postman

SQL clients

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.
• 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.
• 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.