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.