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

Leo Kiehn

Leo Kiehn

Front-end developer at a fintech startup

Full-depth AI personas

Why this persona fits the audience

Works in a 6-person product team and turns founder screenshots and competitor URLs into editable UI drafts before rebuilding them in React. Uses v0 and Figma as starting points for internal review, then aligns the output with the design system.

  • Age: 27
  • Location: London, UK
  • Occupation: Front-end developer
  • Income: £58k
  • Education: BSc in Computer Science
  • Company size: Small (6 people)
  • Years in role: 3
“Code isn't just instructions; it's the only thing that truly exists when you're building something from nothing.”

Leo Kiehn is a 27-year-old Front-end Developer based in London, currently embedded in a high-velocity fintech startup. Holding a BSc in Computer Science, Leo has spent the last three years navigating the transition from academic theory to the chaotic reality of product development. His role is uniquely positioned at the intersection of design and engineering; he acts as the bridge between the founder's vision and the final user interface. While the founders provide screenshots, competitor URLs, or napkin sketches, Leo is responsible for transforming these abstract inputs into editable, production-ready UI drafts using React. He leverages generative tools like v0 and Figma to accelerate the initial drafting phase, but his true value lies in his ability to refine these outputs, ensuring they strictly adhere to the company's evolving design system. This process requires a delicate balance of speed and precision, as any deviation can lead to significant technical debt down the line. Living in a shared flat in Shoreditch, Leo's lifestyle reflects his personality: structured yet adaptable. He commutes by bicycle, a routine that keeps him grounded amidst the city's frenetic pace. Professionally, he is driven by a desire for technical excellence and collaborative efficiency. He values clean code and streamlined handoffs, often finding himself frustrated by the ambiguity inherent in early-stage product development. His recent decisions have focused on automating repetitive tasks and refining his workflow to handle the rapid iteration cycles required by his small, six-person team. Despite the pressures of a startup environment, Leo remains calm and analytical, preferring to solve problems logically rather than reacting emotionally. He is not looking for a silver bullet to fix his job, but rather tools that respect his expertise and enhance his ability to deliver high-quality software without compromising his own standards.

Background & daily life

A day in their life

Leo wakes up at 7:00 AM, brews coffee while scrolling through GitHub trends and industry newsletters. He cycles to the office, arriving by 8:45 AM to catch the morning stand-up. By 9:30 AM, he is diving into a ticket involving a complex form validation issue, switching between VS Code and Figma. Lunch is a quick sandwich eaten at his desk while watching a tutorial on Next.js performance optimization. Afternoon meetings are dominated by clarifying ambiguous requirements from the founder, requiring him to translate vague concepts into technical specs. He spends the late afternoon debugging a CSS layout issue caused by an auto-generated component, ensuring it adheres to the design tokens. He leaves around 6:30 PM, heading home to cook dinner and read about system architecture before bed.

Lifestyle

Leo lives in a modern, slightly noisy flat in Shoreditch, sharing costs to maintain proximity to London's tech hub. His apartment is a sanctuary of order: a standing desk, noise-canceling headphones, and a single large monitor dominate his space. He cycles to work daily, viewing it as both exercise and a way to dodge the Underground chaos. On weekends, he retreats to analog hobbies like reading technical manuals or hiking in Epping Forest to disconnect from screens. Financially, he is cautious but willing to invest in tools that save time; he pays for premium software subscriptions if they offer clear ROI, avoiding unnecessary clutter. Socially, he prefers small gatherings with close friends over loud networking events, valuing deep conversation over broad socializing.

Work life

Leo operates within a lean six-person product team where speed is currency. His core reality involves translating raw founder ideas—often just rough sketches or competitor links—into functional prototypes using React and Figma. He relies heavily on AI-assisted generators like v0 to create initial drafts, which he then meticulously refines to match the company's strict design system. The pressure comes from the need to balance rapid iteration with code quality; one sloppy commit can break the build pipeline. He spends half his day in Slack and Figma comments, negotiating pixel-perfect details with non-technical founders, and the other half writing clean, reusable components. Collaboration is constant, but he often works solo during deep coding sprints to ensure technical integrity.

Relationships

Leo maintains a tight-knit circle of three childhood friends and two colleagues who understand the grind of startup life. He is close to his younger sister, who studies graphic design, often exchanging feedback on visual aesthetics. His primary influence comes from senior engineers at larger firms whom he follows on social media. He rarely engages in office politics, preferring to let his code speak for him, but he values transparency and direct communication above all else in his professional relationships.

How they decide

Leo is a calculated researcher who avoids impulsive purchases. He evaluates new tools by testing free tiers extensively, checking community reviews on GitHub or Reddit, and analyzing whether the integration workflow fits his existing stack. He is skeptical of marketing fluff and looks for concrete evidence of efficiency gains before committing resources.

How they sound

Leo speaks with a clipped, efficient British cadence, rarely using filler words. He defaults to standard English but drops into specific technical jargon when discussing architecture or frameworks. He avoids hyperbole and emotional language, preferring factual descriptions. In casual settings, he remains polite but reserved, often listening more than speaking. He uses phrases like 'technically feasible,' 'that won't scale,' or 'let's iterate on that' frequently. He never overshares personal details in a professional context.

Personality traits

  • Methodical
  • Quietly opinionated
  • Detail-oriented
  • Process-driven
  • Pragmatic
  • Low-drama
  • Analytical
  • Independent worker
  • Efficiency-obsessed
  • Technically precise

Goals

  • Achieve senior engineer status within the next two years
  • Build a personal library of reusable React components
  • Master advanced TypeScript patterns
  • Maintain a sustainable work-life balance while startups scale
  • Contribute meaningfully to open-source projects on weekends

Problems & frictions

  • The friction between rapid prototyping and maintaining a scalable design system
  • Managing vague requirements from non-technical founders
  • Time lost manually converting designs to editable code structures
  • Balancing technical debt accumulation with feature velocity
  • Finding reliable documentation for niche React libraries

Values

  • technical accuracy
  • collaboration
  • efficient handoff
  • clean code
  • pragmatic innovation

Interests

  • React
  • design systems
  • developer tooling
  • minimalist workspace setups
  • urban cycling

Media habits

  • Loves the 'Syntax' podcast
  • Follows specific Substack newsletters on React patterns
  • Watches GitHub trend pages weekly
  • Scrolls Twitter/X for dev tool announcements
  • Reads Medium articles on scaling frontend architecture

Questions & answers

Leo Kiehn’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of UX Magic (https://uxmagic.ai/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make UX Magic better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I use Figma and v0 for initial drafts, translating founder screenshots into editable UI. UX Magic's ability to clone URLs and generate code directly is interesting, potentially saving some time. However, the crucial part for me is how well it aligns with an existing design system. If the output requires significant rework to match our tokens, it negates the speed advantage. The promise of 'production-ready code' is also key; I'd need to verify its quality and adherence to our standards. I'm hesitant to commit to another subscription without a clear ROI. I wouldn't pay more than $30 per month for this.
    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.