You are hired as CTO of a 300-person company with slow delivery and frequent outages. What do you do in your first 100 days?
Short answer
Listen across the business and engineering, stabilize the most damaging reliability issues, measure the delivery system, build trust with quick wins, define a one-page technology strategy linked to business goals, adjust organization and leadership where necessary, and set up a transparent operating rhythm with clear metrics.
Detailed answer
| Phase | Actions |
|---|---|
| Days 1–30: listen and stabilize | 1:1s with executives, customers, engineers; incident review of last 6 months; immediate fixes for top outage causes (change management, on-call, rollback); baseline DORA metrics |
| Days 31–60: diagnose | Architecture and debt hotspots, team structure and dependencies, talent assessment, vendor and cost review, security posture |
| Days 61–100: commit | One-page strategy with 3–4 guiding policies, 12-month roadmap, org changes, metrics scorecard, operating cadence (weekly tech leadership, monthly business review) |
Early wins: SLOs and incident process for top journeys; deployment pipeline improvements; visible fix of a long-standing customer pain.
What the interviewer expects
Balance between listening and acting, reliability first, business alignment, people decisions.
Common mistakes to avoid
Announcing a rewrite or reorganization in week two; ignoring existing leaders' knowledge.