Why this role exists
In Peak One, all modules work on one shared data model: people, companies and tasks exist once, not as a separate copy in every module. That is the platform’s strength and also an obligation. Every change has to fit across interface, logic and data.
Your outcomes
- Features implemented consistently across all layers.
- A shared data model without hidden parallel copies.
- Tested, documented code others can pick up.
- Noticeably fewer bugs and workarounds in your areas.
Your day and scope
Building interfaces and APIs, extending data models, planning migrations, writing tests, reviewing code, analysing bugs and paying down technical debt deliberately. AI-assisted development is routine; every change is understood and owned by people.
Boundaries: You own technical delivery across frontend, backend and data in your areas. Product prioritisation and cross-cutting architecture decisions are made together with others.
Your first 90 days
First 30 days
Get to know the codebase, data model and delivery path; ship first bug fixes and small changes.
By day 60
Own a change that touches interface, API and data model together.
By day 90
Reliably look after one area of Peak One and have delivered one documented improvement to stability or maintainability.
What you bring
- Hands-on experience in frontend and backend development.
- Solid understanding of relational data models.
- Discipline with tests, reviews and documentation.
- Willingness to review others’ and AI-generated code critically.
What you can learn with us
- Our specific codebase and conventions.
- The domain logic of our modules.
When this role is less of a fit
You want to focus on a single layer only, or you consider tests and documentation optional.
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 on a fictional sample application: add a feature across interface, API and data. No real Peak Atlas code, no real data. People assess structure, data model, tests and explanation.
Decision
A person decides, never an AI. You always get a response.
Your entry question
„A new module needs contact data. How do you prevent a second, diverging copy of the contacts from appearing?“
Apply now