Speak engineering.
Lead with clarity.
I'm an engineer. I run small practice groups where technical people rehearse the meetings that decide things: design reviews, postmortems, client calls. You practise, I tell you honestly how you came across.
- Capped at 6 engineers, so everyone gets real speaking time
- 12-week cohorts, led by an engineer
- Unscripted simulations of situations from your actual job
Based in Oulu, Finland. Training technical teams across Europe.
What a session looks like
You and your group work through one real situation, live, with me guiding it. Here are a few we run.
Design review
Present a technical decision and defend it while people push back.
Incident postmortem
Walk through what went wrong and stay clear when the pressure is on.
Daily standup
Give a short update, flag a risk, and ask for what you need.
Client call
Explain something technical to someone who is not an engineer.
How it flows
- 1
You get the brief
The scenario and any materials arrive before the session, so you can prepare.
- 2
You get a role
One week you lead, the next you push back. Roles change so you practise all of it.
- 3
You talk
Fifty minutes of real conversation. Nothing scripted.
- 4
You get notes
I tell you what worked and what to fix, and I keep a running log of your common mistakes.
Who you learn with
Led by an engineer
I'm Darren. I hold a B.Eng in Computer Engineering and wrote code for a living before I started teaching. Across more than 15,000 hours of sessions I've watched exactly where strong engineers lose the room: the design review, the postmortem, the client call that goes sideways.
We don't study grammar. We run those meetings, unscripted, and I log the mistakes that keep coming back until they stop. I've coached people at LinkedIn, Deloitte, and Mercedes-AMG, and engineers at every level in between.
15,000+
hours taught
4 to 6
people per group
12
weekly sessions
50 min
a session