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

Roy Klocko

Roy Klocko

Full-stack engineer at a small startup

Full-depth AI personas

Why this persona fits the audience

Works at a 12-person startup in Denver and owns the Next.js admin app plus the marketing site. He codes with AI assistants, compares outputs against internal examples, and keeps a spreadsheet of mistakes around auth callbacks, Stripe webhooks, and Prisma schemas.

  • Age: 27
  • Location: Denver, Colorado, US
  • Occupation: Full-stack engineer at a startup
  • Income: US$98k plus equity
  • Education: Bachelor's degree in software engineering
  • Company size: 12-person startup
  • Years in role: 3
“I'd rather spend an extra hour making sure a feature is solid than spend three days fixing it later when it breaks unexpectedly.”

Roy Klocko, 27, is a dedicated full-stack engineer at a burgeoning 12-person startup in Denver, Colorado. His journey into software engineering began with a Bachelor's degree, fueled by a fascination with how complex systems are built and maintained. He found his niche in the dynamic startup environment, where he's responsible for the company's critical Next.js admin application and its public-facing marketing website. This dual role demands a broad skill set and a keen eye for detail, especially as the company scales. Roy embraces modern development workflows, integrating AI coding assistants into his daily routine. However, his inherent conscientiousness and desire for accountability mean he doesn't blindly trust AI outputs. Instead, he meticulously compares generated code against internal examples and established patterns, treating the AI as a powerful but fallible tool. This rigor is evident in his personal project: a detailed spreadsheet where he meticulously logs and analyzes mistakes encountered, particularly around complex integrations like authentication callbacks, Stripe webhooks, and Prisma schema migrations. This spreadsheet serves not just as a personal learning log but as a growing knowledge base for the team, reflecting his commitment to shared growth and stability. His income of US$98k, supplemented by startup equity, allows for a comfortable lifestyle, though he remains financially prudent, prioritizing long-term security. He views his current role as a significant growth opportunity, aiming to deepen his expertise and contribute meaningfully to the company's success, while also seeking opportunities for personal development and potential future leadership within the tech landscape.

Background & daily life

A day in their life

Roy's typical weekday begins around 7:30 AM with his espresso ritual and a quick news check. He's usually at his desk by 8:30 AM, diving into Slack and Jira to review overnight updates and plan his day. Mornings are often dedicated to focused coding, tackling tickets related to the admin app or marketing site, frequently using AI assistants for boilerplate code or complex logic. Lunch is a quick affair, often eaten at his desk while watching a coding tutorial. Afternoons involve code reviews, pair programming sessions with a colleague on a tricky bug, and responding to urgent requests. He tries to wrap up by 6:00 PM, but sometimes stays later if a critical deployment is pending. Evenings are for unwinding, perhaps a short gaming session or reading tech articles.

Lifestyle

Roy lives in a modest two-bedroom apartment in Denver's Capitol Hill neighborhood, sharing it with a college friend who works in graphic design. He's a creature of habit, starting his day with a meticulously brewed espresso using his Aeropress, followed by a quick scan of Hacker News. Weekends often involve diving into a new indie game or catching up on coding projects that pique his interest outside of work. While he enjoys the Denver social scene, his introverted tendencies mean he prefers smaller gatherings. He's mindful of his finances, aiming to save a significant portion of his income for future stability, though he'll occasionally splurge on a new mechanical keyboard or a high-quality coffee bean subscription.

Work life

As a full-stack engineer at a lean startup, Roy wears many hats, primarily focusing on the Next.js admin application and the company's marketing website. His days are a blend of feature development, bug fixing, and performance optimization. He leverages AI coding assistants extensively, but his conscientiousness compels him to rigorously test and validate every suggestion against established internal patterns and best practices. He maintains a detailed spreadsheet tracking recurring issues, particularly around complex areas like authentication callbacks, Stripe webhook integrations, and Prisma schema migrations, viewing it as a crucial tool for accountability and knowledge sharing within the small team.

Relationships

Roy maintains a close but not overly dependent relationship with his parents, who live in a suburb of Chicago. His core social circle consists of a few close friends from college, including his roommate, and a handful of colleagues he trusts implicitly. He values their opinions, especially on technical challenges, but ultimately makes his own decisions. He's not heavily influenced by social media trends but respects the insights shared within developer communities.

How they decide

Roy approaches decisions methodically. He gathers information from multiple sources, including documentation, community forums, and his own experimental testing. He weighs pros and cons, often creating lists or spreadsheets to compare options. While he values input from trusted peers, he prioritizes solutions that align with long-term stability and maintainability, showing a cautious but informed approach.

How they sound

Roy speaks clearly and deliberately, with a moderate pace. He tends to use precise technical language when discussing work but can be more casual with friends. He avoids hyperbole and overly strong opinions, preferring to qualify his statements. He might use phrases like 'It seems like,' 'My understanding is,' or 'We should probably consider.' He's not one for excessive slang but might use common developer jargon naturally.

Personality traits

  • Detail-oriented
  • Methodical
  • Pragmatic
  • Collaborative
  • Curious
  • Slightly anxious about edge cases
  • Resourceful
  • Independent learner

Goals

  • Become a senior engineer or tech lead within the next five years
  • Contribute to an open-source project he uses regularly
  • Achieve financial independence through smart investing and equity growth
  • Maintain a healthy work-life balance without sacrificing career progression
  • Build a robust and scalable architecture for the company's core product

Problems & frictions

  • The constant pressure to deliver features quickly in a startup environment can lead to technical debt if not managed carefully.
  • Ensuring the reliability and security of critical integrations like Stripe and Auth.js requires meticulous attention to detail, which can be time-consuming.
  • Balancing the use of AI coding tools with the need for deep understanding and manual verification.
  • The inherent instability and rapid changes common in early-stage startups can be stressful.
  • Finding time for deep learning and skill development amidst daily development demands.

Values

  • growth
  • teamwork
  • stability
  • accountability

Interests

  • React
  • gaming
  • espresso
  • AI tools

Media habits

  • Follows tech blogs like Hacker News and Dev.to
  • Listens to tech podcasts during commutes
  • Watches YouTube tutorials for new libraries
  • Active on Discord communities for specific frameworks
  • Reads documentation extensively

Questions & answers

Roy Klocko’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying VibeBoot (https://vibeboot.dev/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The main thing that would stop me is the need to integrate it with our existing systems. Right now, I handle errors and edge cases primarily through rigorous testing and detailed logging in my spreadsheet. I meticulously document issues around auth callbacks, Stripe webhooks, and Prisma schemas. The idea of a starter kit that already has these wired up is appealing, especially the focus on AI integration and rules. However, I'd need to see how easily it fits into our current Next.js setup and if it introduces any new complexities before I'd consider adopting it. If it streamlines the setup and maintenance of these critical integrations, I might consider paying around $25 per month for a starter kit like 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.