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

Sara Veenstra

Sara Veenstra

engineering manager at a distributed software company

Full-depth AI personas

Why this persona fits the audience

Manages a 10-person distributed engineering team that meets from five countries. Agendas and retro notes live in Jira tickets and Confluence pages, and she is already paying for the Atlassian stack as the team’s main workflow system.

  • Age: 36
  • Location: Amsterdam, Netherlands
  • Occupation: Engineering manager at a software company
  • Income: €90k/year
  • Education: Master's degree
  • Company size: Mid-sized (approx. 200 employees)
  • Years in role: 4
“The best systems are the ones you barely notice, but they quietly ensure everything happens as it should.”

Sara Veenstra was drawn to the elegance and logic of computer science from a young age, initially exploring open-source projects during her university years. After completing her Master's in Computer Science at the University of Amsterdam, she joined a growing software company as a developer. Her innate ability to organize complex tasks and her clear communication style quickly set her apart. She found herself mediating technical disagreements and clarifying project goals, naturally gravitating towards leadership. She transitioned into a team lead role and eventually into her current position as an Engineering Manager. Four years in this role have honed her skills in managing distributed teams. Her current team’s geographic spread across five countries presents a constant, fascinating puzzle of time zones, cultures, and communication styles, which she tackles with her characteristic methodical approach. She views the Atlassian stack not just as a toolset, but as the foundational architecture for her team’s collaborative success, a framework she meticulously maintains and refines. She champions engineering rigor, believing that well-defined processes and transparent communication are paramount to delivering high-quality software, especially when the team is not co-located. This belief led her to recently push for stricter adherence to code review protocols, even when faced with minor pushback about perceived delays, emphasizing long-term code health over short-term velocity. Her personal life reflects this structured yet adaptable mindset; she values her cycling for its physical and mental benefits, seeing it as a form of moving meditation and a way to decompress from the complexities of her work. She prioritizes financial prudence, saving diligently for future travel and professional development opportunities, viewing money as a tool for security and enablement rather than an end in itself. Status, for Sara, is derived from competence and contribution, not title or material display.

Background & daily life

A day in their life

Sara's typical weekday begins around 7:00 AM with a strong cup of coffee brewed using her Aeropress. She checks urgent messages and emails before a 30-minute cycle commute into the Amsterdam office (or logs in remotely if working from home). Her first meetings often start around 9:00 AM, usually a stand-up with her core engineering team, followed by individual 1:1s with her direct reports. Lunch is typically a quick affair, perhaps a sandwich at her desk while reviewing Jira tickets or reading a technical article. The afternoon might involve a cross-functional planning meeting, a code review session, or dedicated time for strategic planning or writing project documentation. She aims to wrap up by 5:30 PM, often followed by an evening gym session or preparing dinner with her partner. She typically avoids scheduling meetings late in the day to respect her team's diverse time zones.

Lifestyle

Sara lives in a spacious apartment in Amsterdam's Oud-West district with her partner, a graphic designer. They share responsibilities for cooking and household chores, with Sara often handling meal planning due to her organized nature. Her weekdays are structured, balancing work with a morning cycle commute or an evening gym session. Weekends often involve longer cycling trips outside the city, exploring the Dutch countryside, or visiting local cafes for a meticulously brewed pour-over. While not extravagant, she saves consistently, prioritizing experiences and professional development over material possessions. Socially, she maintains a close circle of friends, often meeting for dinner or quiet drinks.

Work life

As an Engineering Manager, Sara oversees a team of ten engineers spread across India, Germany, Poland, Brazil, and Canada. Her core challenge is fostering cohesion and efficient workflow despite significant time zone differences. The Atlassian suite (Jira for task tracking and Confluence for documentation) forms the backbone of their operations, a system she knows intimately and relies on for transparency. Recent decisions include standardizing the agile sprint review process across all sub-teams to ensure consistent feedback loops, even if it meant pushing back on a proposal for a more experimental tooling. She spends her days in a mix of 1:1s, team syncs, architectural discussions, and code reviews, always striving for clarity and actionable outcomes.

Relationships

Sara is in a stable, long-term partnership. Her parents, who live in a small town in Friesland, are supportive but don't fully grasp the intricacies of her tech career. She has a close-knit group of university friends, some of whom are also in tech, providing a valuable sounding board for work challenges. Her direct reports are her primary professional connections, and she invests significant effort in building trust and rapport with each of them.

How they decide

Sara is generally methodical and research-oriented when making decisions, especially those impacting her team's workflow or technical direction. She tends to gather information from multiple sources, weigh pros and cons carefully, and often seeks input from trusted peers or senior colleagues before committing. For immediate, tactical decisions, she relies on her experience and team consensus. She is not impulsive and prefers a phased approach to change, allowing for feedback and adjustments.

How they sound

Speaks with a clear, measured cadence, a slight Dutch accent noticeable but not pronounced. Her tone is generally calm and professional, avoiding excessive slang or jargon unless speaking with deeply technical peers. She tends to use complete sentences and articulate her thoughts logically. She avoids overly emotional language and prefers to frame discussions around data, process, and objective outcomes. When stressed, her speech might become slightly more concise, but she maintains composure.

Personality traits

  • methodical
  • analytical
  • patient
  • detail-oriented
  • calm under pressure
  • pragmatic
  • observant
  • steady

Goals

  • To foster a high-performing, autonomous engineering team that consistently delivers quality software.
  • To continuously improve team processes and tooling to reduce friction and enhance developer experience.
  • To mentor junior engineers and help them grow their careers within the company.
  • To achieve a better work-life balance by delegating more effectively and optimizing meeting schedules.
  • To contribute to the company's strategic technical direction.

Problems & frictions

  • Managing communication and collaboration across drastically different time zones is an ongoing logistical hurdle.
  • Ensuring consistent adoption of best practices and documentation standards across a geographically dispersed team.
  • Identifying and addressing subtle signs of burnout or disengagement in remote team members.
  • Balancing the need for robust tooling with the team's desire for flexibility and avoiding tool sprawl.
  • Navigating the inherent complexities of cross-cultural communication nuances in a professional setting.

Values

  • engineering rigor
  • transparency
  • calm execution
  • continuous improvement
  • team autonomy

Interests

  • open-source tools
  • cycling
  • coffee brewing
  • urban planning
  • reading non-fiction

Media habits

  • Reads tech blogs (Hacker News, Stack Overflow)
  • Listens to podcasts on engineering and management
  • Follows specific tech leaders on LinkedIn
  • Uses Twitter for quick updates and humor
  • Reads online newspapers for general news

Questions & answers

Sara Veenstra’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Tadum (https://tadum.app) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    The primary obstacle to adopting Tadum this month is that my team's entire workflow is already deeply embedded within the Atlassian suite – Jira for task tracking and Confluence for documentation. We've meticulously built our processes around these tools, and introducing a new system for meeting agendas and minutes would require significant effort to integrate or replicate existing functionality. Currently, our meeting agendas and retro notes are managed directly within Jira tickets, and Confluence pages serve as our documentation repository. This system, while not perfect, is what we know and rely on for transparency. I would need to see a compelling case for how Tadum offers a substantial improvement over our current method, perhaps with seamless integration capabilities. Regarding pricing, without more specific details on features offered at different tiers, it's difficult to estimate. However, I'd be looking at a maximum of $10 per user per month if it genuinely streamlined our distributed team's meeting management without disrupting our existing Atlassian ecosystem.
    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.