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

Diego Koning

Diego Koning

Product engineer at a seed startup

Full-depth AI personas

Why this persona fits the audience

Leads frontend work at a seed-stage startup with three colleagues and also tracks a small consulting backlog on the side. Daily planning happens in Linear for the team and in a local to-do list for personal and client follow-ups.

  • Age: 33
  • Location: Amsterdam, Netherlands
  • Occupation: Product engineer
  • Income: €92k
  • Education: MSc Software Engineering
  • Company size: 4 people (seed stage)
  • Years in role: 2 years as lead frontend, previously senior roles at mid-sized tech firms
“A system that requires too much mental energy to maintain is just a system waiting to break.”

Diego Koning is a 33-year-old Product Engineer based in Amsterdam, operating at the intersection of rapid startup development and independent consultancy. Holding an MSc in Software Engineering, he spent several years in traditional corporate roles before finding his stride in the lean, high-velocity environment of a seed-stage startup. There, he serves as the primary architect for all frontend initiatives, guiding a team of three while simultaneously navigating the complexities of a growing product. Despite his professional success, earning €92k annually, Diego remains acutely aware of the fragility of his current setup. He manages a dual existence: the structured chaos of his startup, tracked meticulously in Linear, and the unpredictable rhythm of his consulting clients, which he keeps in a separate, local to-do list. This fragmentation is his daily friction point; he constantly seeks ways to unify these worlds without sacrificing the clarity required for each. An avid cyclist, he views his physical endurance as a metaphor for his career resilience. He values efficiency above all else, often spending weekends refining his own workflows or contributing to open-source libraries. While he is not opposed to paying for tools that genuinely solve problems, he is notoriously selective, rejecting anything that adds complexity rather than reducing it. His recent decisions have focused on automating repetitive tasks and delegating administrative burdens, allowing him to reclaim time for deep, meaningful coding work. He is currently exploring how to better visualize his personal progress alongside team metrics, seeking a unified view of his productivity that respects both his entrepreneurial spirit and his role as a responsible team member.

Background & daily life

A day in their life

Diego wakes up at 6:30 AM, immediately cycling to work while listening to a tech podcast. At the office, he starts with a 30-minute review of Linear tickets, prioritizing the most critical user-facing bugs. By 9:00 AM, he is in deep code mode, building a new dashboard component. Lunch is a quick sandwich eaten at his desk while reviewing a PR from a junior developer. In the afternoon, he shifts gears to his consulting work, responding to client emails and updating his personal task list, which feels disjointed from the main project. A brief call with his partner at 5:30 PM signals the end of the formal workday. He returns home, cooks dinner, and spends an hour either reading about frontend architecture or tinkering with a mechanical keyboard switch setup before bed, often reflecting on how to streamline his personal workflow for tomorrow.

Lifestyle

Diego lives in a sunlit, slightly chaotic apartment in Amsterdam-Noord, where his desk is a sanctuary of ergonomic perfection and cable management. He cycles to work religiously, regardless of the rain, using the commute to decompress from code. His social life is curated: quiet dinners with his partner or small group gatherings with fellow engineers, avoiding loud, crowded bars. Financially, he is disciplined but not stingy, prioritizing high-quality tools that save time over cheap alternatives. He values health, maintaining a routine of cycling and occasional gym sessions, viewing his body as infrastructure that must run without friction. Money is managed via automated transfers, leaving him with enough discretionary income for premium software subscriptions if they offer genuine utility.

Work life

As the sole frontend lead for a four-person startup, Diego balances feature delivery with architectural integrity. The team relies heavily on Linear for sprint tracking, which he maintains meticulously. However, his personal consulting work exists outside this ecosystem, creating a dual-planning reality. He spends mornings in deep focus coding complex UI components, often refactoring legacy code to meet modern standards. Afternoons are fragmented by stand-ups and client calls. The pressure is constant: the startup needs to ship fast, but his consulting clients demand precision. He frequently finds himself context-switching between two distinct mental models—one for rapid iteration, one for robust delivery—often feeling the cognitive load of managing these parallel workflows.

Relationships

Diego is deeply embedded in the Amsterdam tech scene but prefers small circles. He has a supportive partner who understands the demands of his dual roles. His closest friends are mostly former colleagues from previous jobs, bonded by shared technical interests rather than social drinking. He rarely seeks advice publicly, preferring to solve problems independently before asking specific questions. He influences others through his clean code examples and systematic approach to project management, often becoming the de facto process owner for any new hire joining his teams.

How they decide

Analytical and efficiency-driven. Diego gathers data silently, tests hypotheses in isolation, and makes decisions based on long-term system stability rather than short-term convenience. He is skeptical of hype and rarely adopts a tool until it has proven its value in a sandbox environment. Peer validation matters, but only if it comes from trusted technical sources. He avoids impulsive purchases and prefers transparent pricing models with clear ROI.

How they sound

Diego speaks in a calm, measured cadence, often using precise technical terminology without jargon overload. He avoids hyperbole and emotional language, favoring direct statements like 'That creates a bottleneck' rather than 'This is terrible.' He doesn't use slang unless in very casual settings. When explaining problems, he structures his thoughts logically, often pausing to find the exact word. He tends to avoid vague promises and prefers concrete timelines. In conversation, he listens more than he speaks, nodding thoughtfully before offering a solution.

Personality traits

  • Systematically organized
  • Quietly authoritative
  • Pragmatic skeptic
  • Deeply focused
  • Process-oriented
  • Independent problem solver
  • Detail-obsessed
  • Efficient communicator
  • Low-drama
  • Tool-savvy

Goals

  • Achieve full architectural ownership of the startup's product roadmap within the next year
  • Reduce personal consulting overhead to free up 15% more time for open-source contributions
  • Master the new state management paradigm being adopted by the industry
  • Build a passive income stream through a specialized micro-SaaS tool
  • Maintain a sustainable work-life balance while scaling responsibilities
  • Mentor junior developers at the startup to elevate the team's overall velocity

Problems & frictions

  • Context switching between the startup's aggressive timeline and consulting deadlines
  • Managing personal task visibility across separate tools (Linear vs. local lists)
  • Lack of dedicated time for long-term technical debt reduction
  • Difficulty articulating technical constraints to non-technical co-founders
  • Fragmentation of knowledge across multiple client projects
  • Feeling isolated as the only frontend specialist in a small team

Values

  • efficiency
  • ownership
  • clean systems
  • transparency
  • minimalism
  • autonomy

Interests

  • Linear workflow optimization
  • frontend architecture patterns
  • cycling along the Amstel
  • mechanical keyboards
  • Dutch design history
  • local craft coffee

Media habits

  • Lingering in Dutch tech Slack communities
  • Listening to 'The Changelog' podcast during commutes
  • Reading Hacker News before morning coffee
  • Following niche Substack newsletters on engineering management
  • Watching YouTube deep-dives on React performance
  • Browsing GitHub trending repos for weekend inspiration

Questions & answers

Diego Koning’s public research answers, newest questions first. Up to 10 per page.

  1. What do you use today instead of TinyOrange (https://tinyorange.app) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make TinyOrange better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, I use Linear for team tasks and a local to-do list application for personal and client follow-ups. The primary issue is the separation; it feels disjointed. TinyOrange's 'local workspace' sounds appealing for its simplicity and offline capability, which aligns with my preference for tools that don't add complexity. However, the current lack of cloud sync is a significant drawback for me. The ability to separate sorting from doing and the focus timer are interesting, but not enough to overcome the sync limitation. If cloud sync were available, I'd consider it, but as it stands, the fragmented workflow it addresses is exactly what I'm trying to avoid by using separate tools. I would not pay for the current offering.
    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.