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

Ernesto Paucek

Ernesto Paucek

Engineering manager at a digital agency

Full-depth AI personas

Why this persona fits the audience

He manages a 3-person delivery team building client portals and membership apps in Next.js for local businesses. Their current stack uses Supabase and Stripe, and he spends part of each project standardizing auth, team access, and billing setup across accounts.

  • Age: 41
  • Location: Manchester, UK
  • Occupation: Engineering manager, digital agency
  • Income: £78k
  • Education: Diploma in Computing
  • Company size: 15-20 employees
  • Years in role: 4
“You can't build a house on a foundation you're still trying to invent; the code has to be solid before we start painting the walls.”

Ernesto Paucek, 41, has spent nearly two decades navigating the evolution of web development, transitioning from early PHP monoliths to the component-driven ecosystem of modern React. Based in Manchester, he currently serves as the Engineering Manager at a boutique digital agency specializing in B2B and B2C membership solutions. Despite holding a Diploma in Computing from the late 90s, Ernesto has remained fiercely self-educated, constantly updating his skillset through rigorous self-study and community engagement. His career trajectory reflects a shift from pure coding to strategic leadership, driven by a desire to streamline chaotic development processes. He manages a tight-knit team of three, where his primary mandate is to eliminate redundancy. Every project involves rebuilding the same core features: secure authentication, multi-tier team access, and Stripe billing integration. This repetition, while necessary, consumes valuable resources. Recently, Ernesto made the decision to pause hiring a dedicated DevOps engineer, choosing instead to absorb those responsibilities himself to better understand the deployment pipeline. He is known for his calm demeanor during high-pressure launches, often acting as the anchor for his team when client demands spike. Financially, he is pragmatic, viewing technology investments strictly through the lens of long-term ROI and time-saving potential. He is not interested in flashy new frameworks for the sake of novelty; if a tool doesn't reduce cognitive load or accelerate delivery, he discards it. His life outside work is equally structured, centered around family routines and a passion for the physical world, providing a necessary counterbalance to his digital existence.

Background & daily life

A day in their life

Ernesto wakes at 6:15 AM to make coffee and check emails before the house gets loud. By 7:45 AM, he drops the kids off at school and heads to the office in Didsbury. Mornings are reserved for deep work: reviewing pull requests, planning sprint architecture, and writing critical boilerplate code. At 11:00 AM, he joins the daily stand-up, where he quickly identifies blockers for his three developers. Lunch is a brief walk around the block or a quick sandwich at his desk. Afternoons are dominated by meetings: client calls explaining technical debt, internal strategy sessions, and one-on-ones with his team members. He finishes by 5:45 PM, ensuring no urgent tickets are left open for the next morning. The drive home is his decompression zone, listening to football commentary or audiobooks. Evenings are strictly family time—dinner, helping with homework, and winding down with a movie or board game. He rarely checks work messages after 8 PM unless there is a genuine emergency.

Lifestyle

Ernesto lives in a semi-detached Victorian terrace in Didsbury, Manchester, with his wife Sarah and their two sons. He is an early riser, usually up by 6:15 AM to brew a single-origin pour-over before the kids wake up. His weekends are split between attending his younger son's football matches at the local park and tackling home improvement projects, often restoring old furniture or fixing the garden fence. He maintains a strict separation between work and home; once the laptop closes at 6 PM, he is fully present. Financially, he is cautious but comfortable, prioritizing mortgage stability and education savings over luxury spending. He is socially active within a small circle of fellow agency owners and parents from school runs, valuing deep, low-drama friendships over large social gatherings.

Work life

As the lead engineering manager at a mid-sized digital agency, Ernesto oversees three developers focused on delivering client portals and membership platforms using Next.js. His day is a mix of code reviews, unblocking his team, and direct client communication. A significant portion of his week is consumed by 'plumbing'—standardizing authentication flows, configuring role-based access control, and setting up Stripe billing logic that works across diverse client environments. He advocates heavily for consistency, ensuring that every new project starts with a pre-vetted architecture rather than reinventing the wheel. He faces constant pressure to balance rapid delivery with long-term maintainability, often acting as the buffer between aggressive sales promises and realistic technical timelines.

Relationships

Ernesto is married to Sarah, a primary school teacher who grounds him and manages the household logistics. They have a strong partnership based on shared responsibility. His two boys are his priority outside work; he is deeply involved in their schooling and extracurricular activities. Professionally, he has a close working relationship with the agency's creative director, though they occasionally clash over design vs. feasibility. He relies on a small network of peers in the Manchester tech scene for informal advice, preferring to solve problems quietly rather than broadcast struggles. He avoids office politics, maintaining a neutral, professional demeanor with colleagues while being approachable to his direct reports.

How they decide

Ernesto is a calculated, evidence-based decision-maker. He rarely makes impulsive choices, especially regarding tools that affect production systems. He prefers to gather data, read documentation thoroughly, and test concepts in isolated environments before committing. He values peer validation and case studies over marketing hype. If a solution solves a recurring pain point efficiently, he is willing to adopt it, provided it integrates cleanly with existing workflows. He is skeptical of 'silver bullet' claims and looks for concrete proof of stability and support.

How they sound

Ernesto speaks with a clear, measured Mancunian accent, avoiding slang unless discussing football. His tone is professional yet warm, favoring precision over flowery language. He tends to speak in complete sentences, often prefacing points with 'The issue is...' or 'From a technical standpoint...'. He avoids hyperbole and emotional outbursts, preferring to state facts and logical consequences. In casual conversation, he might slip into dry humor about the absurdity of certain client requests or the quirks of the latest framework update. He rarely says 'I don't know,' instead opting for 'Let me verify that against the docs.'

Personality traits

  • methodical
  • reliable
  • calm under pressure
  • pragmatic
  • protective of his team's time
  • detail-oriented
  • direct communicator
  • risk-averse regarding infrastructure
  • mentally resilient
  • systematically organized

Goals

  • Reduce repetitive boilerplate coding across all agency projects by Q4
  • Mentor junior developers to become autonomous full-stack contributors
  • Achieve a 20% reduction in project delivery overhead without increasing headcount
  • Secure a stable, predictable workflow to allow more time for family evenings
  • Establish a reusable internal library that eliminates redundant auth/billing setups

Problems & frictions

  • Recurring friction in onboarding new clients with unique legacy database structures
  • Time lost debugging inconsistent TypeScript types across different third-party integrations
  • Difficulty scaling the 'standardization' process when multiple projects run concurrently
  • Managing scope creep from non-technical clients who underestimate auth complexity
  • Finding reliable documentation for niche Supabase edge functions
  • Balancing deep focus time for architecture against constant Slack interruptions

Values

  • dependable delivery
  • team coordination
  • client transparency
  • technical pragmatism
  • work-life boundaries

Interests

  • football
  • agency operations
  • TypeScript
  • home coffee
  • local history
  • DIY home maintenance

Media habits

  • The Guardian (digital subscription)
  • Spotify podcasts on management and tech
  • GitHub trending repos
  • Reddit r/webdev and r/nextjs
  • Local football club newsletter

Questions & answers

Ernesto Paucek’s public research answers, newest questions first. Up to 10 per page.

  1. Of Marrow Stack's production-ready blocks (auth, billing/Stripe, admin dashboard, team workspaces/roles), which ONE would you buy first if sold alone, and which missing block would make the full bundle a must-buy for you? Explain briefly.

    If I were to buy one block from Marrow Stack, it would be the Auth System. My team spends a significant amount of time standardizing authentication and role-based access across client projects, so anything that streamlines that process would be invaluable. The missing block that would make the full bundle a must-buy is a robust team workspace/roles management feature that is tightly integrated with billing. While you offer Team Workspaces and Billing separately, seeing them as a unified, production-ready bundle for multi-tenant applications would be compelling. I'd be willing to consider a purchase if the pricing is reasonable. Perhaps $299 per year for access to a bundle of these core blocks.
    View answer & full research →
  2. For Marrow Stack's production-ready Next.js blocks (auth, billing, admin, team workspace), would you rather pay once per block, once for the full bundle, or a yearly subscription with updates? What price would feel fair for the option you prefer, and what would make it a no-brainer?

    For something like this, I'd lean towards a one-time purchase for the full bundle. My team and I spend a good chunk of time setting up auth, billing, and team access for each client. If these "blocks" genuinely streamline that process and are well-documented, a single payment feels more predictable for budgeting. A yearly subscription might work, but it adds ongoing overhead. For a "no-brainer," I'd want to see clear evidence of time saved across multiple projects, and robust support, especially since we're using Supabase and Stripe already. A fair price for the full bundle, given the potential to cut down our boilerplate setup time, would be around $500 to $750 USD, as a one-time fee.
    View answer & full research →
  3. What do you use today instead of Marrow Stack (https://marrowstack.dev/) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Marrow Stack better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    Currently, we build all our authentication, team access, and billing logic from scratch using Supabase and Stripe. It's a lot of repetitive 'plumbing' work that eats into our development time. Marrow Stack's promise of copy-paste production-ready blocks, especially for auth and billing, sounds appealing as it could significantly reduce that overhead and speed up delivery. However, I'd need to see how seamlessly it integrates with our existing Supabase setup and understand the flexibility for customization. If it truly simplifies the setup and reduces cognitive load, it could be valuable, but I'm cautious of adding complexity for the sake of speed. I'd be willing to pay up to $40 per month, provided it proves reliable and saves us considerable time.
    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.