Why this role exists
In many small and mid-sized businesses, contacts, offers, services and payments are spread across different tools. Peak One aims to turn that into one shared reality. That only works if data flows in and out cleanly, errors become visible and nobody has to guess which version is correct.
Your outcomes
- Stable, documented integrations with clear ownership for each data field.
- Visible error and conflict handling instead of silent data loss.
- Reusable patterns for new connections.
- Traceable, privacy-aware handling of transferred data.
Your day and scope
Understanding third-party APIs, mapping data fields to the shared model, building sync and error handling, monitoring integrations and clarifying with Customer Success which connections are really needed. Access to customer data only to the extent necessary.
Boundaries: You own building and running Peak One’s integrations. Core module features and the prioritisation of new connections are shaped together with other roles.
Your first 90 days
First 30 days
Understand the shared data model and existing connections; name the biggest sources of errors.
By day 60
Build one integration or fundamentally stabilise one, including monitoring and documentation.
By day 90
Have established a reusable integration pattern that makes new connections faster and safer.
What you bring
- Hands-on experience with APIs, webhooks and data sync.
- Care with failure cases, retries and conflicts.
- Basic understanding of data protection and access rights.
- Clean technical documentation.
What you can learn with us
- Our customers’ specific systems.
- Our internal data model in detail.
When this role is less of a fit
You want to wire up connections quickly without caring about failure cases, monitoring and data quality.
Compensation and conditions
We only commit to compensation, contract type, working hours and location once they are approved. We will tell you all of it concretely in the first call, before you invest time in further steps.
Your application process
Short application
Name, email and your answer to the role's entry question. CV optional.
First call
A personal conversation about the role, conditions and your questions. We cover compensation and location concretely here.
Work sample
An announced, time-boxed task: design a sync between two fictional systems using synthetic data, including conflict rules and error handling. No real APIs, no real customer data. People assess data model, robustness and explanation.
Decision
A person decides, never an AI. You always get a response.
Your entry question
„A contact was changed differently in two connected systems at the same time. How do you decide what holds in Peak One?“
Apply now