GeeCON 2023: Sebastian Gebski - Unicorn's baby steps: what should you know as a 1st-time startup CTO

### Overview In this GeeCON 2023 presentation, Sebastian Gebski—Principal Architect at AWS and former CTO/VP of Engineering—breaks down the essential realities, mental models, and challenges faced by first-time startup CTOs and aspiring technical leaders. The talk addresses how technical leadership differs fundamentally from hands-on software development, particularly within high-ambiguity, growth-oriented startup environments where organizations must operate rapidly with low inertia. Gebski traces the technical leadership lifecycle across four distinct stages of growth, highlights practical leadership trade-offs, and addresses controversial realities regarding pressure, technical debt, and company culture.

### Key Topics - **CTO Archetypes & Roles:** Gebski distinguishes three common CTO profiles: the Architect (owning the core technical vision, algorithms, or framework), the Head of Delivery (managing systems, processes, and engineering execution), and the Advocate (serving as a technical spokesperson and liaison, similar to Werner Vogels at Amazon). He also differentiates the "leader" hat (influencing people) from the "manager" hat (managing systems), noting that while a CTO does not need to excel at every hat personally, those responsibilities must be actively delegated. - **The Four Startup Stages:** 1. *Envisioning:* Focusing on understanding user problems, unique value propositions, and validating assumptions with data (both hard data and anecdotal fieldwork) before writing code. 2. *Product-Market Fit:* Determining what to prove with limited runway and deciding what to build first. Gebski illustrates this using Midjourney, which focused purely on generative image quality and launched as a Discord bot rather than building web or mobile apps. 3. *Operating with Real Users:* Addressing explicit and implicit customer promises, uptime implications, and business-metric monitoring. Gebski recounts an outage in a beauty/wellness SaaS platform that revealed salons could not operate without seeing scheduled appointments, prompting the implementation of graceful degradation (minimal read-only access). 4. *Organizational Scaling:* Transitioning from single codebases to parallel, multi-site engineering teams, managing component ownership, and formalizing architecture around non-functional requirements ("-ilities"). - **Decision-Making Frameworks:** Adopting formal mechanisms such as Amazon's classification of one-way door (irreversible, high-risk, requiring deep research and "disagree and commit") versus two-way door decisions (easily reversible) to avoid CTO bottlenecks. - **Agility and Development Friction ("Boiling Frogs"):** Maintaining development velocity by recognizing gradual slowdowns like sluggish builds, untracked breaking builds, manual approval gates, and over-engineering. - **The Social Contract, Pressure, and Skin in the Game:** Managing startups requires sustained push and pressure from leadership. Gebski advocates establishing an upfront, explicit "social contract" regarding working hours, compensation, and risk tolerance, coupled with "skin in the game" (such as equity sharing) so contributors share in both success and loss.

### Technical Details & Common Pitfalls Gebski challenges standard engineering dogmas by emphasizing that technical debt is not bad engineering; rather, it is a strategic tool traded consciously for speed and runway. He highlights architectures "designed for rewrite," where services bounded by stable business contracts allow underlying components to expire and be replaced easily. Additionally, he warns against critical mistakes: - Pursuing engineering perfectionism and clean code over business pragmatism. - The fallacy of "technical success" where developers build the requested software successfully but the product ultimately fails commercially. - Misjudging the build vs. buy dilemma by underestimating ongoing maintenance costs when choosing to custom-build infrastructure instead of leveraging existing cloud services.

### Takeaways A startup CTO's core responsibility is driving business outcomes rather than pursuing technical perfection. To succeed, technical leaders must establish clear decision-making frameworks, measure operational and business metrics early, communicate expectations transparently via social contracts, and prioritize focus over trying to build everything.