Let's build the digital products others don't dare to.
Here, you don't push tickets: you design and build systems that real operations depend on.
- Critical systems
- Built in-house
- Design × Tech × Domain
Work that actually exists, in the field.
You don't just build an interface. You build a tool that will be used in the field — where reliability genuinely matters.
Industry
Factories and production environments, where near-enough is expensive.
Large accounts
Demanding organizations, with real stakes and real constraints.
Ambitious startups
From MVP to scaling, with genuine product ownership.
Critical systems
Solutions that must be operable, observable and built to last.
You don't get a task. You understand a problem.
Design and development move together, close to the business, in short cycles — and everyone sees the real impact of their work.
- 01Understand
- 02Design
- 03Build
- 04Test
- 05Learn
- 06Improve
Design + Development, one team
Our designers work alongside developers. What's designed is what gets built.
Iterative and agile
We move in short cycles, with regular demos and early adjustments.
Close to the client
We talk directly to the business. No broken telephone between the need and the code.
Knowledge sharing
Reviews, pairing and team rituals: we learn from each other, continuously.
We'd rather have a tight team of excellent people than an army of interchangeable profiles.
Our culture comes down to two words: high standards and ownership. Everything else follows.
Technical excellence
We aim for work done well, not just shipped. Code review, tests, restraint: quality is a habit, not an option.
Product mindset
We don't code specs, we solve problems. Understanding the 'why' before the 'how' is part of everyone's job.
Collaboration
Design, dev and business move together. The best ideas come from the whiteboard, not an isolated ticket.
Autonomy
We trust people. Everyone owns their topics, makes decisions and takes responsibility for them.
Innovation
We test, prototype and challenge the status quo. Technical curiosity is encouraged, not merely tolerated.
Continuous learning
We grow with every project. Knowledge sharing, upskilling and the right to make mistakes are part of daily life.
Why we need you, specifically.
Each profile solves a real problem in how we build. Here's which one.
Developers
WhyBecause we build our own products, and it takes people who can turn complex problems into robust systems.
Product Designers
WhyBecause understanding a complex domain isn't enough: you have to turn it into a clear, genuinely usable experience.
Architects
WhyBecause our products must be able to evolve without becoming fragile.
DevOps
WhyBecause a product only has value if it can be run, monitored and maintained properly.
Project managers
WhyBecause a complex project needs someone who can hold the line between client, business, design and technology.
Domain experts
WhyBecause technology alone doesn't understand the field.
We're not looking for
order-takers.
We're looking for
people who can understand, question and build.
What actually matters
- Curiosity
- Autonomy
- Ability to understand
- Attention to detail
- Critical thinking
- Eagerness to learn
- Collaboration
- Ownership
- A taste for complex problems
A short, clear and human process.
Five steps, one philosophy: understand who you are and how you think — not trip you up.
You tell us about you
Not just your CV. Your experience, your ambitions, the way you think.
We talk shop
No traps, no cramming. We look for your real level and how you solve a problem.
You meet the team
Hiring doesn't work one way: you need to know who you'll be working with.
We decide
A clear answer, a fast decision. No endless process.
We onboard you
The goal isn't to get you to sign, but to make you autonomous, fast.
A team, not a collection of CVs.
Product, engineering and field work in the same room — not in silos.
Framing workshops
We align business stakes, constraints and priorities before opening the editor.
Technical discussions
Architecture, security, debt: choices are debated openly, as a team.
Design + development
Design and development iterate side by side, close to real usage.
Back to the field
We go back to users: the tool proves itself where it is used.
Is this the right environment for you?
Better to be clear on both sides.
What you'll find here
- Real ownership
- Complex projects
- Closeness to the business
- Autonomy
- High standards
- Continuous learning
What you won't find
- Micro-management
- Purely executional work
- Pointless process
- Heavy hierarchy
- Projects without impact
Think you can build with us?
Let's talk.
No open positions published right now — but we continuously meet profiles who share our standards.