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

Romy Baseda

Romy Baseda

Engineering manager at a fintech

Full-depth AI personas

Why this persona fits the audience

Runs sprint planning for an 8-person remote engineering team that keeps stories in Jira and estimates during video calls. The group usually shares votes manually in chat, with final points copied into Jira after the meeting.

  • Age: 41
  • Location: Berlin, Germany
  • Occupation: Engineering manager
  • Income: €118k
  • Education: Master's degree in computer science
  • Company size: Mid-sized fintech (approx. 250 employees)
  • Years in role: 5
“The most elegant solutions are often the ones that simplify complexity without introducing new problems.”

Romy Baseda, 41, is an Engineering Manager at a mid-sized fintech company headquartered in Berlin, where she has been for the past five years. Holding a Master's degree in Computer Science from the Technical University of Munich, her academic foundation is strong, emphasizing theoretical computer science and algorithms. Her career trajectory has been deliberate, moving from a software engineering role to team lead and eventually manager, driven by a desire to influence technical direction and team dynamics. She chose Berlin for its vibrant tech scene and quality of life, finding a good balance between professional ambition and personal well-being. Romy lives alone in a well-appointed apartment, a testament to her organized nature and appreciation for order. Her income of €118k allows for financial security, which she prioritizes through prudent saving and investment, reflecting her long-term outlook. She is deeply committed to technical rigor, believing that well-engineered systems are the bedrock of reliable financial services. This commitment extends to her team's processes; she actively seeks to optimize workflows, particularly the sprint planning and estimation process, which she currently finds to be a bottleneck. The current method of manual voting in chat during video calls for story points, followed by manual entry into Jira, is a prime example of a process she views as inefficient and ripe for improvement. She has recently been researching alternative tools and methodologies that could streamline this, aiming for greater accuracy and reduced overhead. Her interest in distributed systems is not just professional but also a personal fascination, driving her to stay abreast of the latest developments. She sees her role as a steward of both technical excellence and team health, navigating the complexities of remote work and agile development with a pragmatic, data-informed approach. Her decision to focus on improving sprint planning stems from a core value: minimizing process overhead to maximize engineering productivity and focus on delivering value.

Background & daily life

A day in their life

Romy's typical weekday begins around 7:00 AM with a quick check of urgent emails and Slack messages from her team in different time zones. After a light breakfast and a strong coffee, she's usually in back-to-back video calls from 9:00 AM onwards: a daily stand-up with her team, a backlog grooming session, and then the crucial sprint planning meeting. During planning, she guides the team through story point estimations, observing the manual chat voting and noting down the final consensus to update Jira later. The afternoon is often dedicated to 1:1s with her engineers, code review follow-ups, and strategic discussions with product management. She tries to wrap up by 6:00 PM, often squeezing in a short bike ride before preparing dinner.

Lifestyle

Romy's life in Berlin is structured and efficient. She lives alone in a bright, modern apartment in Prenzlauer Berg, which she meticulously keeps organized. Her weekdays are dominated by work, but she carves out time for her passions. Evenings often involve a quick, healthy meal prepared at home, followed by reading technical articles or catching up on industry news. Weekends are for longer city cycling excursions, exploring new routes through the city's parks and along the Spree, or meeting up with a small circle of close friends for coffee or a quiet dinner. She prioritizes her health with regular cycling and mindful eating, and her financial habits are conservative, focusing on long-term security.

Work life

As an Engineering Manager at a growing fintech, Romy oversees an 8-person remote team responsible for core platform services. Her days are a blend of technical oversight, people management, and process refinement. She spends significant time in Jira, grooming the backlog and ensuring stories are well-defined. Sprint planning is a key ritual, where she facilitates estimation sessions via video calls. The current process involves manual voting in chat, which she finds increasingly cumbersome. She's constantly evaluating team performance metrics and looking for ways to improve delivery speed without sacrificing quality, navigating the pressures of rapid product development and maintaining a high-performing, distributed team culture.

Relationships

Romy maintains a close but geographically dispersed relationship with her parents and younger brother, who live in a smaller town in Bavaria. Her social circle in Berlin is small but deeply trusted, consisting of a few university friends and colleagues she's known for years. She values their intellectual discussions and shared interests. Her team members are her primary professional relationships, and she invests significant effort in building trust and rapport with them, even remotely.

How they decide

Romy is a highly analytical and research-oriented decision-maker. She gathers data, weighs pros and cons meticulously, and often consults with trusted peers or technical leads before committing to a course of action. She is not impulsive and prefers to understand the long-term implications of any decision, especially those impacting team processes or technical architecture. She values evidence and demonstrable results over hype.

How they sound

Romy speaks with a clear, measured cadence, her German accent subtly present. Her tone is generally calm and professional, avoiding overly casual slang or excessive jargon unless discussing technical specifics with peers. She tends to be direct and factual, preferring to explain the 'why' behind her statements. She avoids emotional appeals or overly effusive language, focusing on logic and evidence. When discussing challenges, she's more likely to frame them as 'areas for improvement' or 'process inefficiencies' rather than complaints.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • patient
  • analytical
  • reserved
  • principled
  • observant
  • efficient

Goals

  • To foster a highly collaborative and technically excellent engineering team.
  • To contribute to the architectural evolution of the company's core platform.
  • To achieve a better work-life balance by optimizing team processes.
  • To mentor junior engineers and help them grow their careers.
  • To complete a challenging multi-day cycling tour in the Alps.

Problems & frictions

  • The current manual process for sprint planning estimations is time-consuming and prone to errors.
  • Ensuring consistent code quality and technical debt management across a remote team.
  • Balancing the need for rapid feature delivery with maintaining system stability.
  • Facilitating effective communication and collaboration in a fully remote setting.
  • Finding time for deep technical work amidst management responsibilities.

Values

  • reliability
  • technical rigor
  • low process overhead
  • team autonomy
  • data-driven decisions

Interests

  • distributed systems
  • team leadership
  • city cycling
  • agile methodologies
  • open-source contributions

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commutes
  • Follows key figures in distributed systems on Twitter
  • Subscribes to newsletters on agile practices
  • Watches technical talks on YouTube

Questions & answers

Romy Baseda’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at TasksTally (https://taskstally.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).

    This tool, TasksTally, appears to be discontinued, which is a significant drawback. If it were active and met my needs for streamlining our sprint planning – specifically, the manual chat voting and Jira updates – I'd consider it. A price around $5 to $10 per user per month would be a no-brainer for a tool that integrates seamlessly with Jira and eliminates manual data entry. Above $20 per user per month, I would likely stop considering it, especially given the current manual process is free. I'd expect real-time synchronized voting, automated Jira story point updates, and perhaps some basic historical reporting. My maximum would be $10 per month.
    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.