Senior developers and technical leadership for your own team
Developers & technical leadership
You are not looking for an extra pair of hands, but for someone who understands why your system does what it does. That is what you hire at Chief: senior developers and technical leadership who work in your team. A Chief developer stays part of Chief, with colleagues to fall back on, so knowledge of your system does not end up in one person's head.
Why that matters
Hire software developers with a team behind them
The team behind your developer
A developer who joins your team stays part of Chief. They keep taking part in our reviews, can fall back on colleagues, and record what we find in your system in your repository. If someone leaves Chief, a colleague who already knows the context takes over.
Three ways we join
- A senior developer in your team, in your codebase and way of working, who says what they see.
- Technical direction and architecture: making choices, writing them down and being able to explain them later.
- Coaching, including working with AI, with the same review for what a model suggests as for what a person types.
A tech lead when you have no CTO
We read supplier proposals, test your roadmap and take part in hiring developers. See how that works out in our cases.
What working together looks like
An introduction
You tell us where it is stuck: a team short on seniority, a system nobody dares to touch, or a roadmap with no technical pushback. We ask questions and tell you at the end whether we think we can help. At our office in Utrecht, at yours, or online.
Technical exploration
We look through your code, your backlog and the way you release, and talk to the people who work in it every day. You get short advice in writing: which profile you need, where we would start and what we would deliberately leave alone.
You meet the person, not a CV
No profile in your inbox, but a conversation with the developer or tech lead who will do the work. You decide whether it clicks. Senior people are scarce, so we are honest about whether it fits.
Working in your team, with Chief behind it
Our developer works in your rhythm and keeps taking part in our reviews. We check together whether it gives you what you were after. Everything we learn about your system is written down in your repository.
What working together looks like
You do not need to know up front whether you want a developer, a tech lead or both. That comes out by itself in the first two steps.
One extra developer, all of Chief behind them.
Cases built with this expertise
How Chief provides technical leadership for De Compliance Afdeling's new Compliance Tool, with extra development capacity and one central platform.
Rhythm helps healthcare organisations plan capacity better. Chief works on the design of its new software suite and an AI-supported development process.
Chief led the renewal of Kieskeurig.nl for Reshift: price and product updates are now processed within 10 minutes instead of hours or days.
Frequently asked questions
Is this secondment?
No. The developer working with you stays part of Chief: they take part in our reviews, they have colleagues to fall back on, and they work from our office in Utrecht or on your site, depending on what the work needs. You notice the difference the moment something goes wrong or someone drops out: you do not have one person, you have the team behind them.
Who owns the code you write?
You do, from the first commit. We work in your repository, with your pipelines and your own cloud account on Azure or AWS. If we reuse a component we already had, we say so up front and agree how you can carry on with it without us.
What happens to the software we already have?
It usually stays exactly where it is. We take over existing systems and build on them. We start by understanding what is there, not by rewriting it.
How do you handle handover when we stop?
Handover starts on day one. What we learn goes into your repository: architecture choices with the reasoning next to them, how to run a release, where the traps are. At the end we walk your developers through it. If you do not need us after that, it went well.
What do you need from us to get started?
Access to your code and your environments, and someone who is allowed to make decisions about the product and is reachable when a choice comes up. Beyond that it helps if you say out loud what is not going well, including the awkward part. We will find out anyway, only later and with more damage done.
How quickly can you start?
It depends on who is free. We will not send someone whose skills are nearly but not quite what you need. What we can usually begin straight away is the technical exploration from step 2, so you are not standing still until someone starts.
Want to think it through with us?
Tell us briefly where it is stuck and what is missing: an extra developer, technical direction, or both. We will come back with the profile that fits and when that person could start. If it is not a fit with us, we will say that too.
Monday to Friday
8am to 5pm
Send us a message
What else can Chief help you with?
Sometimes an extra developer is not the answer and something has to be built, taken over or replaced. We do that with the same team: custom software and AI implementation.
AI implementation
Implementing AI in your processes and existing software, on data you can trust. See how we start with one process and what you get first.
Custom software
Custom software development from Utrecht: platforms, apps, integrations, hardware and firmware, from business case to support. See how we work.
