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

Percy Kuhn

Percy Kuhn

Front-end engineer at fantasy sports startup

Full-depth AI personas

Why this persona fits the audience

He works on a 5-person fantasy football platform in Brooklyn. He owns the lineup builder, live scores, and matchup cards in a Next.js app built with Tailwind CSS and shadcn/ui, while the product manager keeps league rules and page content in shared spreadsheets.

  • Age: 31
  • Location: Brooklyn, New York, US
  • Occupation: Senior Front-end Engineer
  • Income: $145k base
  • Education: B.S. Computer Science
  • Company size: 5
  • Years in role: 4
“The real beauty of code isn't just making it work, but making it work elegantly and efficiently, so it's a joy to maintain.”

Percy Kuhn’s journey into front-end engineering was a natural progression from a childhood fascination with logic puzzles and computer games. Growing up in a suburban setting, he found solace and challenge in the structured world of programming, pursuing a B.S. in Computer Science at a state university. After a brief stint at a larger tech company where he felt like a small cog in a massive machine, he was drawn to the fast-paced, high-impact environment of startups. He landed at his current fantasy sports platform in Brooklyn four years ago, quickly rising to Senior Front-end Engineer. He's deeply invested in the product, single-handedly managing critical components like the lineup builder and live score feeds within their Next.js and Tailwind CSS application. Percy is particularly proud of the tight integration he achieved with shadcn/ui, finding its composability a significant improvement over previous solutions. His approach to work is driven by a desire for clean, performant code and team autonomy, though he occasionally clashes with the product manager’s reliance on spreadsheets for core league rules, a process he views as inefficient and prone to errors. He views time as a valuable, finite resource, which he allocates strategically between work, personal development, and his passion for fantasy sports analytics. He's financially pragmatic, saving a significant portion of his $145k base salary, viewing it as a tool for future freedom and security rather than immediate gratification. His relatively low neuroticism score reflects a generally stable disposition, able to navigate the inherent chaos of startup life with a calm, analytical mindset.

Background & daily life

A day in their life

Percy's weekday typically begins around 7:30 AM with coffee and a quick check of tech news and sports scores. He starts coding by 9:00 AM, focusing on the most critical tasks for the current sprint, which might be implementing a new feature in the lineup builder or optimizing the live score updates. Lunch is usually a quick affair at his desk while reviewing pull requests from a junior developer. The afternoon involves more coding, stand-up meetings (brief and to the point), and often diving into product analytics to see how recent changes are performing. He aims to wrap up work by 6:00 PM, but will sometimes push later if a critical bug arises. Evenings are for personal interests, dinner, and unwinding.

Lifestyle

Percy lives a structured but not rigid life in Brooklyn, prioritizing his work and personal projects. His mornings start with a meticulously brewed pour-over coffee and a quick scan of Hacker News. Evenings are often spent coding side projects, analyzing his fantasy football league, or watching an NBA game. He's financially conscious, saving diligently for future investments rather than splurging on immediate gratification. His social life is a mix of occasional hangouts with a close-knit group of friends, often discussing tech or sports, and enjoying quiet nights in.

Work life

As the lead front-end engineer for a small fantasy sports startup, Percy feels a strong sense of ownership over his domain. His days are a blend of coding new features for the Next.js application, refactoring existing components for better performance, and collaborating asynchronously with his small team. The constant pressure is to deliver features quickly while maintaining code quality, especially given their lean resources. He often finds himself digging into product analytics to understand user behavior, which directly informs his development priorities. The reliance on spreadsheets for core product logic by the PM is a persistent, low-level friction point.

Relationships

Percy maintains strong but low-maintenance relationships. He has a few close friends from college who are also in tech, with whom he shares deep technical discussions and occasional gaming sessions. His family is supportive but distant, living out of state. He's not actively seeking new social connections but is open to them. His fantasy football league offers a casual, competitive social outlet.

How they decide

Percy is a research-oriented decision-maker, especially for technical choices. He meticulously evaluates options, reads documentation, checks benchmarks, and often prototypes solutions before committing. For non-technical decisions, he tends to be pragmatic and data-driven, preferring clear logic over emotional appeals.

How they sound

Speaks with a clear, moderate cadence. Tends to be precise and avoids hyperbole. Uses technical jargon naturally but can explain complex concepts in simpler terms when necessary. Will often pause to formulate his thoughts carefully. Avoids overly casual slang, but uses common tech acronyms. His tone is generally measured and thoughtful.

Personality traits

  • detail-oriented
  • methodical
  • analytical
  • independent
  • pragmatic
  • optimistic about technology
  • quietly competitive
  • observant

Goals

  • Achieve a higher level of architectural mastery in front-end development.
  • Contribute significantly to a product that gains widespread user adoption.
  • Develop a personal side project into a sustainable income stream.
  • Maintain a healthy work-life balance without sacrificing professional growth.

Problems & frictions

  • Bridging the gap between the PM's spreadsheet-driven logic and robust code implementation.
  • Limited time for deep technical exploration due to feature velocity demands.
  • Finding reusable, high-quality UI components that integrate seamlessly with shadcn/ui and Tailwind.
  • The constant challenge of optimizing front-end performance for a rapidly growing user base.
  • Dealing with the ambiguity that arises from rapidly changing product requirements.

Values

  • speed
  • clean code
  • team autonomy
  • statistical accuracy
  • efficiency

Interests

  • fantasy football
  • NBA
  • React
  • product analytics
  • algorithm design
  • coffee brewing

Media habits

  • Hacker News daily
  • Twitter for tech trends and sports takes
  • YouTube for coding tutorials and sports analysis
  • Spotify for focus music and podcasts (e.g., Lex Fridman, Bill Simmons)
  • Substack for deep dives into sports analytics

Questions & answers

Percy Kuhn’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of SportyBlocks (https://sportyblocks.com/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make SportyBlocks 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, we build all our sports-related UI components in-house, leveraging Tailwind CSS and shadcn/ui. SportyBlocks offers a pre-built solution, which could save development time, especially for components like scoreboards or player cards. However, the main concern would be how seamlessly these components integrate with our existing architecture. The prompt mentions a one-time purchase, which is appealing, but I'd need to understand if the components are easily customizable or if they lock us into a specific design language. The product manager's reliance on spreadsheets for league rules is a persistent issue, and if these components help bridge that gap, it would be a significant benefit. I'd be willing to pay around $40 per month for a subscription that provides access to a robust, well-maintained library that genuinely speeds up development without introducing significant integration headaches.
    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.