Why this persona fits the audience
Co-founds a 4-person B2B SaaS team in London and still writes most of the code herself, including prototypes, bug fixes, test runs, and deployment steps. She already uses GitHub Copilot and shell scripts, and keeps product decisions close to the terminal and issue tracker.
- Age: 41
- Location: London, UK
- Occupation: CTO and Co-founder
- Income: £128k salary + equity
- Education: MSc in Software Engineering
- Company size: 4 people (including her)
- Years in role: 3 years as CTO/Co-founder; 15 years total in engineering
“You can't build a house on a foundation you're too afraid to inspect.”
Maxine Carroll-Rohan is a quintessential modern technologist who bridges the gap between the gritty reality of early-stage entrepreneurship and the theoretical elegance of software engineering. Born in Manchester and educated at Imperial College London with an MSc in Software Engineering, she spent the first decade of her career architecting enterprise systems for fintech giants, where she learned the cost of technical debt firsthand. In 2023, driven by a desire for autonomy and a frustration with bureaucratic inertia, she co-founded a four-person B2B SaaS startup in London. Unlike many founders who retreat to strategy rooms, Maxine remains the primary coder, personally handling everything from prototype validation to production deployments. She operates with a fierce sense of accountability, believing that a leader must understand the code they ship. Her workspace reflects this pragmatism: a chaotic mix of hardware, open-source repositories, and handwritten notes on whiteboards. She has cultivated a unique workflow that leverages GitHub Copilot not as a crutch, but as a force multiplier, allowing her to write cleaner, faster code while maintaining strict oversight. Despite her success and a £128k salary plus significant equity, she remains frugal and grounded, viewing money merely as fuel for the mission rather than a status symbol. Her recent focus has shifted toward implementing rigorous data governance and automating testing protocols, recognizing that the next phase of growth requires stability as much as speed. Maxine navigates the startup landscape with a calm demeanor, her resilience forged through years of debugging complex systems and leading small teams through high-pressure pivots. She is a guardian of privacy and technical integrity, often refusing to compromise on security standards even when pressed by potential clients. To her, the terminal is not just a tool but a sanctuary where logic prevails over chaos.
Background & daily life
A day in their life
Maxine wakes at 5:30 AM, immediately cycling ten miles through Hackney Marshes to clear her head. By 7:15 AM, she's brewing coffee and reviewing overnight logs from the US servers, spotting a minor latency spike in the payment gateway. At 8:30 AM, she joins the team via Zoom for a 15-minute sync, quickly delegating a frontend fix to the junior dev before diving into her own terminal. The morning is spent refactoring the authentication module, using shell scripts to automate repetitive linting tasks. Lunch is a quick sandwich eaten at her desk while reading a Substack thread on distributed consensus. Afternoon meetings are sparse, reserved for investor updates and hiring interviews. The afternoon block is sacred for deep coding; she deploys a hotfix to staging, verifies it with her custom test runner, and pushes to production. Evening ends around 6:30 PM, followed by guitar practice or film developing. She goes to bed by 10:30 PM, having mentally logged off completely.
Lifestyle
Maxine lives in a high-ceilinged, brick-walled flat in Shoreditch that smells faintly of old coffee and sawdust. Her mornings begin with a 20-minute cycle to work through quiet streets before the city wakes, a ritual that grounds her before the chaos of the startup day. She maintains a rigorous fitness routine, alternating between road cycling and weight training three times a week, treating physical endurance like mental stamina. Financially, she is disciplined; despite her high income, she avoids luxury consumption, preferring to reinvest surplus cash into server costs or emergency buffers. Evenings are reserved for analog hobbies—developing film in her bathroom sink or strumming an acoustic guitar while listening to British folk records. Her social circle is tight-knit, consisting mostly of other founders and engineers who value privacy and direct conversation over networking events.
Work life
Her office is a standing desk cluttered with mechanical switches and two 4K monitors displaying a terminal window alongside a live Jira board. As the de facto lead engineer, she spends roughly 70% of her time writing code, debugging race conditions, and managing CI/CD pipelines, reserving the rest for architectural planning and one-on-ones. The team of four relies entirely on her technical judgment; there is no middle management layer. She operates with a local-first philosophy, keeping all sensitive data and development environments on-premise or within private cloud buckets. The pressure is constant but manageable; she thrives on the immediacy of shipping features directly to production. Her days are punctuated by rapid-fire Slack messages and spontaneous stand-ups, yet she fiercely protects her 'deep work' blocks where she types without interruption, often wearing noise-canceling headphones to signal unavailability.
Relationships
Maxine shares her life with Elias, a structural engineer who appreciates her precision but often worries about her work hours. They have no children yet, which gives them flexibility but also a shared silence about future family planning. Her closest confidants are two former colleagues from her pre-startup days who now run their own agencies; they meet monthly for 'war stories' over tea, offering a safe space to vent without corporate jargon. She values her co-founder deeply but maintains professional boundaries, ensuring their relationship remains focused on business survival rather than personal entanglement.
How they decide
Maxine employs a 'measure twice, cut once' approach, heavily reliant on data and empirical evidence rather than intuition alone. She rarely makes decisions in isolation; instead, she prototypes solutions quickly in a sandbox environment, gathers metrics, and then commits. She is skeptical of hype cycles and prefers tools that offer transparency and control. When evaluating new technologies, she prioritizes longevity and community support over flashy features. Her decision-making process is methodical: she identifies the core constraint, simulates the outcome, and only proceeds if the risk is quantifiable and acceptable.
How they sound
Her speech is clipped, precise, and devoid of filler words. She speaks with a distinct Received Pronunciation accent softened by London colloquialisms, often dropping the 'g' in gerunds casually. She avoids corporate buzzwords like 'synergy' or 'circle back,' preferring terms like 'shipping,' 'blocking,' or 'technical debt.' When explaining complex concepts, she uses metaphors drawn from cycling mechanics or folk song structures. She tends to pause briefly before answering to ensure accuracy, rarely raising her voice even when stressed. Her tone is generally calm and authoritative, projecting confidence without arrogance.
Personality traits
- hyper-observant
- decisive under pressure
- technically meticulous
- pragmatically idealistic
- quietly authoritative
- resourceful
- boundary-conscious
- system-oriented
- direct communicator
- resilient
Goals
- Achieve sustainable profitability within 18 months to secure Series A independence
- Architect a fully automated testing suite that reduces regression bugs by 90%
- Build a culture of radical transparency where every team member understands the codebase
- Maintain personal coding fluency while transitioning to more strategic leadership
- Establish a robust data governance framework that exceeds GDPR requirements
- Develop a mentorship pipeline for junior engineers joining the remote team
Problems & frictions
- Time fragmentation caused by context switching between coding and stakeholder management
- Difficulty scaling the current monolithic architecture as user load spikes unexpectedly
- Balancing the need for rapid iteration against the desire for long-term technical debt reduction
- Managing the cognitive load of being the sole gatekeeper for critical security patches
- Finding reliable documentation for legacy libraries that haven't been updated in years
- Preventing burnout during late-night deployment windows when production issues arise
Values
- shipping
- accountability
- team leverage
- privacy
- technical integrity
- frugality
Interests
- startup operations
- dev tooling
- folk music
- cycling
- mechanical keyboards
- analog photography
Media habits
- Hacker News daily digest
- Local London tech meetups
- NPR's 'All Things Considered' during commute
- Substack newsletters on distributed systems
- Spotify folk playlists for deep work
- GitHub trending repositories