Why this role exists
Peak One is the central platform of Peak Atlas. Modules should not keep their own copies of data but work on one shared data model. That only works with a platform layer that offers clear interfaces, clean permissions and stable building blocks – so new modules can be built faster and with fewer errors.
Your outcomes
- One shared data model with clear, documented interfaces.
- Reusable building blocks, for example for permissions, events and logging.
- Traceable changes to the data model without breaking existing modules.
- A platform on which product teams can build new features without detours.
Your day and scope
Designing and building platform components, code reviews, aligning with product and design on new modules, working on tests and documentation. You use AI tools as a matter of course – responsibility for architecture and code stays with you and the team.
Boundaries: You own the shared foundation: data model, interfaces and platform building blocks. Operations and infrastructure, security reviews and individual business modules sit with closely connected roles.
Your first 90 days
First 30 days
Understand Peak One, the data model and past architecture decisions; name the biggest friction points for new modules.
By day 60
Deliver one clearly scoped platform component with tests and documentation and use it in a module.
By day 90
Establish a reliable process for data model changes and propose the next platform priorities with reasons.
What you bring
- Solid backend development experience.
- Good instinct for data models and interfaces.
- Tests, reviews and documentation as part of doing the job well.
- Ability to explain technical decisions clearly.
What you can learn with us
- Our data model and the business logic of the modules.
- Specific technologies in our environment.
- Our way of working with AI-assisted development.
When this role is less of a fit
You would rather ship individual features quickly without thinking about shared building blocks, or design architecture on paper without writing code yourself.
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 design task for a fictional module: sketch the data model, interface and approach to change, and explain it in conversation. No access to our code, no unpaid product work. People assess clarity, trade-offs and how understandable it is.
Decision
A person decides, never an AI. You always get a response.
Your entry question
„A new module wants to create its own copy of customer data “just for now”. How do you respond, and what alternative do you propose?“
Apply now