Steve Dickens

Why this persona fits the audience

He is CTO at a 18-person AI workflow startup in London. The company’s current web app, auth, billing, and internal admin are assembled from a paid Next.js starter repository plus custom extensions, and he owns the technical roadmap for the product team. He is comfortable shipping code, but keeps an eye on build speed and recurring software spend.

• Age: 41
• Location: London, UK
• Occupation: CTO / Cofounder
• Income: £145k salary + options
• Education: MEng Computer Science, Imperial College London
• Company size: 18 people
• Years in role: 3 years

“The elegance of a system isn't just in its complexity, but in how efficiently it solves a real problem.”

Steve Dickens’ journey into the heart of AI startups began not with a sudden spark, but a steady, methodical progression through the rigorous academic and professional landscape of computer science. Armed with an MEng from Imperial College London, he developed a deep appreciation for robust engineering principles and the intricate beauty of well-designed systems. His early career involved several years at a large, established tech firm, where he honed his skills in backend development and cloud infrastructure, learning the importance of scalability, reliability, and, crucially, cost management in enterprise environments. This experience instilled in him a profound respect for engineering quality and predictable delivery, values he carries forward daily. Seeking greater impact and autonomy, Steve co-founded his current AI workflow startup three years ago. He was instrumental in selecting their foundational technology stack, opting for a paid Next.js starter repository. This decision was driven by a desire to accelerate initial development without sacrificing core architectural integrity, allowing the small team to focus on their unique AI-driven features. He views the starter kit not as a crutch, but as a pragmatic foundation upon which to build, carefully integrating custom extensions to tailor it precisely to their needs. Steve is acutely aware of the financial realities of a startup. His role as CTO involves not just technical leadership but also a keen eye on the bottom line. He meticulously tracks build speeds, server costs, and licensing fees, constantly seeking optimizations that don't compromise the product's integrity or the team's velocity. This fiscal discipline is a core tenet of his leadership, reflecting a belief in sustainable growth. He’s comfortable shipping code himself when necessary, but his primary focus is empowering his team and architecting a platform that can scale efficiently. His technical roadmap is a carefully balanced act between innovation, stability, and economic prudence, ensuring the company can navigate the competitive AI landscape effectively.

Background & daily life

A day in their life

Steve's typical weekday begins around 7:00 AM with a quick scan of overnight alerts and key metrics. After a brief breakfast and a walk with his partner, he's at his desk by 8:30 AM. The morning is often consumed by team stand-ups, code reviews, and architectural discussions, focusing on the current sprint's priorities. Lunch is usually a quick affair at his desk while catching up on industry news. Afternoons are a mix of deep work on technical challenges, planning future sprints, and occasional external calls with potential partners or vendors. He aims to wrap up by 6:30 PM, often followed by an evening of cooking or personal study.

Lifestyle

Steve's life outside of work is structured and focused. He and his partner maintain a tidy Islington flat, often hosting small dinner parties for close friends. Weekends involve a mix of exploring London's galleries, cycling along Regent's Canal, and dedicated time for personal coding projects or reading technical books. He's a proponent of mindful eating and tries to cook healthy meals most nights, though busy periods can lead to takeout. Financially, he's disciplined, saving diligently for future investments and aiming for long-term financial security, viewing his salary and options as a means to that end.

Work life

As CTO of an 18-person AI startup, Steve's days are a constant juggle between strategic planning and hands-on problem-solving. He's responsible for the technical roadmap, ensuring the team's output aligns with business goals while maintaining high engineering standards. His team relies heavily on a paid Next.js starter kit for core functionalities like auth, billing, and admin, which Steve augmented with custom extensions. He's deeply involved in code reviews, architectural discussions, and performance monitoring, always mindful of build times and the company's recurring software expenditure. Coworkers describe him as calm under pressure, but demanding of technical rigor.

Relationships

Steve maintains a close relationship with his partner, who provides a valuable creative counterpoint to his technical world. His core social circle consists of a few university friends and colleagues from previous roles, with whom he discusses technology and life. Within the company, he fosters a collaborative environment but maintains a clear leadership presence, respected for his technical acumen and steady decision-making.

How they decide

Steve approaches decisions methodically. He gathers data, weighs technical merits against business impact and cost, and often prototypes solutions before committing. He values input from his team but ultimately trusts his own analysis and experience. He is not easily swayed by hype and prefers proven, efficient solutions over unverified novelties.

How they sound

Speaks with a clear, measured cadence, typical of educated Londoners. Avoids excessive slang or jargon unless discussing technical specifics with peers. His tone is generally calm and rational, even when discussing challenging issues. He tends to be concise, getting straight to the point without unnecessary embellishment. He might use phrases like 'fundamentally', 'from an architectural standpoint', or 'the critical path'.