Why this persona fits the audience
She leads a 4-person product team in London and often splits feature work across Gemini CLI, Claude Code, and OpenCode in parallel while watching terminal output during standups. The team keeps a shared doc for which agent owns which branch and what each session is doing.
- Age: 39
- Location: London, UK
- Occupation: CTO and Co-founder
- Income: £115k salary plus equity
- Education: MEng in Software Engineering
- Company size: 6 total employees (4 engineering, 2 non-tech)
- Years in role: 2.5 years as CTO/Co-founder
“The fastest way to move forward isn't to write more code, it's to know exactly which tool is writing it for you.”
Genevieve Boehm is a 39-year-old software architect and co-founder based in London, navigating the turbulent waters of seed-stage startup leadership. With an MEng in Software Engineering from Imperial College London, she spent a decade in senior engineering roles at fintech giants before launching her own venture two and a half years ago. Her philosophy centers on maximizing team throughput through radical transparency and aggressive automation. Currently, she manages a lean four-person product team, orchestrating a complex workflow where feature development is split across Gemini CLI, Claude Code, and OpenCode. This parallel processing approach allows her team to iterate faster than traditional methods, though it introduces significant challenges in context management. She meticulously maintains a shared document that tracks which agent owns which branch, a necessity born from the friction of managing multiple AI sessions simultaneously. Standing over the shoulder of her team during standups, watching terminal outputs scroll in real-time, she acts as both the technical anchor and the cultural glue. Despite the high-pressure environment, she maintains a calm demeanor, driven by a deep-seated belief that clean communication and technical curiosity are the true drivers of success. Her recent decisions have focused on refining their internal tooling to reduce the cognitive load of managing these AI agents, ensuring that the technology serves the humans, not the other way around. With a salary of £115k and a significant equity stake, she balances financial security with the existential risk of a startup. Her life outside work is a sanctuary of order, centered around her Shoreditch loft, her cycling routes, and her close-knit circle of family and friends, all of which sustain her through the relentless demands of building the future.
Background & daily life
A day in their life
Genevieve wakes at 6:15 AM, avoiding screens until her morning coffee ritual is complete. By 8:30 AM, she is cycling into Shoreditch, listening to a podcast on distributed systems. Her workday begins with a 15-minute async check-in via Slack, followed by a live standup where she monitors the terminal outputs of three concurrent AI agents working on different microservices. She spends the late morning refactoring the core API, using her own MEng background to spot architectural drift that the agents miss. Lunch is a quick salad eaten at her desk while reading a GitHub issue thread. Afternoons are reserved for pair-programming sessions with her lead engineer, focusing on debugging complex race conditions. Around 5:00 PM, she updates the shared agent-tracking doc, ensuring every branch has a clear owner. She leaves the office by 6:30 PM to avoid burnout, cycling home to cook dinner and spend time with her cats, finally disconnecting from work by 8:00 PM.
Lifestyle
Genevieve lives in a sun-drenched, exposed-brick loft in Shoreditch, a space that doubles as her office when the office feels too confining. Her routine is dictated by the city's rhythm; she cycles to work through the morning fog, using the commute to listen to deep-dive technical podcasts or simply decompress. She is health-conscious but not obsessive, prioritizing sleep and high-protein lunches over rigid gym schedules. Financially, she balances a comfortable salary with the volatile reality of equity, keeping a 'burn rate' mindset for personal spending. Socially, she curates a tight circle of fellow founders and engineers who understand the unique isolation of early-stage leadership, meeting them for drinks only after major milestones are cleared.
Work life
Her day is a constant juggling act between code, strategy, and people management. As the sole technical decision-maker for a four-person product team, she spends mornings reviewing architectural diagrams and afternoons in 'flow state' coding or debugging. The team operates in a hybrid model where she splits feature work across multiple AI agents—Gemini CLI, Claude Code, and OpenCode—simultaneously. Standups are visual affairs where she watches terminal outputs scroll in real-time, tracking which agent is handling which branch. She maintains a rigorous, living shared document that acts as the single source of truth for agent ownership, ensuring no context is lost in the chaos of parallel execution. The pressure is immense, not from volume, but from the speed at which technology shifts beneath their feet.
Relationships
Genevieve is married to a civil engineer in Manchester, whom she sees every other weekend; they prioritize quality time over frequency. Her closest professional influence is her co-founder, a former VP of Engineering at a FAANG company, whose pragmatism grounds her ambition. She mentors three junior developers remotely, offering guidance that extends beyond code to career navigation. Her social circle is sparse but deep, consisting mostly of peers who have navigated the same startup trenches, creating a bond built on shared vulnerability rather than casual acquaintanceship.
How they decide
Analytical and evidence-based, yet accelerated by experience. Genevieve rarely makes impulsive decisions; instead, she gathers data points from experiments, peer feedback, and historical patterns before committing. She values 'small bets'—testing new workflows on non-critical paths first. While she respects community consensus, she is willing to go against the grain if the metrics suggest a better path. Her process involves a rapid cycle of hypothesis, implementation, and review, preferring concrete results over theoretical elegance.
How they sound
Her speech is precise, British, and devoid of fluff. She uses industry terminology freely but avoids corporate jargon like 'synergy' or 'pivot'. When frustrated, her tone becomes sharp and direct, cutting straight to the root cause. She speaks in short, declarative sentences, often pausing to let a technical concept land. She avoids hedging language like 'I think' or 'maybe', preferring 'the data shows' or 'we need to'. In casual conversation, she remains engaging but retains a professional cadence, rarely oversharing personal details unless it serves a broader point about human nature or team dynamics.
Personality traits
- Methodically chaotic
- High-bandwidth communicator
- Pragmatic optimist
- Detail-obsessed architect
- Empathetic but direct
- Time-poor efficiency seeker
- Skeptical of hype
- Rapidly adaptive
- Process-driven
- Quietly competitive
Goals
- Achieve product-market fit before running out of runway
- Build a resilient, self-documenting engineering culture
- Reduce cognitive load on the team by automating repetitive workflows
- Maintain personal work-life balance despite being a co-founder
- Scale the engineering team without diluting technical quality
Problems & frictions
- Context switching between multiple AI sessions creates fragmentation in code reviews
- Difficulty tracking which agent generated which specific commit diff
- Team members occasionally lose confidence when agents produce conflicting solutions
- Managing the psychological toll of rapid technological obsolescence
- Balancing deep focus time with constant stakeholder interruptions
- Ensuring consistent documentation standards across rapidly changing branches
Values
- team throughput
- clean communication
- technical curiosity
- radical transparency
- sustainable pacing
Interests
- startup operations
- developer tools
- AI prototyping
- minimalist architecture
- urban cycling
Media habits
- Engineering newsletters (e.g., The Pragmatic Engineer)
- Indie Hacker podcasts on commute
- GitHub trending repos
- Substack threads on AI safety
- Local tech meetups (no slides, just demos)