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

Moses Bernier

Moses Bernier

Staff backend engineer on a platform team

Full-depth AI personas

Why this persona fits the audience

Works on a 6-person platform team at a mid-size SaaS company in Seattle. Uses GitHub Copilot for day-to-day coding, has been testing Claude Code and Cursor in side projects, and keeps notes from those experiments in a shared spreadsheet for the team’s monthly AI tooling review.

  • Age: 34
  • Location: Seattle, WA, USA
  • Occupation: Staff Backend Engineer
  • Income: $210k base + bonus
  • Education: M.S. in Computer Science
  • Company size: Mid-size (approx. 800 employees)
  • Years in role: 4
“The elegance of a system isn't just in its speed, but in how predictably and reliably it handles the unexpected.”

Moses Bernier, at 34, has steadily built a reputation as a highly competent backend engineer, drawn to the intricate challenges of platform development. His M.S. in Computer Science from the University of Washington provided a strong theoretical foundation, which he has rigorously applied and expanded upon during his four years as a Staff Backend Engineer at his current mid-size SaaS company. Seattle's vibrant tech scene was a natural fit, and he thrives in its demanding, fast-paced environment. His income of $210k base plus bonus reflects his experience and the critical nature of his role in maintaining and evolving the company's core infrastructure. Moses approaches his work with a high degree of conscientiousness and openness, constantly seeking to deepen his technical understanding and explore new paradigms. He is particularly fascinated by the potential of AI in software development, actively experimenting with tools like GitHub Copilot, Claude Code, and Cursor. These explorations are not casual; he meticulously documents his findings and comparisons in a shared spreadsheet, a practice integral to his team’s monthly AI tooling review. This methodical approach extends to his system design principles, where he prioritizes robustness and scalability above all else. While he values peer collaboration and learning, his extraversion is moderate, preferring focused technical discussions over broad social networking. His life outside of work is equally deliberate, characterized by disciplined saving habits, a commitment to physical fitness through cycling and running, and a preference for intellectually stimulating leisure activities. He is driven by a desire for mastery and continuous improvement, aiming to build systems that are not only functional but also maintainable and efficient in the long term. His relationship with time is that of a careful steward; he invests it wisely in both professional development and personal well-being, recognizing that sustainable career growth requires a balanced approach.

Background & daily life

A day in their life

Moses's weekday begins around 7:00 AM with a quick check of overnight system alerts and key metrics, followed by a strong pour-over coffee. He commutes by bike if the weather permits, listening to a tech podcast. The morning is usually dedicated to focused coding, tackling complex tickets or refactoring tasks, often with GitHub Copilot assisting. After a brief team stand-up, he might spend an hour in a design review session for a new service or pairing with a junior engineer. Lunch is usually a quick affair at his desk while browsing Hacker News. The afternoon could involve more coding, investigating performance bottlenecks, or preparing notes for the next AI tooling review. He aims to wrap up by 5:30 PM, usually fitting in a short workout or a walk before starting dinner.

Lifestyle

Moses lives a structured but not rigid life in Seattle. His days are typically bookended by coding and technical reading. He prioritizes his health, often opting for a run along the waterfront or a cycling commute to clear his head. Financially, he's disciplined, saving a significant portion of his income while enjoying occasional splurges on high-quality coffee and electronics. Socially, he prefers smaller, focused gatherings with like-minded individuals over large parties, valuing deep conversations and shared technical interests.

Work life

As a Staff Backend Engineer on the platform team, Moses is deeply involved in ensuring the scalability, reliability, and efficiency of the company's core services. His days are a mix of deep work coding, architectural design discussions, and code reviews. He collaborates closely with a small, dedicated team, often debating the merits of different approaches to complex problems. The pressure to maintain high uptime and performance is constant, driving his interest in new tools and techniques that can improve developer productivity and system robustness.

Relationships

Moses maintains a close-knit circle of friends, mostly former university colleagues and current workmates with shared technical passions. He has a good relationship with his parents, who live on the East Coast, and calls them weekly. His immediate work team is his primary social and intellectual circle during the week, influencing his technical decisions and professional development.

How they decide

Moses is a highly research-driven decision-maker, especially concerning technical tools. He meticulously compares options, often building small proof-of-concepts and gathering empirical data. He values peer input and internal team consensus but ultimately relies on his own thorough analysis and alignment with long-term technical strategy.

How they sound

Speaks in a measured, clear cadence. Tends to use precise technical terminology without being overly jargonistic. Avoids hyperbole or overly casual slang. Can sound thoughtful and slightly reserved when discussing complex ideas, but his enthusiasm surfaces when talking about elegant solutions or novel technologies. His tone is generally professional and earnest.

Personality traits

  • Analytical
  • Methodical
  • Curious
  • Detail-oriented
  • Pragmatic
  • Patient
  • Independent
  • Systematic

Goals

  • Become a recognized expert in distributed systems architecture
  • Mentor junior engineers on best practices
  • Contribute to an open-source project in his domain
  • Achieve a better work-life balance without sacrificing career growth
  • Develop a deeper understanding of AI's practical applications in backend development

Problems & frictions

  • Managing technical debt in a rapidly evolving codebase
  • The constant need to evaluate and integrate new developer tools without disrupting existing workflows
  • Finding dedicated blocks of uninterrupted time for complex problem-solving
  • Onboarding new team members effectively to a complex platform architecture
  • Keeping up with the sheer volume of emerging AI technologies and their potential impact

Values

  • reliability
  • technical depth
  • peer learning
  • efficiency
  • continuous improvement

Interests

  • AI coding assistants
  • system design
  • developer tooling
  • distributed systems
  • performance optimization

Media habits

  • Reads Hacker News daily
  • Follows key figures in AI/ML on X (formerly Twitter)
  • Listens to tech podcasts during commutes
  • Subscribes to technical newsletters
  • Watches YouTube deep dives on system architecture

Questions & answers

Moses Bernier’s public research answers, newest questions first. Up to 10 per page.

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

    This month is already quite packed with a few critical system upgrades and preparing for our quarterly review. My team's AI tooling evaluation is ongoing, and I'm documenting my findings on Claude Code and Cursor for that. While 'learning by doing' sounds promising, the page doesn't clearly outline a specific subscription cost or tiered structure, making it difficult to assess value. I'd need to see a clear pricing model before committing any budget. For now, I'm prioritizing structured, internal evaluations. I wouldn't pay for this this month.
    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.