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

Gregg Lakin

Gregg Lakin

Senior backend engineer on a small SaaS product team

Full-depth AI personas

Why this persona fits the audience

Works on a 6-person engineering team at a B2B SaaS company in San Francisco. Uses PostgreSQL every day for debugging API issues, checking migrations, and editing staging data. Keeps DBeaver and psql open alongside the code editor and occasionally exports query results for teammates.

  • Age: 31
  • Location: San Francisco, CA, US
  • Occupation: Senior Backend Engineer
  • Income: $185k
  • Education: B.S. in Computer Science
  • Company size: Small (under 50 employees)
  • Years in role: 4
“The elegance isn't in the complexity, but in finding the simplest, most robust solution to a hard problem.”

Born and raised in a quiet suburban town in Ohio, Gregg developed an early fascination with how things worked, often taking apart electronics to understand their inner workings. This curiosity naturally led him to computer science in college, where he excelled, particularly in systems programming and database courses. He earned a B.S. in Computer Science from a reputable state university. After graduating, he joined a mid-sized tech company in Austin, Texas, where he honed his backend skills for three years, gaining exposure to various database technologies and distributed systems concepts. Seeking the vibrant tech scene and more challenging roles, he relocated to San Francisco about four years ago. He joined his current B2B SaaS company shortly after, drawn by the prospect of working on a core product with a small, agile team where his contributions would have a tangible impact. Gregg lives a life structured by routine and a pursuit of mastery, whether in his professional domain or personal hobbies. His income allows for comfort and investment in quality tools, but he remains pragmatic and averse to unnecessary luxury. He views time as a valuable, finite resource, which he allocates deliberately between demanding work, focused personal development, and essential physical and mental well-being activities. His approach to life is characterized by a methodical, problem-solving mindset, always seeking to understand, improve, and build robust systems, both in code and in his own life.

Background & daily life

A day in their life

Gregg's weekday typically starts around 7:00 AM with a double espresso and a quick scan of Hacker News. He heads out for a 45-minute trail run in Golden Gate Park before showering and preparing for work. By 9:00 AM, he’s logged in, reviewing Slack messages and planning his day. The morning is often spent tackling a complex backend task, perhaps optimizing a particularly slow API endpoint or working on a new database migration script. Lunch is usually a quick, healthy meal at his desk while catching up on industry blogs. The afternoon involves a team stand-up, pairing with a junior engineer to debug an issue, and more coding. He might spend 30-60 minutes digging into PostgreSQL logs and running queries in DBeaver to diagnose a production anomaly. He logs off around 5:30 PM, often followed by preparing dinner or working on a personal side project.

Lifestyle

Gregg lives in a modest one-bedroom apartment in the Outer Sunset district, valuing its proximity to Golden Gate Park for trail runs. His evenings often revolve around perfecting his home espresso setup, a ritual that mirrors his meticulous approach to coding. He's not a big spender on material goods, preferring to invest in experiences and high-quality tools that enhance his hobbies or work. Weekends might involve a long trail run, followed by quiet evenings experimenting with new coffee beans or diving into a complex open-source project. Social life is limited to a few close friends, often centered around shared technical interests or outdoor activities.

Work life

As a senior backend engineer on a small team, Gregg’s days are a blend of deep coding, collaborative problem-solving, and urgent bug fixes. He's deeply involved in the architecture and maintenance of their B2B SaaS product, particularly its PostgreSQL database layer. This means frequent use of DBeaver and psql for diagnostics, schema management, and data manipulation on staging environments. He values clear documentation and well-defined tickets, as smooth handoffs are crucial in their lean team structure. The pressure is on to ensure system stability and performance, especially as the product scales.

Relationships

Gregg maintains a close relationship with his parents, who live back east, via weekly video calls. His primary social circle consists of about five friends, many met through university or previous tech jobs, who share his passion for running or backend development. He has a cordial, professional relationship with his six-person team, relying on clear communication but not deep personal bonds with most. His influence is primarily through technical expertise and steady, reliable contributions.

How they decide

Gregg is a research-heavy decision-maker, especially for anything technical. He weighs evidence, considers edge cases, and prefers to understand the underlying mechanics before committing. For workflow improvements or tool adoption, he values empirical data and successful precedents. He’s generally cautious, avoiding impulsive choices and seeking consensus or at least clear rationale when collaborating.

How they sound

Speaks with a clear, even cadence, avoiding excessive slang or jargon unless discussing technical specifics with peers. His tone is generally calm and measured, even when discussing complex problems. He tends to use precise language and may pause to formulate his thoughts carefully. He avoids hyperbole and focuses on factual descriptions.

Personality traits

  • methodical
  • detail-oriented
  • patient
  • observant
  • persistent
  • pragmatic
  • independent
  • analytical

Goals

  • Achieve principal engineer status within his company
  • Contribute significantly to a major open-source project
  • Run a sub-3-hour marathon
  • Achieve perfect latte art consistently
  • Mentor junior engineers effectively

Problems & frictions

  • Intermittent database performance bottlenecks that are hard to pinpoint
  • Balancing urgent feature requests with essential refactoring work
  • Technical debt accumulation in legacy parts of the codebase
  • Communicating complex technical issues to non-technical stakeholders
  • The constant need to stay updated with rapidly evolving technologies

Values

  • reliability
  • low-friction workflows
  • clean handoffs
  • technical excellence
  • efficiency

Interests

  • distributed systems
  • trail running
  • home espresso
  • backend architecture
  • performance optimization

Media habits

  • Reads Hacker News daily
  • Subscribes to backend engineering newsletters
  • Listens to technical podcasts during commutes
  • Follows key figures in distributed systems on Twitter
  • Occasional Reddit browsing (r/programming, r/sysadmin)

Questions & answers

Gregg Lakin’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Data Peek (https://www.datapeek.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).

    My current workflow for debugging API issues and checking migrations involves keeping DBeaver and psql open alongside my code editor. I'd consider trying Data Peek, especially if it offers a faster, more integrated experience than my current setup. The primary hesitation would be the learning curve and the time investment to integrate it into my daily routine, which is already quite structured. If it genuinely speeds up my debugging and data exploration without introducing significant overhead, I'd be willing to pay $10 per month for a Pro license to use it commercially.
    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.