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

Leo Graham

Leo Graham

Early-career front-end developer

Full-depth AI personas

Why this persona fits the audience

Is a junior front-end developer in Manchester, building a portfolio around freelance sites, bootcamp projects, and a few volunteer builds. Uses GitHub Pages, a PDF resume, and a spreadsheet to keep versions straight while applying to developer roles.

  • Age: 29
  • Location: Manchester, UK
  • Occupation: Front-End Developer
  • Income: GBP 48k
  • Education: Computer Science diploma plus bootcamp
  • Company size: 15-person fintech startup
  • Years in role: 1.5
“Code should do exactly what it says it does, nothing more and nothing less; if I can't explain why a line exists, it shouldn't be there.”

Leo Graham is a twenty-nine-year-old front-end developer navigating the competitive tech landscape of Manchester. Originally holding a Computer Science diploma, he pivoted into web development through an intensive six-month bootcamp, driven by a desire for practical, tangible output. Currently employed at a fifteen-person fintech startup earning GBP 48,000 annually, Leo balances full-time responsibilities with a side hustle of freelance builds and volunteer projects for local charities. His workflow is defined by a rigorous organizational approach; he maintains a custom spreadsheet to track project versions, ensuring that his GitHub Pages portfolio remains pristine despite frequent updates. This meticulous nature stems from a personality high in conscientiousness, where reliability and progress are paramount. Leo’s interests extend beyond coding; he is an avid home networking enthusiast, constantly upgrading his mesh Wi-Fi setup, and a devoted supporter of local football. Despite a moderate level of neuroticism regarding career stability, he channels anxiety into learning, dedicating evenings to mastering open-source contributions. Recently, he made the strategic decision to pause social media activity to focus on refining his React portfolio, believing that quality of work outweighs quantity of exposure. Living in a shared flat, he manages finances with strict discipline, allocating funds for future home ownership while investing in continuous education. Leo represents the modern self-directed learner: pragmatic, slightly anxious, yet relentlessly focused on building a sustainable and meaningful career in technology.

Background & daily life

A day in their life

Leo wakes up at 6:30 AM, brewing strong coffee while checking the weather and football scores. By 7:45 AM, he is cycling to his office in Ancoats, listening to a tech podcast. Work begins with a quick stand-up at 9:30 AM, followed by a block of uninterrupted coding until lunch. At 1 PM, he takes a walk outside to clear his head before tackling complex bugs in the afternoon. After finishing his tasks, he stays until 6:00 PM to review pull requests for his teammates. On Tuesdays and Thursdays, he heads to the gym post-work. Evenings are reserved for his home networking projects or studying React patterns. He winds down by reading a non-fiction book on productivity before bed, avoiding screens after 10:30 PM to ensure good sleep for the next day.

Lifestyle

Leo lives in a converted warehouse flat in Ancoats with two colleagues, splitting rent and utilities to manage the cost of living in Manchester. His evenings are split between optimizing his home lab—tinkering with Raspberry Pis and mesh Wi-Fi routers—and watching Manchester United or local lower-league matches on a large TV. He is health-conscious, running three times a week along the Irwell Valley, though he often skips sessions when a tight deadline hits. Financially, he is budget-conscious, using a spreadsheet to track every subscription and expense, prioritizing savings for a future deposit over luxury purchases. Socially, he prefers small gatherings at friends' houses rather than loud clubs, valuing deep conversation over high-energy networking events.

Work life

At a mid-sized fintech startup, Leo spends most of his day writing React components and debugging CSS grid layouts. He works alongside four other developers and a product manager who pushes hard for speed, often creating friction with Leo's desire for clean, documented code. His mornings start with a stand-up meeting where he reports on ticket progress, followed by hours of focused coding interrupted by Slack pings and Jira updates. He relies heavily on VS Code extensions and Chrome DevTools, often staying late to fix browser compatibility issues that the QA team missed. The pressure to deliver features quickly sometimes conflicts with his instinct to refactor, leading to a constant internal negotiation between technical debt and shipping velocity.

Relationships

Leo is close to his younger sister, who studies graphic design, often seeking her advice on visual presentation. He has a tight-knit group of five university friends who meet monthly for dinner and board games. His primary professional influence is his current mentor, Sarah, a lead engineer who taught him the value of code documentation. He volunteers occasionally with a local coding club for teenagers, finding it rewarding to explain basic concepts. While not widely known in the city's tech scene, he has built a reputation as the reliable guy who actually reads the documentation.

How they decide

Leo is a methodical researcher who avoids impulse buys. He typically gathers information from forums, official documentation, and peer reviews before committing to any new tool or purchase. He values transparency and detailed specifications over marketing fluff. If a decision involves money, he creates a comparison table weighing long-term utility against immediate cost. He rarely changes his mind once he has validated a choice, preferring stability and proven reliability over experimental novelty unless the benefits are overwhelmingly clear.

How they sound

Leo speaks with a distinct Mancunian accent, softening his consonants but maintaining a precise, articulate cadence. He tends to be direct and factual, avoiding hyperbole or emotional language. In professional settings, he uses industry-standard terminology confidently but admits gaps in knowledge immediately rather than bluffing. He rarely uses slang in formal contexts but might drop casual phrases like 'sorted' or 'fair enough' with peers. He avoids saying 'I think' without backing it up with data, preferring statements like 'The logs indicate' or 'Based on the specs.' His tone is generally calm and measured, even when discussing stressful deadlines.

Personality traits

  • meticulously organized
  • quietly persistent
  • analytically cautious
  • self-taught pragmatist
  • socially reserved but warm
  • tech-savvy DIYer
  • detail-oriented
  • mildly anxious about obsolescence
  • team-player
  • methodical

Goals

  • Secure a permanent Senior Front-End role within two years
  • Contribute meaningfully to a major open-source library
  • Build a fully automated smart home system from scratch
  • Achieve financial independence through disciplined saving
  • Learn TypeScript deeply to modernize legacy codebases
  • Improve his physical fitness to run a half-marathon

Problems & frictions

  • Difficulty maintaining version control across multiple freelance projects
  • Lack of a centralized place to showcase volunteer work alongside paid gigs
  • Time management struggles between upskilling and daily job demands
  • Uncertainty about which technical skills will remain relevant long-term
  • Frustration with inconsistent feedback loops from hiring managers
  • Overwhelmed by the sheer volume of new frameworks and tools released weekly

Values

  • reliability
  • learning
  • practicality
  • progress

Interests

  • React
  • open source
  • football
  • home networking

Media habits

  • The Changelog podcast
  • Local football match replays
  • Reddit r/webdev
  • Spotify 'Deep Focus' playlists
  • Tech Twitter threads
  • BBC News morning briefings

Questions & answers

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

  1. Looking at Portie (https://www.portie.me): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    A one-time payment of $10 for a year of access sounds like a no-brainer, honestly. That's less than a tenner, which is what I'd probably spend on lunch. For that, I'd expect a clean, professional-looking site that's easy to update and showcases my projects clearly, especially the tech stack. If it started creeping up towards £50 for a year, I'd probably hold off and stick with refining my GitHub Pages setup, especially since I'm trying to save for a house deposit. I wouldn't pay a monthly subscription for something like this, so my maximum would be $10 one-time payment.
    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.