The engineering leader just left.
When the head of engineering exits abruptly, the team needs steady leadership while the search runs. Stabilize delivery, retain key talent, and set the next permanent leader up to succeed.
There comes a point when your engineering organization needs real leadership — but not yet a permanent hire. I step in, on your timeline, to stabilize operations, restore rigor and operational excellence, and leave you with scalable systems that run without me.
There are four patterns I see over and over. If one of these sounds like your company, we should talk.
When the head of engineering exits abruptly, the team needs steady leadership while the search runs. Stabilize delivery, retain key talent, and set the next permanent leader up to succeed.
Velocity without predictability is a debt that compounds. The fix is delivery discipline — installed while the team continues to ship — so growth doesn't outrun reliability.
When an existing executive isn't operating at the level the role demands, the organization needs a senior partner — to shadow, coach, and raise the bar, or to manage a clean transition if that's where it lands.
Early-stage organizations rarely need a full-time engineering executive on day one — but they do need executive-grade thinking. A fractional engagement bridges the gap until a permanent hire becomes a clear commercial decision.
A consistent, systematic approach to success, in predictable, collaborative phases.
Meet the team, read the code, sit in the rooms, understand existing processes, identify leaders and influencers. Diagnose before prescribing.
Document the state, name what's working, name what's not, propose a sequence. Agreed-to plan before any action.
Deliver against the plan. Weekly rhythm with the CEO. Monthly business-level readout. No surprises.
Three pillars hold up the leadership work, regardless of the engagement: challenge, trust, and ownership.
Vision without action changes nothing. I translate it into realistic workloads and challenge key people to drive them. Leaders are built through that translation — vision → strategy → execution — and they grow when the work itself stretches them.
Trust is the substrate. I build mutual trust with key people early, so that when I hand them a deliverable, the assignment carries the implicit message: I believe you can deliver, on time and to specification. Without that, no challenge lands.
Real leadership owns the outcome — success or failure. I expect leaders to deliver, and I expect them to own what happens either way. Success is a cause for celebration. Failure is a trigger for learning, and learning compounds. Either way, the leader carries the weight.
The last three years at SugarAI (formerly SugarCRM): 115 engineers across five countries, shipping the CRM products behind a $130M+ ARR business. The short version of what the work looked like, in numbers:
Sprint predictability moved from 54.5% to 89.8% against an 80% goal — not through heroics, but through discipline. Delivery velocity held steady through a 20% workforce reduction, because the team knew where they stood and what they were being asked to do.
First new product launch in a decade, delivered in six months. Structured test strategy pulled defects down 25%. Rebuilt onboarding cut time-to-initial-contribution by 20%. Vendor reassessment and renegotiation reduced organizational expenses by up to 65% in key services.
And the operating fundamentals held: 99.9%+ uptime across customer-facing SaaS, with GDPR and SOC 2 treated as the default, not a retrofit.
Industries and contexts where this engagement model has delivered measurable results.
Tell me about your engineering organization — the challenges you're facing, the team you have today, and what success looks like to you. I read every message personally.