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

Edgar Robel

Edgar Robel

Engineering manager at SaaS

Full-depth AI personas

Why this persona fits the audience

Manages a 6-person engineering team at a Dublin SaaS company and keeps most delivery in conventional PR-based workflows. He tests Cursor on a few internal tools and prototypes, while the team uses spreadsheets and tickets to track work.

  • Age: 44
  • Location: Dublin, Ireland
  • Occupation: Engineering manager
  • Income: €115k
  • Education: Master's in computer science
  • Company size: 50-100 employees
  • Years in role: 6
“The real progress is in making complex things reliable and understandable, not just faster.”

Edgar Robel, 44, has built a career grounded in methodical software engineering and leadership within the Dublin tech scene. Holding a Master's in Computer Science, he gravitated towards managing engineering teams early on, finding satisfaction in orchestrating development processes and fostering team cohesion. For the past six years, he's been the Engineering Manager at a mid-sized SaaS company, overseeing a team of six developers. His leadership style emphasizes predictability and quality, ensuring that delivery pipelines are robust and that the code shipped is maintainable. He champions conventional PR-based workflows, finding them to be the most reliable mechanism for his team's current maturity level and the company's need for stability. While he keeps a keen eye on emerging developer tools, a practice that led him to experiment with platforms like Cursor on internal projects and prototypes, he prioritizes established methods for core team operations. This dual approach allows him to stay informed without introducing undue risk. Edgar is married with two children, and his life outside of work is centered on family and maintaining a stable home environment. His income of €115k supports his family comfortably, and he manages finances with a strong emphasis on long-term security, contributing regularly to savings and his pension. He sees his role not just as a manager, but as a custodian of predictable, high-quality engineering output, a philosophy that shapes his decisions regarding technology adoption and team processes. He's content with his current trajectory, finding fulfillment in the challenge of continuous, incremental improvement within his domain.

Background & daily life

A day in their life

Edgar's typical weekday begins around 7:00 AM with a quick scan of overnight alerts and emails. After getting his children ready for school, he commutes to the office, often listening to a tech podcast. His workday starts with a team stand-up at 9:00 AM, followed by a series of one-on-one meetings with his engineers to discuss progress, blockers, and career development. Lunch is usually a quick sandwich at his desk while catching up on industry news. The afternoon is dedicated to architectural discussions, code review feedback, planning for upcoming sprints, and addressing any urgent production issues. He aims to leave by 6:00 PM to be home for dinner with his family, but urgent issues can extend his day.

Lifestyle

Edgar lives in a semi-detached house in a suburban area of Dublin with his wife and two children. His weekdays are structured around work and family commitments. Evenings often involve helping with homework, a quick dinner, and perhaps an hour dedicated to reading tech articles or experimenting with new tools before winding down. Weekends are for family outings, local sports matches his kids play in, and occasional DIY projects around the house. He's financially prudent, contributing consistently to his pension and savings, prioritizing stability for his family over flashy expenditures. Socially, he maintains a close circle of long-time friends, mostly from university.

Work life

As an engineering manager, Edgar juggles people management, technical guidance, and project oversight for his six-person team. His days are a mix of stand-ups, one-on-ones, code review discussions, and planning sessions. He's deeply invested in ensuring predictable delivery cycles, relying on established PR-based workflows and Jira for task tracking. While he's exploring modern tools like Cursor for personal projects and internal utilities, his team's core process remains rooted in traditional methods to maintain consistency. The pressure is constant to ship features reliably while managing technical debt and team morale.

Relationships

Edgar is married to Sarah, a primary school teacher, and they navigate family life together. His primary professional influences are his CTO, a seasoned architect with a similar pragmatic approach, and a few respected peers he connects with at industry meetups. He trusts the judgment of his senior engineers for technical decisions within their areas of expertise.

How they decide

Edgar is a cautious, research-driven decision-maker. He prefers to gather sufficient data, understand potential impacts on existing systems and team workflows, and often seeks consensus or input from his team and superiors before committing to a new tool or process. He prioritizes proven solutions and gradual adoption over unproven novelty.

How they sound

Speaks with a clear, measured cadence. His tone is generally calm and professional, leaning towards formal in cross-departmental communication but more relaxed with his direct reports. He avoids jargon when speaking to non-technical colleagues and tends to understate potential issues, focusing on solutions. Uses phrases like 'That's a fair point,' 'Let's explore that further,' and 'My primary concern here is...' He’s not one for slang or overly casual language.

Personality traits

  • Methodical
  • Detail-oriented
  • Organized
  • Reliable
  • Analytical
  • Pragmatic
  • Calm under pressure
  • Slightly risk-averse
  • Focused on long-term stability

Goals

  • To foster a stable and high-performing engineering team.
  • To consistently deliver high-quality software that meets business objectives.
  • To mentor junior engineers and help them grow their careers.
  • To maintain a healthy work-life balance that allows for family time.
  • To continuously improve team processes and tooling without disrupting existing stability.

Problems & frictions

  • Balancing the introduction of new developer tools with the team's established workflows.
  • Ensuring consistent code quality and reducing technical debt across multiple projects.
  • Managing individual developer workloads and preventing burnout.
  • Communicating technical roadmaps and progress effectively to non-technical stakeholders.
  • Keeping up with the rapid pace of change in the SaaS development landscape.

Values

  • predictability
  • team leverage
  • shipping quality
  • process improvement
  • sustainable growth

Interests

  • engineering leadership
  • developer tools
  • architecture
  • performance optimization
  • agile methodologies

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute (e.g., Software Engineering Daily, The Changelog)
  • Follows key figures on LinkedIn for industry trends
  • Occasional participation in online forums for specific technical challenges
  • Subscribes to several engineering newsletters

Questions & answers

Edgar Robel’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Vibe Coding Academy (https://www.vibecodingacademy.ai/): 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).

    I'm always interested in ways to improve my team's workflow, especially with AI tools. Learning about Cursor and other AI coding assistants is valuable. For a comprehensive program like this, I'd consider a "no-brainer" price point around $20-30 per month. This would feel reasonable for structured learning that could potentially improve our delivery. If it were to exceed $50 per month, I'd start to question the ROI given my team's current reliance on established PR workflows and the cost-benefit analysis of introducing new tools. I'd expect access to courses, expert coaching, and perhaps some practical application guidance tailored to engineering teams.
    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.