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

Maryann Rogahn

Maryann Rogahn

Engineering director overseeing reliability

Full-depth AI personas

Why this persona fits the audience

Directs engineering for a 120-person healthcare SaaS in the US and reviews every major outage summary. A 3-person reliability group handles on-call rotations, incident timelines, and follow-up actions across Slack, Jira, and Datadog, with quarterly reporting to leadership.

  • Age: 45
  • Location: New Jersey, USA
  • Occupation: Director of Engineering
  • Income: $220k-$280k total compensation
  • Education: B.S. Computer Engineering
  • Company size: 120
  • Years in role: 7
“The goal isn't just to fix the fire; it's to understand why it started and reinforce the walls so it never happens again.”

Maryann Rogahn's journey into engineering leadership was driven by a desire for order and a deep-seated belief in the importance of robust systems, especially in critical sectors like healthcare. Growing up in a middle-class family in Pennsylvania, she was always the one taking things apart to see how they worked. Her Bachelor's in Computer Engineering from Penn State provided a solid theoretical foundation, but it was her early career roles in quality assurance and then software development that exposed her to the messy reality of complex systems under pressure. She joined her current company seven years ago as a senior engineer, quickly rising through the ranks due to her meticulous approach to problem-solving and her ability to communicate technical issues effectively. She took on the Director of Engineering role four years ago, initially focusing on platform development, but her knack for identifying systemic weaknesses and her calm demeanor during crises naturally led her to prioritize and eventually formalize the reliability function. She lives by the principle that 'good enough' is rarely good enough when patient outcomes are on the line. Her income affords her a comfortable lifestyle, but her spending habits are pragmatic; she prioritizes savings and investments over conspicuous consumption, viewing financial security as another form of operational control. Time is her most precious commodity, and she fiercely guards it, optimizing her schedule to maximize impact and minimize wasted effort, a philosophy that extends from her professional life to her carefully managed home routines. She's currently wrestling with how to scale her reliability group effectively without compromising the depth of their analysis, a challenge that occupies a significant portion of her strategic thinking.

Background & daily life

A day in their life

Maryann's day typically begins at 5:30 AM with a workout, followed by reviewing urgent alerts or overnight system performance summaries before her family wakes. After a quick breakfast and ensuring her kids are ready for school, she commutes to the office, listening to a leadership podcast. Her workday is a mix of scheduled meetings – stand-ups with her reliability team, planning sessions with product managers, one-on-ones with her direct reports, and strategy discussions with VPs – and focused work periods. She dedicates time to reviewing incident reports, analyzing performance dashboards, and preparing for quarterly leadership updates. Lunch is often a working lunch, and she aims to leave by 6:00 PM to make it home for family dinner, though late-night alerts can sometimes disrupt this.

Lifestyle

Maryann lives in a suburban home in New Jersey with her husband, a software architect, and their two teenage children. Her days are packed, balancing professional demands with family life. Weekends often involve chauffeuring kids to sports or extracurriculars, but she carves out time for reading industry journals or reviewing personal finance spreadsheets. She prioritizes her health with a consistent morning gym routine and meal prepping on Sundays. While financially comfortable, she's mindful of long-term savings and her children's college funds, preferring practical investments over speculative ones.

Work life

As Director of Engineering for a rapidly growing healthcare SaaS company, Maryann is deeply immersed in ensuring system reliability. Her primary focus is on the 120-person engineering team, but her direct oversight extends to the critical 3-person reliability group. She reviews every major outage summary, scrutinizing incident timelines and post-mortems for actionable improvements. Her team uses Slack for immediate communication, Jira for tracking incidents and follow-ups, and Datadog for monitoring. Quarterly reports to leadership are a significant undertaking, requiring clear, data-backed presentations on system performance and reliability metrics.

Relationships

Maryann's closest professional confidante is her husband, who offers a sympathetic ear for her work challenges and often provides a valuable engineering perspective. She maintains a collegial but professional relationship with her direct reports and has a good working rapport with other department heads. Her influence stems from her demonstrated competence and calm, data-driven approach, rather than overt charisma.

How they decide

Maryann is highly research-driven and data-focused. She meticulously gathers information, consults relevant metrics, and often seeks input from her direct team before making significant technical or strategic decisions. She values evidence and prefers solutions with demonstrable, measurable outcomes, leaning towards established best practices over unproven trends.

How they sound

Maryann speaks with a clear, measured cadence, avoiding jargon unless speaking to a technical audience. Her tone is professional and earnest, often punctuated by thoughtful pauses as she formulates her points. She uses precise language and avoids hyperbole, preferring factual statements. When discussing sensitive topics like patient safety or system failures, her voice becomes more serious and focused. She rarely uses slang and maintains a generally formal but approachable demeanor.

Personality traits

  • meticulous
  • proactive
  • detail-oriented
  • methodical
  • calm under pressure
  • decisive
  • organized
  • diligent
  • systems thinker
  • results-driven

Goals

  • Achieve zero critical patient data breaches within the next two years.
  • Develop a robust internal training program for reliability engineering.
  • Successfully scale the engineering team by 20% while maintaining system stability.
  • Foster a culture of proactive problem-solving and ownership across all engineering disciplines.
  • Continue professional growth in leadership and strategic technology planning.

Problems & frictions

  • Balancing the demands of rapid feature development with the non-negotiable need for system stability.
  • Ensuring comprehensive post-incident analysis that leads to systemic, not just superficial, fixes.
  • Attracting and retaining top-tier reliability engineering talent in a competitive market.
  • Managing technical debt that accumulates from past rapid growth phases.
  • Communicating complex reliability challenges and their impact to non-technical stakeholders.

Values

  • patient safety
  • operational control
  • measurable outcomes
  • systemic integrity
  • accountability

Interests

  • health tech
  • leadership development
  • workflow automation
  • system resilience
  • process optimization

Media habits

  • Reads industry newsletters (e.g., The Pragmatic Engineer)
  • Listens to leadership and tech podcasts during commute
  • Follows key SRE and engineering blogs on LinkedIn
  • Occasional Twitter browsing for tech news

Questions & answers

Maryann Rogahn’s public research answers, newest questions first. Up to 10 per page.

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

    My main concern with adopting a new tool like Sherlocks.ai this month would be integrating it into our current workflow without disrupting our existing processes. Today, my reliability group handles incident analysis manually, meticulously documenting timelines and root causes in Jira after each major event. We also rely heavily on Datadog for monitoring. While the promise of AI-driven root cause analysis is appealing, especially for reducing MTTR, I need to be confident it truly complements our existing stack and doesn't introduce more complexity or require extensive re-tooling. The ability to integrate seamlessly with Datadog and Slack, as mentioned, is a positive point. I would be willing to pay up to $500 per month for a solution that demonstrably improves our incident response times and provides actionable insights without significant overhead.
    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.