Mentoring
Make better technical decisions, without learning only from failure.
Experience doesn’t replace mistakes… but it helps you avoid a lot of them.
I help you step back, structure your thinking, and raise the quality of your decisions.
Discuss your situationAt a glance
- What it is
- One-to-one technical mentoring for developers, leads and CTOs: stepping back from architecture decisions, structuring your reasoning and your technical stance.
- Who it is for
- Developers who want to grow beyond the code, leads and CTOs whose decisions are never challenged.
- Deliverables
- One-to-one sessions, live or asynchronous, on real cases from your own context, with direct and actionable feedback.
- Typical duration
- One to two sessions a month at first, then adjusted to what you are going through.
- How it runs
- Remote, with workshops and scoping sessions on site when the project calls for it.
- Where
- Anywhere in France remotely; on-site work in the Paris area (Île-de-France).
Getting in touch: contact form or WhatsApp, reply within a few working days.
What it’s really like
When you’re a developer, lead, or CTO:
- you learn mostly in production
- decisions are rarely challenged
- you move fast… without always knowing if it’s the right call
And some mistakes are expensive: in time, debt, and credibility.
Value proposition
An external, senior, no-filter perspective.
Not generic coaching.
Not theory disconnected from reality.
Just concrete conversations to:
- challenge your decisions
- clarify your choices
- accelerate your growth
What we work on together
Architecture & design
Find the right trade-offs, avoid over-engineering.
Technical decision-making
Know when to simplify, when to structure.
Lead / CTO posture
Arbitrate, prioritise, say no.
Quality & technical debt
Balance speed and solidity.
Product & technical vision
Align what you build with what actually creates value.
Format
- 1:1 sessions (video or async)
- Concrete cases from your context
- Direct, actionable feedback
Experience
I’ve supported:
- developers levelling up
- leads stepping into new roles
- CTOs structuring their organisation
I’ve also mentored at several hackathons, where the goal is clear: make fast, relevant decisions and ship under constraint.
How I work
- No sugar-coating
- No over-theorising
- Plenty of concrete detail
The goal isn’t to hand you answers, it’s to help you make the right ones.
Typical situations
- You have a technical role with growing responsibility
- You’re unsure about key decisions
- You want to level up (dev lead, lead CTO)
- You feel isolated in your technical choices
Outcome
You gain:
- clarity
- confidence
- better decision quality
FAQ
How often are sessions?
Often once or twice a month to start, then adjusted to your context (new role, critical period, need for perspective).
Is this classic career coaching?
No. The focus is technical and decision-making (architecture, prioritisation, lead posture), not a generic personal development programme.
Do I need a fixed topic each time?
A thread helps, but we can also start from a live situation (deadline, priority conflict, tooling choice) and work from there.
In person or remote?
Mostly remote (video); in-person sessions possible in the Paris area by arrangement.
Does this map to searches like “developer mentoring” or “CTO support”?
Yes: 1:1 format, decisions and architecture at the centre, grounded experience from client work and events like hackathons.