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

Lyam Gerritsen

Lyam Gerritsen

Founding engineer at an early-stage startup

Full-depth AI personas

Why this persona fits the audience

In a 2-founder, 1-engineer startup, he handles product implementation and feedback routing, pulling issues from Slack, issue trackers, and customer calls into Linear labels. He is technical enough to automate pieces, but the team still reviews the summaries together.

  • Age: 27
  • Location: Amsterdam, Netherlands
  • Occupation: Founding engineer
  • Income: €78k gross
  • Education: Bachelor's degree in software engineering
  • Company size: 3
  • Years in role: 2
“The most elegant solution is often the one that just works, silently and efficiently, allowing everything else to fall into place.”

Born and raised in Groningen, Lyam developed an early fascination with how things worked, often taking apart electronics to understand their inner mechanisms. This curiosity naturally led him to software engineering. After completing his Bachelor's degree at the University of Twente, he worked for a couple of years at a well-established tech company in Utrecht. However, the structured environment felt limiting, and he craved the agility and direct impact of a startup. Two years ago, he joined forces with two friends to found their current venture, pooling their savings and conviction to build something from the ground up. Lyam's role as the founding engineer is all-encompassing; he architected the initial product, built the core infrastructure, and continues to be the primary force behind its technical development. His approach is characterized by a deep respect for technical elegance and a relentless pursuit of speed, ensuring they can iterate rapidly based on market feedback. He views every piece of code as an opportunity to optimize, automate, and build leverage for the future. His income of €78k gross is comfortable for Amsterdam, but a significant portion is consciously allocated towards savings and potential future equity gains, reflecting his long-term perspective on the startup's success. He lives a relatively frugal but comfortable life, prioritizing experiences and professional growth over material possessions. His current focus is on building a scalable foundation that can support rapid user growth, a task that occupies most of his waking hours and fuels his drive.

Background & daily life

A day in their life

Lyam's typical weekday begins around 7:00 AM with a strong coffee and a quick scan of Hacker News. He's usually at his standing desk by 7:30 AM, tackling the most complex coding tasks before the day's meetings begin. Around 9:00 AM, he syncs with the founders, discussing priorities and reviewing any critical issues that surfaced overnight. The rest of his morning is a mix of coding, responding to urgent Slack messages, and pulling feedback from various sources into Linear. Lunch is often a quick sandwich eaten at his desk while reviewing pull requests. Afternoons involve more coding, occasional customer calls to gather context, and working on infrastructure automation scripts, culminating in a brief team review of the day's synthesized feedback before he signs off around 6:30 PM.

Lifestyle

Lyam shares an apartment in Oud-West with a friend from university, enjoying the vibrant neighborhood but often prioritizing work over extensive social outings during the week. Weekends might involve catching up with friends over a beer at a local 'bruin café' or exploring the city's cycling paths. He's mindful of his finances, saving a portion of his income for potential future investments or travel, but isn't overly restrictive. His routine is usually structured, with early mornings often dedicated to deep work before the startup's main communication channels become too active.

Work life

As the sole engineer in a nascent startup, Lyam is deeply embedded in the entire product lifecycle. His days are a constant juggle between writing core features, debugging, and managing the influx of user feedback. He meticulously processes feedback from Slack channels, GitHub issues, and direct customer calls, translating it into actionable tasks within Linear. While he enjoys automating repetitive tasks, the team’s shared understanding of customer needs means manual review of synthesized feedback is still a critical step. The pressure to iterate quickly is palpable, but balanced by a desire to build robust, well-architected solutions.

Relationships

Lyam maintains close ties with his two co-founders, with whom he shares a deep professional respect and a common vision. His friendships tend to be with fellow tech professionals or former university classmates, people who understand the demands of his career. Family remains supportive, though they don't fully grasp the intricacies of startup life.

How they decide

He tends to be highly analytical and research-driven when making technical decisions, weighing pros and cons meticulously. For operational or product-related choices, he relies on data and consensus with his co-founders, but ultimately trusts his technical judgment for implementation strategies.

How they sound

Speaks with a clear, measured cadence, occasionally lapsing into Dutch phrases when comfortable. His technical explanations are precise, often using analogies to illustrate complex concepts. He avoids hyperbole and overly casual slang, preferring direct and accurate language. When discussing challenges, he's factual rather than complaining.

Personality traits

  • Analytical
  • Driven
  • Pragmatic
  • Detail-oriented
  • Resourceful
  • Independent
  • Systematic
  • Focused

Goals

  • Successfully scale the startup's product to a significant user base.
  • Build a reputation as a highly competent and innovative engineer.
  • Achieve financial independence through equity in the startup.
  • Mentor junior engineers as the team grows.
  • Contribute to open-source projects in his spare time.

Problems & frictions

  • Balancing the need for rapid feature development with maintaining code quality and technical debt.
  • The sheer volume and varied sources of customer feedback can be overwhelming.
  • Feeling the constant pressure of time and limited resources inherent in an early-stage startup.
  • Ensuring the infrastructure can scale smoothly as user numbers increase.
  • Finding time for deep, uninterrupted coding amidst constant communication and context switching.

Values

  • leverage
  • speed
  • technical elegance
  • autonomy
  • impact

Interests

  • automation
  • developer tools
  • startup operations
  • scaling infrastructure
  • system design

Media habits

  • Reads Hacker News daily
  • Follows key engineering figures on Twitter/X
  • Listens to tech podcasts during commutes
  • Skims through technical blogs
  • Watches YouTube tutorials for specific libraries

Questions & answers

Lyam Gerritsen’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Feedback Brief (https://www.feedbackbrief.com) 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 primary concern is the sheer volume of feedback we receive and the manual effort required to synthesize it from Slack, customer calls, and issue trackers into Linear. The promise of 'Effortless Feedback Management' and 'Less Reading, More Building' is appealing. However, without knowing the pricing structure or seeing details on how it integrates with our current workflow, it's difficult to commit. We're a lean team, so budget is a consideration. If it genuinely automates the categorization and prioritization that I currently spend significant time on, I might consider it, but I'd need more transparency on costs. My current process involves manually tagging and creating issues in Linear, which is time-consuming but gives me direct control.
    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.