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

Sean Hauck

Sean Hauck

software engineer

Full-depth AI personas

Why this persona fits the audience

He is a mid-level software engineer in Manchester on a four-person ecommerce team, using Cursor and Copilot to work through TypeScript and Shopify customizations. He documents unfinished agent work in Linear and a shared Markdown checklist.

  • Age: 25
  • Location: Manchester, UK
  • Occupation: Software engineer at an ecommerce company
  • Income: £62k
  • Education: BSc in Software Engineering
  • Company size: Small to medium-sized enterprise (SME) with ~150 employees
  • Years in role: 3
“It's about building things that work well, not just working fast. Small, consistent improvements add up to something solid in the end.”

Sean Hauck, 25, is a diligent software engineer deeply embedded in the ecommerce world of Manchester. His journey into software engineering began with a fascination for how digital systems ticked, leading him to pursue a BSc in Software Engineering at a reputable UK university. Upon graduation, he joined his current company, drawn by the challenge of working with live customer-facing systems and the opportunity to specialize in frontend and backend development for an online retail platform. He's now three years into his role, having progressed to a mid-level position within a focused four-person team. His daily work revolves around maintaining and enhancing the company's Shopify-based ecommerce store, a task that requires a solid grasp of TypeScript, Liquid templating, and various API integrations. Sean has embraced modern development tools with enthusiasm; he's a regular user of Cursor for its AI-assisted coding capabilities and GitHub Copilot, finding that they significantly streamline his workflow, especially when debugging complex issues or exploring new implementation patterns. He’s keenly aware of the costs associated with these tools and is always looking for ways to optimize their usage without sacrificing productivity. Beyond the immediate demands of his job, Sean is driven by a desire for craftsmanship and steady progress, preferring to build robust, well-considered solutions rather than quick fixes. He’s saving diligently for a deposit on his own flat, reflecting a pragmatic approach to his financial future, and finds solace and focus in his hobbies of playing the guitar and regular running. His team operates with a strong emphasis on transparency, a value Sean deeply appreciates as it fosters trust and facilitates collaborative problem-solving. He meticulously documents unfinished work in Linear and shared Markdown checklists, a testament to his conscientious nature and commitment to thoroughness. Sean's career goal is to evolve into a senior engineer, contributing to more complex architectural decisions and potentially mentoring junior developers, while always striving to maintain the work-life balance that he values highly.

Background & daily life

A day in their life

Sean's typical weekday begins around 7:30 AM with coffee and a quick scan of Hacker News. He leaves his flat by 8:15 AM, often listening to a tech podcast on his commute to the office. His workday starts with checking his Linear board and the team's shared checklist for urgent tasks or updates. The morning is usually spent coding, tackling tickets, and collaborating with colleagues on feature development or bug fixes, heavily utilizing Cursor and Copilot. Lunch is a quick affair, often a sandwich at his desk or a walk to a nearby cafe. The afternoon might involve code reviews, sprint planning meetings, or diving into documentation for a new integration. He aims to wrap up by 5:30 PM, sometimes staying a bit later if a critical issue arises. Evenings are for personal pursuits: a run, guitar practice, or research for personal projects.

Lifestyle

Sean lives a fairly routine life in a rented flat in Chorlton, Manchester, sharing with an old university friend who works in marketing. His weekdays are structured around work, punctuated by his hobbies. Evenings are typically spent either practicing guitar, going for a run along the River Mersey, or catching up on tech blogs. He's conscious about his finances, saving a decent portion of his salary towards a deposit for a small flat of his own, but he doesn't shy away from occasional treats like a new piece of tech or concert tickets. Socially, he enjoys quiet nights in with friends or casual meetups at a local pub.

Work life

As a mid-level engineer on a four-person ecommerce team, Sean’s days are a blend of focused coding and collaborative problem-solving. He spends a significant chunk of his time wrestling with complex TypeScript logic and customizing Shopify themes, often leveraging AI tools like Cursor and GitHub Copilot to accelerate development and explore solutions. When a task isn't fully resolved or requires further investigation, he meticulously documents the unfinished aspects and potential next steps in Linear, supplementing this with entries in a shared team Markdown checklist. He values clear communication and works closely with his immediate colleagues, aiming for a transparent workflow where everyone is aware of progress and potential roadblocks. The pressure is usually to deliver features on time while maintaining code quality and site performance.

Relationships

Sean maintains close ties with his university friends, though they often see each other less frequently than they used to. His immediate family lives in the North East, and they talk on the phone weekly. Within his team, he has a good working relationship with his three colleagues, characterized by mutual respect and a willingness to help each other out. His flatmate provides a casual social outlet and a sounding board for non-work-related issues.

How they decide

Sean generally approaches decisions methodically. He’ll often research options thoroughly, compare pros and cons, and consider the long-term implications. He’s not impulsive and prefers to have a clear understanding of the problem and potential solutions before committing. Peer recommendations and documented evidence (e.g., benchmarks, case studies) carry significant weight, but he ultimately relies on his own analysis to make a final choice.

How they sound

Sean speaks with a clear, measured cadence, typical of a Manchester accent but without excessive slang. He tends to be articulate and precise when discussing technical topics. In casual conversation, he’s friendly but generally avoids overly effusive language or hyperbole. He prefers directness and clarity, especially in professional settings, and will often pause to formulate his thoughts before responding to complex questions. He tends to understate his achievements and focus on the process or the team effort.

Personality traits

  • Analytical
  • Diligent
  • Methodical
  • Pragmatic
  • Curious
  • Cooperative
  • Resourceful
  • Focused
  • Slightly reserved

Goals

  • Achieve senior engineer status within the next three years.
  • Contribute to an open-source project related to ecommerce infrastructure.
  • Purchase his own property in the Manchester area.
  • Develop deeper expertise in scalable backend systems.
  • Maintain a healthy work-life balance, avoiding burnout.

Problems & frictions

  • The constant need to keep up with rapidly evolving AI tools and their integration into existing workflows.
  • Balancing the desire for perfect, optimized code with tight project deadlines.
  • Navigating legacy codebases that can be challenging to refactor efficiently.
  • The occasional frustration of AI-generated code requiring significant manual correction.
  • Finding effective ways to reduce the operational costs associated with frequent AI agent usage for complex tasks.

Values

  • craftsmanship
  • steady progress
  • team transparency
  • efficiency
  • continuous learning

Interests

  • ecommerce systems
  • guitar
  • running
  • TypeScript
  • AI coding assistants
  • backend optimization

Media habits

  • Follows tech news sites (e.g., Hacker News, The Verge)
  • Listens to podcasts on programming and AI during commutes
  • Watches YouTube tutorials for new libraries and frameworks
  • Active on Stack Overflow and GitHub
  • ocasionaly scrolls through LinkedIn for industry trends

Questions & answers

Sean Hauck’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://www.paritok.com/ (Paritok) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    Landing on Paritok, the main thing that's unclear is how this "compression gateway" actually integrates with my existing AI coding tools like Cursor and Copilot. The description says it "drops in between," but I'm not seeing a clear path for that. It sounds interesting for potentially saving on LLM bills, which is always a consideration, and the idea of longer sessions is appealing for tackling more complex Shopify customizations. However, the pricing model for the hosted GPU version, $0.30 per 1M billable file tokens, is a bit vague without knowing how many tokens that actually represents in practice. I'd want to see a more concrete example of the integration and clearer pricing before considering signing up.
    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.