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

Luan Kurnicki

Luan Kurnicki

Engineering manager at a distributed SaaS company

Full-depth AI personas

Why this persona fits the audience

Runs a 6-engineer squad from Berlin and is responsible for the team's monthly ship summary. They usually collect completed tickets from Jira, cross-check them in a spreadsheet, and keep to conservative tooling choices because release reporting is only one part of their role.

  • Age: 44
  • Location: Berlin, Germany
  • Occupation: Engineering manager
  • Income: €92k
  • Education: Bachelor's degree
  • Company size: Mid-sized (200-500 employees)
  • Years in role: 5
“The most elegant solution is often the one that simply works, reliably, without demanding constant attention.”

Luan Kurnicki, 44, is an Engineering Manager at a mid-sized, distributed SaaS company, based in Berlin, Germany. Holding a Bachelor's degree in Computer Science, he has dedicated the last five years to managing a team of six engineers, fostering their growth while ensuring the company's product roadmap stays on track. His professional ethos is deeply rooted in reliability and technical rigor; he believes that robust systems are built on a foundation of meticulous planning and execution. This philosophy heavily influences his approach to his most recurring, and often time-consuming, responsibility: the monthly ship summary. Luan's current process involves manually collecting completed tickets from Jira, meticulously cross-checking them in a company-sanctioned spreadsheet, and then compiling this into a report. He consciously opts for conservative tooling choices for this and similar administrative tasks, prioritizing stability and low-friction integration over the allure of cutting-edge, potentially disruptive, software. This pragmatic stance is a direct consequence of his role's multifaceted nature; release reporting is just one piece of a larger puzzle that includes team mentorship, performance management, and strategic alignment with broader company objectives. His income of €92k reflects his experience and the responsibilities he carries. Luan is not driven by status or the accumulation of wealth for its own sake; instead, he values financial security that allows for thoughtful investment in his passions and a comfortable, predictable lifestyle. He sees time as a finite, valuable resource, and his decisions, both professional and personal, are often guided by a desire to optimize its use, minimizing wasted effort on inefficient processes. He recently pushed back on a proposal to integrate a flashy new project management tool, arguing that the learning curve and potential for disruption outweighed the promised benefits for a task his current, albeit manual, system handles adequately. His focus remains on ensuring his team can ship code predictably and that the reporting accurately reflects their hard work, without introducing unnecessary complexity or risk.

Background & daily life

A day in their life

Luan's typical weekday begins around 6:30 AM with a run, followed by coffee and a review of overnight alerts or urgent messages. His workday officially starts at 9:00 AM with a daily stand-up for his team, where he listens intently to updates and blockers. The morning is often filled with 1:1 meetings with his engineers, code review sessions, and planning for upcoming sprints. Lunch is usually a quick affair, often at his desk while catching up on industry news. Afternoons are dedicated to cross-functional meetings, architectural discussions, and, crucially, the meticulous work of gathering data for the monthly ship summary – pulling ticket statuses from Jira, cross-referencing details in a shared spreadsheet, and ensuring accuracy before finalization. He tries to wrap up by 6:00 PM, leaving evenings for personal pursuits.

Lifestyle

Luan lives in a comfortable, if slightly cluttered, Altbau apartment in Prenzlauer Berg with his partner and their cat. His routine is structured: early morning runs along the Spree, followed by a strong coffee and a quick scan of tech news before diving into work. Evenings are often spent tinkering with his home network setup, exploring new open-source router firmware, or losing himself in a complex sci-fi novel. He's not one for lavish spending, preferring to invest in quality tools and experiences, and his social life revolves around a small circle of close friends, often meeting for board game nights or quiet dinners rather than loud parties. He values his downtime immensely, seeing it as essential for recharging his analytical mind.

Work life

As an Engineering Manager, Luan navigates the complexities of leading a distributed team of six engineers. His primary focus is ensuring predictable delivery and maintaining high standards of code quality. The monthly ship summary is a recurring task that demands meticulous attention to detail, often involving manual collation of Jira tickets into a spreadsheet. He's cautious about adopting new tools, prioritizing stability and ease of integration over cutting-edge features, especially for reporting functions. This pragmatic approach stems from the understanding that release reporting is just one facet of his broader responsibilities, which include team mentorship, performance reviews, and strategic planning. He often finds himself mediating between the desire for innovation and the need for operational consistency.

Relationships

Luan maintains strong professional relationships with his direct reports, valuing their technical input and fostering an environment of mutual respect. His partner, a graphic designer, provides a creative counterpoint to his analytical world and is his primary confidante. He has a few long-standing friendships from university, mostly with individuals in technical fields, who understand his work pressures and share similar interests in technology and strategy games.

How they decide

Luan is a cautious and research-oriented decision-maker. He prefers to gather data, evaluate multiple options, and consider long-term implications before committing. He values proven solutions and is wary of hype, often seeking out peer reviews or case studies from similar organizations. When it comes to tools, he prioritizes reliability and integration with existing systems, often opting for established, well-supported solutions over newer, unproven ones.

How they sound

Speaks with a measured cadence, often pausing to formulate his thoughts precisely. His tone is generally calm and professional, avoiding overly casual slang or excessive jargon unless discussing technical specifics with peers. He tends to use clear, direct language and is not prone to hyperbole. When discussing challenges, he focuses on process and system improvements rather than blaming individuals. He might occasionally use a German idiom if speaking informally with someone he knows well.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • reserved
  • dependable
  • analytical
  • patient
  • systematic

Goals

  • Achieve a more streamlined and automated release reporting process for his team.
  • Mentor junior engineers to foster technical growth and autonomy.
  • Contribute meaningfully to an open-source project he uses regularly.
  • Maintain a healthy work-life balance without sacrificing team performance.
  • Develop a robust and secure home lab environment.

Problems & frictions

  • The manual effort involved in compiling the monthly ship summary is time-consuming and prone to human error.
  • Balancing the team's desire for adopting newer technologies with the company's need for stability and supportability.
  • Ensuring consistent communication and collaboration across a geographically distributed team.
  • Finding sufficient time for deep technical work amidst managerial duties.
  • The constant pressure to deliver features while also maintaining existing systems.

Values

  • reliability
  • low-friction processes
  • accountability
  • technical rigor
  • predictability

Interests

  • open-source software
  • running
  • home networking
  • sci-fi
  • board games

Media habits

  • Reads tech blogs (Hacker News, LWN.net)
  • Listens to podcasts during commute (e.g., 'This Week in Tech', 'Syntax')
  • Follows key figures on Mastodon/X
  • Watches YouTube for technical deep dives
  • Occasional Reddit browsing (r/sysadmin, r/programming)

Questions & answers

Luan Kurnicki’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at TicketPoster (https://ticketposter.com/): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    The idea of turning Jira tickets into a polished A2 poster is interesting, especially for our monthly ship summaries. It could make those reports more tangible for the team. The pricing of 2€ per final A2 PDF sounds reasonable for a single output, but I would need to see how much effort it actually saves compared to my current spreadsheet process. If it were a subscription, say for unlimited reports, I'd consider up to $15 per month, provided it integrated smoothly and saved significant manual work. However, if it's just a one-off purchase per poster, then $10 for the PDF would be my absolute limit before I'd consider it not worth the effort.
    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.