01
Technical leadership
Architecture and system design, platform evolution, large-scale refactoring, technical strategy, and engineering effectiveness.
Senior technical builder
Hands-on technical leadership for teams solving hard engineering problems.
I work as a Staff Engineer, Principal Engineer, or technical lead for small, high-performing software teams. AI is a force multiplier, not the destination.
The goal is not to manage larger engineering organizations. The goal is to build, mentor, architect, and lead through technical expertise.
Target work
Technical leadership anchored in real software building.
02
Building software
Product development, platform engineering, AI-enabled software systems, agentic engineering workflows, and internal tooling.
03
Mentoring teams
Coaching engineers and tech leads, raising standards, improving decision-making, and building engineering capability through example.
Value proposition
Builder first. Technical leader second. Executive experience in context.
I combine deep technical curiosity, 30+ years of software engineering experience, architectural thinking, and scaling experience without needing hierarchy to create influence.
Build
Design and ship better software while maintaining quality under real delivery pressure.
Decide
Help teams make stronger technical decisions and simplify complex systems.
Enable
Increase delivery effectiveness through mentoring, standards, and practical workflow design.
Apply AI
Use agentic engineering pragmatically where it improves throughput, feedback loops, and code quality.
Why this profile fits
Few people combine deep technical work with senior engineering leadership.
Differentiation
- Former Head of Engineering and VP Engineering
- Hands-on technical mindset with strong systems thinking
- Proven scaling experience from code to boardroom
- Early practitioner of agentic engineering workflows
Preferred environment
- Small teams of 5 to 20 engineers
- Strong engineering culture and high autonomy
- Builders over managers
- Fast feedback loops and meaningful software
Ideal roles
Primary roles are senior individual-contributor and player-coach positions.
Primary
Secondary
Only when technical work remains central.
Best fit
Software companies that need experienced technical leadership inside the work.
Typical situations
- Scaling from startup to scale-up
- Platform modernization and technical debt reduction
- AI-native engineering adoption
- Major architectural transitions
Technical influence matters most when it stays close to code, product, and the teams doing the work.
Trajectory
The path moves from executive context toward deeper technical involvement.
Current executive role with increasing technical involvement.
Player-coach role combining architecture, mentoring, and selective management.
Staff or Principal Engineer style work with deep software involvement and minimal people management.