Most startup engineering problems aren’t new.

I help startup leaders make better technology decisions, improve engineering delivery and turn AI adoption into useful team practices.

Advice from Dan Williams: former founder, CTO and Head of Engineering at a YC-backed startup. Meet Dan.

A few lines are enough. I’ll read your message and reply personally.

From writing the code to leading the organisation.

I have been responsible for code, engineering teams and technology decisions at company level, including as Head of Engineering at a YC-backed company. I can work through the technical detail and still account for the team, the constraints and what the business needs.

Software engineer Founder & CTO Consumer technology CTO YC-backed Head of Engineering Engineering leader working with AI

About Dan and The Startup CTO

How I can help

Bring me the decision or problem in front of you. We’ll look at the evidence, challenge assumptions and work out what needs attention first.

Focused reviews

An independent examination of a specific problem. I’ll explain what I found, the evidence behind it and what I recommend doing next. Reviews can cover AI adoption, team health, delivery, organisation, technology strategy or hiring. Bring the evidence you already have. You do not need to diagnose the problem first.

Advisory

Regular access when a leadership team or investor wants an experienced second opinion on an important decision or difficult problem.

Call me before you make the expensive decision.

Follow-through

For the right, clearly bounded problem, I can stay involved to help leaders and teams put the recommendation into practice.

Is AI making this engineering team measurably better?

The AI Engineering Review looks at how AI is being used across the team, where it is improving the work and where it is adding risk or inconsistency. I identify which workflows need to change and set expectations for using AI safely. The 90-day programme helps the team adopt those practices. We agree the outcomes that should improve and track those alongside adoption.

  1. Map current useFind where adoption is uneven and which engineering workflows are worth changing.
  2. Set the working practicesDefine tools, data handling, review expectations, enablement and support for the team.
  3. Drive adoptionPrioritise changes, establish owners, support the team and measure whether outcomes improve.

How I think about engineering teams

Teams should understand why the work matters, own the outcome, maintain high standards and avoid unnecessary process. These are strong defaults, applied with judgement.

  1. Give engineers the problem, not just the ticket.
  2. Making work smaller is the easiest lever for speed.
  3. Clear boundaries create speed.
Read all eight engineering principles

You don’t need a perfect brief.

If one of these problems sounds familiar, a few honest lines are enough. Tell me what changed, what you can see and which decision or outcome is at stake.