Integration Engineer

Sherpas; Tarragona; Presencial; EUR 50.000 - 80.000; Jornada completa

Descripción de la vacante

Sherpas is seeking a Backend Engineer in Tarragona, Spain, to build and maintain connectors spanning custodial data, CRM, and financial planning tools.

You will make onboarding configurable and reduce engineering dependence by turning bespoke setups into standard processes.

Formación

• Backend engineer with integration experience using undocumented or unstable APIs.
• Ability to design for failures: retries, partial data, and reconciliation.
• Strong Python and SQL skills for data connections.
• Build tooling for others, not just core engineers.
• Frontend skills enabling a configurable UI for non-engineers.

Responsabilidades

• Build and maintain connectors for custodial data, CRM, and financial planning tools.
• Ensure data reconciles accurately and is compliant with regulations.
• Transform bespoke onboarding into standard configurations to reduce engineering work.
• Protect the product roadmap by enabling scalable onboarding.

Conocimientos

Integration experience

Failure modes

Python

SQL

Frontend UX tooling

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. xqziphu
• A working session with our engineering team.