10 fictional AI personas. Exploratory perspectives, not a survey of real customers. Methodology & limitations

Simon O'Hara-Olson

Simon O'Hara-Olson

UI engineer at an early-growth SaaS startup

Full-depth AI personas

Why this persona fits the audience

Works in Manchester on a 4-person frontend team for a scheduling SaaS. He combines Chakra UI, internal wrappers, and a paid third-party admin template on older screens, while the current design system is maintained across Figma and a shared component repo.

  • Age: 35
  • Location: Manchester, UK
  • Occupation: UI Engineer
  • Income: £72k + bonus
  • Education: M.S. in Human-Computer Interaction
  • Company size: 18 employees
  • Years in role: 4
“I don't care how fast we ship if the foundation collapses under the weight of our own shortcuts.”

Simon O'Hara-Olson is a 35-year-old UI Engineer based in Manchester, UK, currently navigating the complexities of early-stage growth at a scheduling SaaS startup. With an M.S. in Human-Computer Interaction, Simon possesses a rare blend of academic rigor and pragmatic engineering skills. He joined the company four years ago as one of the first developers, witnessing the evolution from a scrappy MVP to a product handling thousands of enterprise clients. Today, he serves as the frontline architect of the user interface, tasked with the monumental challenge of unifying a fragmented visual language. His environment is a patchwork of modern innovation and necessary compromise; he actively maintains a robust Chakra UI design system for new features while simultaneously wrestling with a paid third-party admin template that powers the application's legacy screens. This duality requires him to constantly write internal wrapper components, acting as a bridge between disparate codebases to ensure a consistent user experience. Simon's professional life is defined by a relentless pursuit of consistency and speed, values that drive his meticulous approach to TypeScript and system design. He is known among his peers for his ability to spot architectural flaws early and his willingness to push back on unrealistic deadlines to preserve code quality. Despite the pressures of a four-person team where every member wears multiple hats, Simon maintains a steady hand, prioritizing long-term maintainability over short-term gains. Outside of work, he channels his energy into maintaining a structured home life, cycling regularly, and engaging in thoughtful debates about technology with his wife. His career trajectory is not driven by the desire for fame, but by the satisfaction of building systems that are elegant, scalable, and resilient.

Background & daily life

A day in their life

Simon wakes at 6:30 AM, brewing coffee and checking emails on his phone before getting out of bed. After a light breakfast, he cycles to the office in Didsbury, listening to a tech podcast to prime his brain for the day. Upon arrival, he attends a 15-minute stand-up where he clarifies the blockers for the current sprint, specifically regarding the mismatched styles in the legacy admin panel. His morning is dedicated to deep work: refactoring a complex data table component using TypeScript generics to ensure type safety. Lunch is a quick sandwich eaten at his desk while reviewing pull requests, focusing on accessibility standards. The afternoon involves a collaborative session with the product manager to define the scope of a new dashboard widget, translating their vague requirements into concrete UI specs. He finishes by updating the internal documentation wiki and pushing a commit that fixes a subtle layout shift on mobile devices, leaving the office by 6:00 PM to cook dinner and relax with his partner.

Lifestyle

Simon lives in a quiet corner of Didsbury, Manchester, where his days are structured around efficiency. His home office is a sanctuary of ergonomic furniture and dual monitors, reflecting his belief that physical comfort dictates coding output. He maintains a disciplined routine: cycling to work three times a week to clear his head, followed by evening cooking sessions that focus on healthy, quick meals. Financially, he is prudent, maximizing his pension contributions and avoiding unnecessary luxury spending, preferring to invest in high-quality tools that last. Socially, he keeps a tight circle of close friends and family, valuing depth over breadth in relationships, often gathering for board game nights or casual drinks rather than loud parties.

Work life

At his small SaaS startup, Simon is the de facto guardian of the user interface. His reality involves stitching together a fragmented tech stack: maintaining legacy screens built on a paid third-party admin template while simultaneously migrating new features to a modern Chakra UI-based design system. He spends significant time writing internal wrapper components to enforce consistency across the codebase, ensuring that the Figma designs match the actual implementation. The pressure comes from the need to move fast as a four-person team, balancing immediate feature requests with the long-term necessity of refactoring technical debt. His days are dominated by TypeScript configuration, debugging layout shifts, and code reviews that focus heavily on accessibility and maintainability.

Relationships

Simon is married to a graphic designer who shares his appreciation for clean aesthetics, though they debate the merits of functional minimalism versus artistic expression. Their relationship is grounded in mutual respect for each other's professional expertise. He has a small group of university friends in Manchester who meet monthly, mostly discussing career trajectories and local politics rather than technology. His primary influence comes from senior engineers he follows online, whose rigorous approach to system design shapes his own daily decisions. Family remains a priority, with regular Sunday dinners serving as his anchor against work stress.

How they decide

Simon employs a research-heavy, evidence-based decision style. He rarely adopts new technologies or methodologies based on marketing hype; instead, he demands proof of stability, community support, and backward compatibility. When evaluating a solution, he mentally simulates its integration into his existing architecture, weighing the long-term maintenance cost against immediate benefits. He seeks peer validation through technical forums and GitHub discussions before committing to a path, often running small prototypes to verify assumptions. His choices are cautious, calculated, and driven by a desire to minimize future regret and technical debt.

How they sound

Simon speaks with a calm, measured Mancunian cadence, using precise terminology without unnecessary jargon. He avoids hyperbole and emotional language, preferring direct statements like 'that won't scale' or 'the type safety is insufficient.' He tends to pause before answering complex questions, formulating his thoughts carefully. In conversation, he listens more than he speaks, often nodding thoughtfully before offering a concise, well-reasoned counterpoint. He dislikes corporate buzzwords and will gently steer conversations back to practical realities.

Personality traits

  • methodical
  • quietly authoritative
  • perfectionist about edge cases
  • efficient communicator
  • tech-skeptical of hype
  • reliable
  • boundary-conscious
  • detail-oriented
  • pragmatic
  • analytical

Goals

  • Achieve 99% visual parity between Figma designs and production React components
  • Reduce the monolithic component library into modular, reusable sub-systems
  • Lead a migration of all legacy admin templates to the new unified design system within 12 months
  • Improve the team's deployment speed by automating component testing pipelines
  • Secure a Senior Staff Engineer title through architectural leadership rather than management
  • Build a personal portfolio of open-source utilities that solve common SaaS UI problems

Problems & frictions

  • The friction of maintaining two divergent design systems (legacy vs. modern) causes confusion for new hires
  • Limited bandwidth to refactor old code while meeting aggressive product launch deadlines
  • Inconsistent styling in the paid third-party template makes custom theming difficult and error-prone
  • Difficulty explaining the value of technical debt reduction to non-technical founders focused on revenue
  • Time zones and communication gaps when collaborating with remote backend engineers
  • Keeping up with rapid changes in the React ecosystem without breaking existing stable features

Values

  • consistency
  • speed
  • practicality
  • technical debt reduction
  • user-centric logic

Interests

  • admin dashboards
  • TypeScript
  • system design
  • minimalist home office setups
  • Scottish football

Media habits

  • Listening to 'Software Engineering Daily' podcasts during commutes
  • Reading Hacker News and specific GitHub repositories on weekends
  • Following niche CSS architecture blogs
  • Watching technical deep-dive videos on YouTube (no skippable ads)
  • Checking LinkedIn for industry shifts but rarely posting

Questions & answers

Simon O'Hara-Olson’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Open source React components, blocks and a design system for building SaaS applications. Built on Chakra UI, with a Figma kit and themeable primitives. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    The biggest problem we have is unifying the look and feel across our legacy admin panel, which uses a third-party template, and our newer Chakra UI components. It’s a constant battle. We spend a significant amount of time writing wrapper components and patching inconsistencies. I’ve tried to create style guides and component libraries, but it’s a losing battle when the underlying template is so rigid. This costs us development time – easily a day or two each sprint – and leads to user frustration on older screens. I'm not sure how a new set of components would help if they don't directly address the legacy issues or provide a significantly better way to bridge the gap.
    View answer & full research →
Keep exploring

What would you ask next?

Test another angle with this panel, or create an audience for your own market.