Why this role exists
Peak One is Peak Atlas’s central platform. Product development has so far been founder-led and heavily AI-supported. Turning that into a dependable product needs people who understand user problems first-hand, build cleanly and check after release whether a feature actually helps.
Your outcomes
- Shipped features that solve a clearly described user problem.
- Small, reviewable changes instead of large, risky releases.
- Traceable decisions on scope, trade-offs and non-goals.
- Observed usage that feeds into the next iteration.
Your day and scope
Clarifying problems with Customer Success and Sales, sketching solutions, building frontend and backend, writing tests, reviewing code, shipping and reviewing usage. AI tools are part of the job – responsibility for the code you ship stays with you.
Boundaries: You own features from problem definition to post-release review. Overall product direction and platform architecture are shaped together with other roles.
Your first 90 days
First 30 days
Understand Peak One, the shared data model and the key user journeys; ship first small changes.
By day 60
Own one scoped feature from problem statement to release.
By day 90
Have reviewed that feature’s usage, delivered one reasoned improvement and reliably taken over your area.
What you bring
- Hands-on experience building and running web applications.
- Interest in user problems, not only technology.
- A clean, reviewable way of working with tests and reviews.
- Clear communication with non-engineers.
What you can learn with us
- Our specific codebase and tools.
- Our target customers’ day-to-day reality in detail.
When this role is less of a fit
You only want to work through fully specified tickets without talking to users or colleagues from Sales and Customer Success.
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: build a small feature for a fictional application and briefly explain what you deliberately left out. No work on real Peak Atlas code. People assess problem understanding, code quality and reasoning.
Decision
A person decides, never an AI. You always get a response.
Your entry question
„Two weeks after release, how would you tell whether a new feature in Peak One actually solved a problem?“
Apply now