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

Wallace Lowe-Schuppe

Wallace Lowe-Schuppe

Engineering manager at a growth-stage B2B platform

Full-depth AI personas

Why this persona fits the audience

He manages a 9-person backend and platform group in Manchester for a logistics SaaS that already runs user auth through Amazon Cognito. His team owns invite flows, role-based access, support impersonation, and the internal admin tools that customer success uses every day.

  • Age: 38
  • Location: Manchester, UK
  • Occupation: Engineering Manager
  • Income: £125k salary + bonus
  • Education: BEng in Software Engineering
  • Company size: 250 employees
  • Years in role: 4
““You can build for the now, but true engineering is about building for what comes next, without making it brittle.””

Born and raised in Greater Manchester, Wallace developed an early fascination with how things worked, taking apart old radios and meticulously rebuilding them. His parents, both educators, fostered a strong sense of diligence and intellectual curiosity. He pursued a BEng in Software Engineering at the University of Manchester, where he met his wife, Sarah. Post-graduation, he joined a small e-commerce startup, gaining invaluable experience in building systems from the ground up, but also witnessing firsthand the chaos of unmanaged growth. He transitioned to his current company six years ago, initially as a senior backend engineer, and was promoted to Engineering Manager three years ago. His current role involves managing the backend and platform team responsible for critical user management functionalities, including invite flows, role-based access, impersonation, and internal admin tools, for a growing logistics SaaS. This involves a constant balancing act: ensuring the stability of their Amazon Cognito-backed authentication system while iterating on complex features. He recently championed a shift towards more standardized API gateways within their microservices architecture to improve inter-service communication clarity. Financially, Wallace is focused on long-term security, diligently contributing to his pension and mortgage, viewing his income as a means to provide stability for his family and fund his passions. Time is his most precious commodity, a constant negotiation between demanding work, family life, and his desire to tinker with woodworking projects and homebrewing experiments in his shed, which he views as essential mental resets. He values concrete outcomes and measurable improvements, preferring systems that are robust and predictable over flashy, untested solutions. His professional journey has instilled in him a deep appreciation for well-architected systems and the quiet satisfaction of solving complex problems reliably.

Background & daily life

A day in their life

Wallace's typical weekday begins at 6:30 AM with a quick scan of overnight alerts and Hacker News, followed by getting his children ready for school. His commute, a 45-minute train journey into Manchester, is spent listening to tech podcasts or reviewing his calendar. The workday is a mix of 1:1s with his team members, sprint planning meetings, architectural discussions, and troubleshooting urgent issues. He aims to block out an hour for deep work on infrastructure improvements, often interrupted. He leaves work around 5:30 PM, picks up his kids, and spends the evening with his family, often working on his homebrew or woodworking after the children are in bed, usually by 10:30 PM.

Lifestyle

Wallace lives in a semi-detached house in a suburb of Manchester with his wife, Sarah, a primary school teacher, and their two young children. His days are a carefully managed juggle between work, family commitments, and personal pursuits. Weekends often involve football matches, park trips with the kids, and dedicated time in his shed workshop, perfecting his latest brewing batch or sanding a new bookshelf. He's mindful of his finances, aiming for long-term stability, and prioritizes healthy eating and regular, if brief, exercise. Social life is often focused around family gatherings or occasional catch-ups with a few close university friends.

Work life

As an Engineering Manager, Wallace spends his days navigating the complexities of a rapidly scaling SaaS product. His primary focus is ensuring the stability and scalability of the backend systems, particularly the user management components that underpin the entire logistics platform. He's currently wrestling with optimising invite flows for enterprise clients and ensuring the internal admin tools are robust enough for the growing customer success team. The pressure is constant but manageable, stemming from tight release schedules and the need to balance new feature development with critical infrastructure maintenance, all while managing a distributed team and collaborating with Product and Operations.

Relationships

Wallace is married to Sarah, who provides a grounding influence and manages the household's social calendar. His parents, retired teachers, live nearby and offer occasional childcare support. He has a close-knit group of three university friends he sees quarterly for a pub meal. Within work, he trusts his Principal Engineer implicitly and maintains a professional, respectful rapport with the Head of Product.

How they decide

Wallace is a cautious, research-driven decision-maker. He prefers to gather data, consult with senior team members, and thoroughly assess potential impacts before committing to a course of action. He values clarity and well-defined processes, often sketching out diagrams or flowcharts to ensure all angles are considered.

How they sound

Speaks with a clear, measured Mancunian accent, but often adopts a more formal tone in professional settings. He uses precise language, avoiding excessive slang or jargon unless explaining technical concepts. Cadence is steady; he pauses to consider his words. He tends to understate his own contributions and emphasizes team effort. Can sound slightly weary when discussing operational challenges but becomes animated when talking about technical architecture.

Personality traits

  • Methodical
  • Detail-oriented
  • Pragmatic
  • Reliable
  • Introverted
  • Slightly reserved
  • Forward-thinking
  • Patient
  • Quietly ambitious

Goals

  • To build a truly resilient and scalable platform architecture
  • To foster a high-performing and cohesive engineering team
  • To achieve greater work-life integration, not just balance
  • To complete a challenging woodworking project (e.g., a dining table)
  • To visit a major European city with his family

Problems & frictions

  • Managing technical debt while pushing new features
  • Ensuring consistent team performance across different time zones
  • Onboarding new engineers effectively into complex systems
  • Balancing the needs of internal tools versus customer-facing features
  • Finding uninterrupted blocks of time for deep technical thinking

Values

  • stability
  • clarity
  • systems thinking
  • responsibility
  • efficiency

Interests

  • infrastructure
  • football (Manchester City fan)
  • home brewing (craft ales)
  • woodworking (building furniture)

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute
  • Follows industry blogs for infrastructure trends
  • Subscribes to engineering newsletters
  • Watches YouTube tutorials for woodworking

Questions & answers

Wallace Lowe-Schuppe’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://clerk.dev/blog/all-of-user-management-not-just-authentication (Clerk) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The core message that Clerk handles "all of user management, not just authentication" is clear and resonates. I appreciate the candidness about the limitations of typical "auth-as-a-service" providers. What's unclear is the depth of their "User Button" functionality and how easily it integrates with our existing Amazon Cognito setup. While the UI examples look clean, I'd need to see more about the backend API and SDK support for various languages beyond what's immediately apparent. The roadmap mentions team management and enterprise auth like SAML, which are crucial for us, but the "minimum viable product" phrasing makes me cautious. I'd sign up if I could easily integrate it with our current system, perhaps through a trial, and see concrete examples of it handling complex invite flows and role-based access, as those are daily challenges for my team.
    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.