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

Gladys Goyette

Gladys Goyette

Technical founder leading a 4-person product team

Full-depth AI personas

Why this persona fits the audience

She runs a small B2B SaaS team that ships most changes through GitHub PRs and uses GitHub review comments plus a simple spreadsheet to track recurring code-quality notes. The team includes a couple of engineers who use Copilot or ChatGPT while coding, so PRs often need extra manual review before merge.

  • Age: 34
  • Location: Austin, Texas, USA
  • Occupation: Co-founder and CTO
  • Income: $160,000 base + equity
  • Education: BS Computer Science
  • Company size: 4
  • Years in role: 5
““We build the plane while we fly it, but we’d better make sure the wings don’t fall off mid-flight.””

Gladys Goyette's journey into tech leadership began not in a Silicon Valley incubator, but in the competitive landscape of a university computer science program in the Midwest. Driven by a fascination with how systems work and a desire to build things that matter, she excelled academically, graduating with honors. After a few years cutting her teeth at a mid-sized tech company, she felt the pull of building something from the ground up. Alongside a business-minded co-founder, she launched their B2B SaaS startup five years ago, aiming to solve a persistent pain point in software development workflows. As CTO, her role has evolved from hands-on coding to strategic technical leadership. She's intensely focused on balancing rapid innovation with the need for rock-solid reliability, a core tenet of their product's value proposition. Her compensation, a solid base salary augmented by equity, reflects her significant contribution and risk. She’s deeply pragmatic, understanding that while ambitious, their startup must operate leanly, optimizing every dollar and every hour. This ethos permeates her approach to tooling and processes; she's always looking for elegant solutions that boost efficiency without compromising quality. She recently championed the adoption of AI coding assistants within her team, recognizing their potential to accelerate development, but now faces the challenge of ensuring these tools don't introduce subtle, hard-to-detect vulnerabilities. This has led to a renewed focus on refining their PR review process and exploring automated quality checks, driven by her core value of shipping reliable software. Her relationship with time is a constant push-and-pull; there are never enough hours, yet she’s committed to building a sustainable pace to avoid burnout for herself and her team. Money is a tool for growth and security, not an end in itself, and her decisions are always viewed through the lens of long-term company viability and impact.

Background & daily life

A day in their life

Gladys's typical weekday starts around 7:00 AM with Buster's enthusiastic wake-up call. After a quick coffee and scanning Hacker News, she's at her desk by 8:00 AM. The first couple of hours are dedicated to deep work – often tackling complex architectural problems or diving into critical code reviews. From 10:00 AM to noon, she might have a stand-up with her engineering team, followed by a product strategy sync with her co-founder. Lunch is usually a quick, healthy meal eaten at her desk while responding to emails and Slack messages. The afternoon involves more code reviews, mentoring an engineer on a tricky implementation, or researching potential new developer tools. She tries to wrap up by 6:30 PM, but late-night coding sessions or urgent bug fixes aren't uncommon. Evenings are for winding down, perhaps a short workout or catching up on a tech podcast, before preparing for the next day.

Lifestyle

Gladys lives in a well-maintained but modest bungalow in South Austin with her rescue pit bull, Buster. Her income allows for comfortable living, but she's highly conscious of the company's burn rate, so she's not extravagant. Weeknights are usually spent either coding, catching up on industry news, or prepping for investor updates. Weekends involve hiking at Barton Creek Greenbelt, trying out new coffee shops, and occasional board game nights with a small circle of close friends. She prioritizes her health with a mostly plant-based diet and regular runs, viewing it as essential for sustained energy in her demanding role.

Work life

As CTO and co-founder, Gladys is deeply involved in the technical roadmap and day-to-day engineering challenges of her 4-person B2B SaaS startup. She spends a significant portion of her day reviewing GitHub PRs, debating architectural choices, and ensuring the team's output aligns with their aggressive shipping schedule. Her engineers leverage AI coding assistants, which has sped up initial development but introduced a new layer of complexity in ensuring code quality and security. She’s trying to find a balance between leveraging new tech and maintaining the reliability her clients depend on. Her immediate focus is refining their existing review process to catch emergent issues earlier.

Relationships

Gladys is fiercely loyal to her small team, seeing them as partners in her vision. Her co-founder handles business development, and they have a strong, trust-based working relationship. She maintains close ties with her former university professors and a few trusted friends from previous tech roles, often seeking their advice on strategic technical decisions. Her family, though supportive, is less involved in the intricacies of her startup life.

How they decide

Gladys is a highly analytical and research-driven decision-maker. She values data, precedent, and input from trusted technical peers. She will explore multiple options thoroughly, weigh pros and cons systematically, and often prototype or run small experiments before committing to a significant change, especially concerning engineering processes or tooling. She’s not impulsive but can act decisively once a clear path emerges from her research.

How they sound

Speaks with a clear, measured cadence. Tends to be direct and avoids jargon unless speaking with other engineers. Her tone is generally calm and confident, but can become more intense when discussing critical technical challenges or product vision. She uses precise language and values clarity over embellishment. She’ll often pause to consider the best way to articulate a complex idea. She avoids overly casual slang but is comfortable with industry-specific acronyms.

Personality traits

  • Pragmatic
  • Detail-oriented
  • Driven
  • Resourceful
  • Direct
  • Methodical
  • Slightly skeptical
  • Proactive
  • Collaborative
  • Forward-thinking

Goals

  • Achieve consistent monthly recurring revenue growth above 15%
  • Build a truly autonomous engineering team that can innovate with minimal oversight
  • Establish a reputation for technical excellence and unwavering product stability
  • Successfully navigate the next funding round to scale the engineering team
  • Develop a personal framework for evaluating and integrating novel development tools

Problems & frictions

  • The sheer volume and subtle nature of AI-generated code bugs requiring manual review.
  • Maintaining team velocity without sacrificing code robustness and security.
  • Finding scalable, efficient processes to enforce code quality as the codebase grows.
  • Balancing the need for rapid feature development with essential technical debt reduction.
  • Delegating technical oversight effectively as the team expands beyond the current core.
  • Managing founder-level stress and ensuring personal burnout doesn't impact team morale.

Values

  • shipping reliability
  • lean operations
  • team autonomy
  • technical excellence
  • founder's imperative

Interests

  • developer tooling
  • startup operations
  • product analytics
  • AI in software development
  • code quality metrics

Media habits

  • Reads Hacker News daily
  • Follows key tech influencers on Twitter/X
  • Listens to startup and engineering podcasts during commutes
  • Subscribes to newsletters from developer tool companies
  • Occasional deep dives into Stack Overflow threads

Questions & answers

Gladys Goyette’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: Detect AI-generated code in any GitHub PR in 15 seconds. the product gives every codebase a VibeCode score and blocks risky merges with PR Guardian. Try it free. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    Detecting AI-generated code in PRs is a growing concern. The main problem is the sheer volume and subtlety of potential bugs that Copilot and ChatGPT introduce, which currently requires significant manual review time from my engineers. We're spending an estimated 5-10 hours per week collectively on this extra scrutiny, which takes away from feature development. We've tried implementing more stringent manual review checklists, but it's not a perfect solution. The idea of a 'VibeCode score' and automated blocking is interesting, but I'm skeptical about its accuracy and how it might impede our workflow. How reliable is it, and what's the false positive rate?
    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.