Services

What I'd bring

One engagement, not a menu. I take on the engineering-management mandate — the system your engineers work in — and hold the cloud architecture, the hardest code and the coaching inside it at the same time. None of that scales by working harder, so each role gets turned into a system that keeps running when I'm not in the room.

The mandate

Engineering management, as the single point of accountability for people, process and team health. In practice: hiring and onboarding, 1:1s, a training system with a budget attached, code review with an SLA, ceremonies that produce decisions instead of updates, metrics that describe the system instead of ranking people, and decisions written down where the next person can find them.

It works as a fractional role because the output isn't my own throughput. I don't produce sprint points and I don't absorb the urgent incidents. What stays behind is systems, processes, more capable people and better decisions — the parts that keep working on the days I'm not there, which is why the value compounds.

What the role owns, what it doesn't, and who decides

Depth inside the mandate

Four more roles run inside the mandate at the same time — not as extra engagements, and not as a menu to pick from.

Cloud Architect

End-to-end ownership of the stack, the cloud infrastructure, the security model and multi-tenancy. On AWS since 2019 — CDK, DynamoDB, EventBridge, Step Functions, ECS — with security designed in rather than added later.

Tech Lead

Production code on the parts of the system nobody else has the context to carry: auth layers, deploy infrastructure, migrations that cross codebases. Architecture gets written, not supervised.

Leadership Coach

Biweekly 1:1s run as coaching rather than status reports, growth plans people can actually see, and feedback delivered while it can still change something.

Tech Advisor

A validation gate between enthusiasm and adoption: independent study, a proof of concept on a real use case, a Tech Radar placement backed by a decision record, then training for the team. The radar format is ThoughtWorks', the decision records Nygard's.

What transfers to your team

The templates are the easy part. What transfers is knowing which system to build first in a company that has none of them.

Transfers directly: The onboarding milestone ladder, the 1:1 procedure, the training catalogue and its budget mechanics, the pull-request process and its review escalation rules, the Blocker / Suggestion / Nitpick audit convention, incident response, decision records and the Tech Radar, and role documentation that states what each role does not own.
Needs adapting: Team topology, ceremony cadence, OKR scope, which team-health metrics to start with, and every governance threshold. The existence of a threshold transfers; the number doesn't.
Doesn't transfer: The tooling configuration. Anyone competent can rebuild it once the states and the ownership rules are clear — and those rules are the actual deliverable.

The order matters more than any single system: process before ceremony, ceremony before metrics, metrics before targets. Installing them in any other order is how transformation programmes fail.

Technical depth

Cloud: AWS since 2019: AWS CDK (IaC), DynamoDB key design and access patterns, EventBridge, Step Functions, Lambda, S3, ECS Fargate, OIDC federation. Multi-region across the oceans. Also other cloud providers with Terraform.
Languages & frameworks: TypeScript and Node.js first; React, NestJS, MedusaJS, Drizzle ORM, PostgreSQL, Docker.
Architecture: Multi-tenant SaaS, event-driven systems, bounded contexts and data ownership, row-level security, RBAC, C4 models kept in the repository, property-based testing.
Compliance & security: NIS2 treated as a day-zero architectural constraint rather than a retrofit — region choice, encryption, audit logging, least privilege. Dependency scanning and quality gates in CI.

The fastest way to find out whether this fits is a 30-minute call about your team — where the systems are missing and what's getting in the way. No pitch.

Book a free intro call