Help for engineering teams that want to ship with less drama.
I work with teams that need stronger API design, better Laravel architecture, and more intentional developer growth.
If your team is scaling quickly, standardising how it builds, or trying to upskill senior engineers without adding more noise, I can help with focused workshops, curriculum design, and coaching.
Choose the right engagement
Each engagement is shaped around the team and the problem, but these are the three ways most companies work with me.
Team Workshops
Hands-on sessions for engineering teams that want better API decisions, clearer architectural patterns, and stronger delivery habits.
Best for
Platform teams, product engineering groups, and senior developers tackling API design or Laravel architecture.
Format
Remote or on-site, typically delivered as a half-day, full-day, or two-day workshop.
Typical timeline
Usually scoped and scheduled within 2-4 weeks.
What to expect
Most teams book a focused one-off engagement with follow-up notes and recommended next steps.
What teams walk away with
- Custom material shaped around your stack, standards, and current pain points.
- Examples and exercises grounded in production trade-offs, not generic training slides.
- A clear set of patterns the team can keep using after the workshop ends.
Curriculum Design
Internal learning systems for organisations that want onboarding, leveling, and technical education to scale beyond tribal knowledge.
Best for
Engineering leaders building learning paths, internal docs, or developer enablement programs.
Format
A collaborative advisory engagement covering content strategy, structure, and rollout guidance.
Typical timeline
Often delivered over a focused 2-6 week sprint depending on scope.
What to expect
Best when you already know learning is a bottleneck and want a system your team will actually use.
What teams walk away with
- A clearer view of the skills gaps slowing the team down.
- Structured learning paths and documentation priorities tied to real roles.
- A repeatable framework for onboarding and continuous development.
Engineering Coaching
Direct support for senior engineers and leads who need a thoughtful sounding board on architecture, technical communication, and decision-making.
Best for
Senior ICs, new leads, and engineering managers working through complex systems or team growth.
Format
Weekly 1:1 or small-group sessions with async follow-up by email.
Typical timeline
Usually run as a short sprint or monthly coaching block.
What to expect
Ideal when someone on the team needs momentum, sharper thinking, and external perspective.
What teams walk away with
- Better framing of architectural trade-offs and technical direction.
- Feedback on code, communication, and leadership habits.
- Support that helps senior people grow without feeling isolated.
What working together looks like
The process is simple on purpose. I want teams spending their energy on better decisions, not heavier consulting theatre.
Step 1
Discovery
We start with the team, the current bottlenecks, and the change you want to see after the engagement.
Step 2
Tailored plan
I shape the material, format, and examples around your stack, team maturity, and delivery context.
Step 3
Delivery
Workshops and coaching are practical, conversational, and designed to create useful decisions fast.
Step 4
Follow-through
You leave with concrete next steps, notes, and patterns the team can keep using after I leave.
What people say after working with me
Named feedback matters more than vague praise, so here are a few of the people kind enough to say so publicly.
“Steve is one of the most thorough and thoughtful educators I've seen. He puts in a ton of effort and it clearly shows.”
Aaron Francis
Founder, Try Hard Studios
“Steve is the teacher you wish you had in school. He’s informative, entertaining, and passionate about what he does. I’m always excited to see more of Steve’s content!”
Alex Six
Senior Software Engineer, Zillow
“To me, there's one word that comes to mind: 'passion'. There are only a handful of people with the same passion for programming as Steve.”
Brent Roose
Developer Advocate, JetBrains
Who I work best with
The best engagements happen when the team already knows there is a meaningful problem to solve and wants help tackling it thoughtfully.
- Engineering teams standardising API patterns before growth makes the inconsistencies expensive.
- Laravel teams that want cleaner architecture without disappearing into theory.
- Leads building onboarding and internal learning systems that scale.
- Senior developers who need a trusted external perspective on hard technical calls.
Start with a conversation
If you are exploring a workshop, coaching, or a curriculum project, send me a note with a little context on the team, the challenge, and what good looks like.
Include the team size, the problem you want to solve, and whether you are thinking workshop, coaching, or enablement.
I will reply with whether I am the right fit and what the next step should look like.