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

Jesse Kuprion

Jesse Kuprion

Engineering manager at a web agency

Full-depth AI personas

Why this persona fits the audience

Manages a 14-person web agency engineering group in Munich. Jira is the default tracker, with GitHub links and time spent captured separately for client billing, and he spends part of each week reviewing boards, priorities, and handoff notes across two delivery squads.

  • Age: 41
  • Location: Munich, Germany
  • Occupation: Engineering manager
  • Income: €92k salary
  • Education: Diplom-Informatiker equivalent
  • Company size: Approx. 30 employees total at the agency
  • Years in role: 6
“The most satisfying part of my job is seeing a complex project come together smoothly, knowing that our processes and the team's effort aligned perfectly.”

Jesse Kuprion, 41, is an Engineering Manager at a Munich-based web agency, a role he's held for six years. His journey into management was a natural progression from a senior developer role, driven by a knack for organizing workflows and a desire to foster a more structured development environment. He holds a Diplom-Informatiker equivalent, providing a strong theoretical foundation for his practical work. Jesse's professional life is characterized by a deep commitment to predictability and accountability, values that stem from his own meticulous nature and his understanding of client expectations. He manages a team of 14 engineers, overseeing their work through Jira, which serves as the central hub for task tracking. However, the agency's client-billing model necessitates a parallel system where GitHub links and precise time spent are logged separately, a process Jesse meticulously reviews weekly. He spends a significant portion of his time dissecting Jira boards, prioritizing tasks, and ensuring seamless handoffs between his two delivery squads. This constant juggling act between technical oversight, team management, and client-facing responsibilities shapes his daily reality. He recently pushed for a more standardized approach to code reviews across both squads, aiming to reduce inconsistencies and improve overall code quality, a decision met with mixed but generally positive reception from his team. His income of €92k reflects his experience and the agency's success, allowing for a comfortable lifestyle for his family. He views time as a critical resource, both for client projects and for his personal life, which he guards closely. Status is less about prestige and more about the quiet satisfaction of a well-oiled machine and reliable outcomes.

Background & daily life

A day in their life

Jesse's day typically begins around 7:00 AM with a quick check of urgent emails and Slack messages before his son wakes up. After getting his son ready for school and a brief breakfast with his wife, he commutes to the office, often listening to a tech podcast. His mornings are usually packed with stand-up meetings for his two squads, reviewing Jira boards, and addressing any immediate blockers. Lunch is often a quick affair at his desk or a short walk. Afternoons involve more in-depth work: code review sessions, planning future sprints, client calls, and one-on-one meetings with his team leads. He aims to leave by 6:00 PM to be home for dinner and family time, though late client requests can sometimes extend his day. He might squeeze in a quick bouldering session or a bike ride if time permits later in the week.

Lifestyle

Jesse lives in a comfortable apartment in Munich with his wife and young son. His weekdays are tightly scheduled, balancing work demands with family commitments. Evenings often involve helping his son with homework or preparing dinner. Weekends are a mix of active pursuits like bouldering at the local gym or long road cycling trips, interspersed with quiet time tinkering with his mechanical keyboard collection or enjoying a craft beer. He prioritizes predictable routines and values his downtime for recharging, seeing it as essential for maintaining his high level of focus during the week.

Work life

As an engineering manager, Jesse navigates the constant tension between client demands and team capacity. His primary focus is ensuring smooth project delivery for the agency's clients, which means meticulous oversight of Jira boards, sprint planning, and resource allocation across two squads. He's deeply involved in reviewing progress, identifying bottlenecks, and facilitating handoffs between developers and project managers. The need to accurately capture time spent for client billing adds a layer of administrative overhead he finds necessary but time-consuming. He works closely with a lead developer and a project manager, fostering a collaborative but results-driven environment.

Relationships

Jesse is married to Lena, a graphic designer, and they share a close bond, often discussing work challenges and family matters. His son, Leo, is a major focus of his personal life. He maintains a small circle of close friends, mostly from university and his cycling club, with whom he shares interests and occasional weekend meetups. His direct reports and the project managers he collaborates with are his primary professional network.

How they decide

Jesse approaches decisions methodically, preferring to gather all relevant information and assess potential impacts before committing. He values clear processes and data, often creating checklists or flowcharts to ensure all angles are considered. While he respects his team's input, final decisions are based on a rational evaluation of feasibility, impact, and alignment with established goals. He is not prone to impulsive choices and will often defer a decision if more clarity is needed.

How they sound

Speaks with a clear, measured cadence, using precise language. Avoids excessive slang or overly casual phrasing, even in informal settings. His tone is generally calm and professional, but can become more direct when discussing process or accountability. He tends to explain his reasoning thoroughly. He rarely uses filler words and prefers direct communication.

Personality traits

  • methodical
  • detail-oriented
  • structured
  • calm under pressure
  • pragmatic
  • diligent
  • observant
  • resourceful

Goals

  • Achieve a more predictable release cycle for client projects
  • Mentor junior developers to improve their technical and process skills
  • Maintain a healthy work-life balance without sacrificing project quality
  • Explore opportunities for the agency to adopt more standardized development practices
  • Save for a down payment on a larger family home

Problems & frictions

  • Inconsistent client requirements leading to scope creep
  • Difficulty in accurately estimating task durations for billing
  • Context switching between multiple projects and client needs
  • Onboarding new team members to established workflows
  • Technical debt accumulating on older client projects
  • Balancing urgent bug fixes with planned feature development

Values

  • predictability
  • accountability
  • process clarity
  • efficiency
  • reliability

Interests

  • bouldering
  • mechanical keyboards
  • road cycling
  • craft beer
  • reading technical blogs

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Follows key engineering leaders on LinkedIn
  • Subscribes to industry newsletters
  • Watches YouTube reviews of new tech gadgets

Questions & answers

Jesse Kuprion’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://kendo.dev (Kendo) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The initial pitch about the issue tracker living in the terminal is intriguing, especially the MCP tools. However, the "in active development" notice is a bit of a concern for a production environment; I need predictability. The claim of built-in time tracking is a definite plus, as that's a separate process for us now. To sign up, I'd need to see more concrete evidence of stability and perhaps a clear path from active development to a more robust offering. I'm also unclear on how the MCP tools integrate with our existing GitHub workflows beyond just basic sync.
    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.