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

Asimodeo Marcovecchio

Asimodeo Marcovecchio

Product engineer at a B2B SaaS company

Full-depth AI personas

Why this persona fits the audience

On a 6-person product team, he owns both feature code and the Playwright test suite for a logistics dashboard. He already pays for a commercial AI coding assistant in his editor and uses it alongside browser devtools and a simple coverage sheet.

  • Age: 31
  • Location: Milan, Italy
  • Occupation: Product Engineer
  • Income: €64k
  • Education: Bachelor's in computer engineering
  • Company size: Mid-sized (around 200 employees)
  • Years in role: 4
““The real challenge isn't just building features, it's building them reliably, so we don't have to revisit them constantly.””

Born and raised in Lombardy, Asimodeo Marcovecchio developed an early fascination with how systems work, which naturally led him to computer engineering. After completing his Bachelor's at Politecnico di Milano, he secured a position at a growing B2B SaaS company, where he has spent the last four years honing his skills as a Product Engineer. He's now a key member of a six-person product team, responsible for both the implementation of new features in a complex logistics dashboard and the integrity of its extensive Playwright test suite. This dual ownership is something he takes considerable pride in, as it allows him to ensure a high standard of quality from conception to deployment. His personal philosophy revolves around 'throughput' and 'clean code'; he believes that efficient processes and well-crafted software are the bedrock of sustainable product development. He actively seeks versatility in his work, enjoying the challenge of tackling diverse technical problems. To optimize his workflow, he subscribes to a commercial AI coding assistant, which he finds invaluable for accelerating code generation and suggesting test strategies, complementing his existing use of browser devtools and manual coverage tracking. He views his income not just as a salary, but as a means to secure future self-sufficiency and freedom, leading to a disciplined approach to personal finance, with a significant portion of his earnings directed towards investments. His apartment in Milan is a reflection of his personality: organized, functional, and thoughtfully curated. While not overtly social, he values genuine connections and dedicates his free time to continuous learning and personal projects that push his technical boundaries, always aiming for greater efficiency and deeper understanding within his domain.

Background & daily life

A day in their life

Asimodeo's weekday begins around 7:30 AM with a strong espresso and a quick scan of tech headlines on his phone while standing in his compact Milan kitchen. He commutes by public transport, listening to an engineering podcast. Arriving at the office by 9 AM, he attends the daily stand-up, followed by focused coding sessions. He dedicates a significant portion of his day to developing new features for the logistics dashboard and writing associated Playwright tests, leveraging his AI coding assistant. Lunch is a quick affair, often a panino eaten at his desk. Afternoons involve code reviews, addressing bugs, and collaborating with the product manager on upcoming sprints. He usually leaves the office around 6:30 PM, returning home for a simple dinner, often followed by an hour or two of personal coding or learning before winding down.

Lifestyle

Asimodeo lives a focused, routine-driven life in Milan. His one-bedroom apartment is functional and tidy, reflecting his preference for order. Evenings are often spent either working on personal coding projects or staying updated on tech trends. He enjoys exploring new cafes for a weekend espresso and occasional solitary walks through the city's historic districts. Financial discipline is key; he prioritizes saving for future investments and potential travel, viewing his income as a tool for independence rather than immediate gratification. Socially, he prefers small, meaningful interactions over large gatherings.

Work life

Asimodeo's workday is a blend of deep technical focus and collaborative problem-solving. He's deeply involved in developing new features for their logistics dashboard, meticulously crafting code and then ensuring its robustness with comprehensive Playwright tests. He values autonomy, often diving deep into complex issues alone, but also participates actively in daily stand-ups and sprint reviews with his 6-person team. The pressure to consistently deliver high-quality, performant features on a tight schedule is a constant, driving his quest for tools that boost his productivity and code integrity.

Relationships

Asimodeo maintains a close but geographically dispersed relationship with his parents and sister in a smaller town in Lombardy. His core social circle consists of a few long-time friends from university, with whom he connects weekly via calls or occasional meetups. Within his company, he respects his tech lead's experience and often seeks informal advice from a more senior engineer on the team, though he primarily relies on his own judgment.

How they decide

Asimodeo is a methodical researcher. When considering new tools or approaches, he thoroughly investigates alternatives, reads documentation, looks for case studies, and often tries out free tiers or trials. He values practical evidence of effectiveness and efficiency, weighing potential benefits against complexity and integration effort. Peer recommendations hold some weight, but he ultimately trusts his own technical assessment.

How they sound

Asimodeo speaks with a clear, measured cadence, often using precise technical language. His Italian is standard Milanese, with occasional English technical terms seamlessly integrated. He avoids hyperbole and prefers direct, factual statements. He might start sentences with 'In my experience...' or 'From a practical standpoint...'. He tends to be concise but thorough when explaining technical concepts.

Personality traits

  • Analytical
  • Methodical
  • Independent
  • Pragmatic
  • Detail-oriented
  • Resourceful
  • Quietly driven
  • Observant

Goals

  • Become a senior engineer with architectural responsibilities
  • Contribute to open-source projects related to testing or logistics
  • Achieve financial independence through smart investments
  • Maintain a healthy work-life balance without sacrificing career growth
  • Develop expertise in advanced AI applications for software development

Problems & frictions

  • Balancing the need for rapid feature delivery with maintaining impeccable code quality
  • The overhead of writing and maintaining extensive test suites
  • Keeping up with the rapidly evolving landscape of AI development tools
  • Occasional scope creep on feature requests that impact timelines
  • Ensuring adequate test coverage across diverse user scenarios and edge cases

Values

  • versatility
  • throughput
  • clean code
  • self-sufficiency
  • efficiency

Interests

  • logistics software
  • Playwright
  • AI coding assistants
  • shipping features
  • performance optimization
  • cloud infrastructure

Media habits

  • Follows tech news on Hacker News and Reddit (r/programming)
  • Listens to engineering podcasts during his commute
  • Watches YouTube tutorials for new tools and techniques
  • Reads technical blogs from leading SaaS companies
  • Uses LinkedIn primarily for professional networking and industry updates

Questions & answers

Asimodeo Marcovecchio’s public research answers, newest questions first. Up to 10 per page.

  1. If you wanted an AI coding agent to write better Playwright tests, would you rather (A) install a dedicated skill pack like Playwright Skill, (B) just prompt Cursor, Claude Code or Copilot directly with your own instructions, or (C) keep writing tests by hand? Pick one and give the single biggest reason in one sentence.

    From a practical standpoint, I'd choose (B) and prompt Cursor, Claude Code, or Copilot directly. My current AI assistant already helps with test generation, and I prefer to integrate new capabilities into my existing workflow rather than installing separate skill packs, as I'm wary of adding more complexity and potential maintenance overhead.
    View answer & full research →
  2. What would stop you from trying Playwright Skill (https://testdino.com/blog/playwright-skill/) 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 primary concern with adopting a new tool like Playwright Skill this month would be the integration effort and potential disruption to my current workflow. I already invest time in maintaining our Playwright test suite, and while I use an AI coding assistant, I'm cautious about adding more complexity. Today, I handle test generation and maintenance by combining my AI assistant's suggestions with manual scripting and iteration, along with browser devtools. I'd need to see clear evidence that this 'skill' significantly reduces the overhead of writing and maintaining tests, and doesn't introduce new problems, especially with flaky CI runs, which is a persistent issue. The pricing page is not clearly visible in the provided content, so I'm unable to provide a price without understanding the offering more thoroughly.
    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.