Why this role exists
Entrepreneurs rely on Peak One working day to day. The more modules run on the shared data model, the more important reproducible environments, automated delivery, good monitoring and practised recovery become. This role builds that foundation and keeps developing it.
Your outcomes
- Reproducible environments, described as code and versioned.
- Automated, traceable delivery with safe rollbacks.
- Monitoring and alerting that surface real problems early instead of noise.
- Tested backups and documented procedures for incidents.
Your day and scope
Maintaining infrastructure as code, improving delivery pipelines, reviewing monitoring, keeping an eye on costs and working closely with platform and security engineering. After incidents you write honest, blameless reviews with concrete actions.
Boundaries: You own environments, delivery, operations and recovery. Business features and security strategy sit with other roles you work closely with.
Your first 90 days
First 30 days
Understand existing environments, delivery and monitoring; document and prioritise the biggest operational risks.
By day 60
Close the most important gap, for example in backups, alerting or reproducible environments, and run a recovery test.
By day 90
Establish a reliable rhythm for delivery, operational review and incident follow-ups.
What you bring
- Hands-on experience with infrastructure as code and automated delivery.
- Confident with Linux, networking and containers.
- Calm, structured approach to incidents.
- Careful documentation of procedures.
What you can learn with us
- Our environment and its specifics.
- Specific tools you have not run yet.
When this role is less of a fit
You prefer running systems mostly by hand and by gut feeling, or responsibility for running production is not something you want in your role.
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 environment: narrow down an incident from synthetic logs and write a short review with actions. No access to real systems, no unpaid work. People assess approach, prioritisation and clarity.
Decision
A person decides, never an AI. You always get a response.
Your entry question
„How would you know that a backup will really work when it matters – and how would you check that regularly?“
Apply now