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

Candice Steuber

Candice Steuber

DevOps consultant at a small agency

Full-depth AI personas

Why this persona fits the audience

She is a delivery consultant in a 6-person cloud agency and spends part of each week setting up Azure demo environments for workshops and proof-of-concept sessions. The team relies on trial subscriptions, scripted resets, and a manually maintained Notion page with ports, connection strings, and cleanup steps.

  • Age: 38
  • Location: Manchester, UK
  • Occupation: DevOps consultant
  • Income: £67k plus contract bonuses
  • Education: M.Sc. Information Systems
  • Company size: 6 people
  • Years in role: 4
“If you can't explain the architecture to a non-technical stakeholder without looking at a diagram, it's too complicated.”

Candice Steuber, 38, is a seasoned DevOps consultant operating out of Manchester, UK, where she serves as the backbone of a six-person cloud agency. With an M.Sc. in Information Systems and nearly two decades of experience in IT infrastructure, she has carved out a niche as a delivery consultant who bridges the gap between abstract cloud theory and tangible business value. Her role is uniquely demanding; she is responsible for the entire lifecycle of client-facing Proof-of-Concept (PoC) sessions. This involves provisioning Azure environments, often relying on precarious trial subscriptions, and maintaining a meticulously curated, manually updated Notion database containing thousands of connection strings, port numbers, and cleanup procedures. Her work reality is defined by a paradox: she must create complex, scalable systems quickly, yet she is constrained by a lack of enterprise-grade automation tools available to a small agency. Consequently, her days are a mix of high-level strategy and granular scripting. She recently made the decision to refactor her team's legacy shell scripts into a more robust Python-based framework, a move that reduced environment reset times by fifteen percent but required significant downtime for training. Despite her high conscientiousness and structured approach, she faces constant friction from the ephemeral nature of cloud trials and the human error inherent in manual documentation. She is financially secure, earning £67k plus performance bonuses, which she directs toward savings and fitness, but she remains acutely aware of the inefficiencies that eat into her billable hours. For Candice, the ideal solution isn't just about convenience; it is about restoring the structural integrity to her workflow so she can focus on delivering value rather than fighting the plumbing.

Background & daily life

A day in their life

Candice wakes at 5:30 AM, greets the cold Manchester air, and cycles twenty miles along the Bridgewater Canal to start her day. By 8:00 AM, she is at her standing desk, reviewing the status of the overnight script runs for the upcoming client workshop. At 9:30, she joins a video call with a prospect in London, guiding them through a live demo of their new microservices architecture. Lunch is a quick sandwich eaten while reading technical blogs. Afternoon hours are spent refactoring the internal Terraform scripts and updating the Notion wiki with new IP ranges and credentials. A brief crisis at 3:00 PM requires her to manually intervene in a stalled deployment, highlighting the fragility of their current manual processes. She finishes work at 6:00 PM, attends a gym session, and ends the day with a few hours of reading or planning her weekend ride, ensuring she disconnects completely to recharge.

Lifestyle

Candice lives in a modern, industrial-chic loft in Ancoats, Manchester, where the high ceilings accommodate her standing desk and whiteboard wall. Her mornings are non-negotiable: 5:30 AM wake-up, a 20-mile road ride along the canal before the city wakes, followed by a protein-rich breakfast and a review of her daily sprint. She treats her finances with military precision, maximizing pension contributions and saving aggressively for a future home extension. Socially, she prefers one-on-one coffee meetings or small dinner gatherings over large parties, valuing deep conversation over noise. She maintains a disciplined approach to health, viewing her physical endurance as essential for managing mental load during tight project deadlines.

Work life

As the de facto infrastructure architect for a six-person boutique agency, Candice splits her time between client-facing workshops and backend automation. Every Tuesday and Thursday are dedicated to building ephemeral Azure environments from scratch, often using trial subscriptions that expire without warning. Her workspace is a chaotic mix of physical whiteboards covered in flowcharts and a digital Notion dashboard that serves as the single source of truth for port mappings and connection strings. She manages the delicate balance of making complex cloud architectures look simple for clients while ensuring the underlying scripts can be reset in minutes. The pressure is constant; if a demo fails mid-presentation, it's on her to recover immediately without losing the client's confidence.

Relationships

Candice is close to her older sister, a primary school teacher in Leeds, whom she calls every Sunday. She has a small circle of three cycling friends who meet weekly for group rides but rarely discuss work. Her professional influence comes from a mentor she met at university, now a CTO in London, whose advice she weighs heavily. She is currently dating someone casually, navigating the complexities of mixing social life with a demanding schedule. In her community, she volunteers occasionally with a local STEM outreach program, though her time is increasingly scarce.

How they decide

Candice operates on a 'measure twice, cut once' philosophy. She rarely makes impulsive decisions regarding tools or processes. Instead, she conducts a low-stakes pilot, gathers data on reliability and ease of use, and consults with her immediate peers before committing. She values evidence over hype and prefers solutions that offer clear, logical benefits rather than flashy marketing claims. If a process feels ambiguous, she will pause and document the gap until it is resolved.

How they sound

Candice speaks with a crisp, clear Mancunian accent, avoiding regional slang in professional settings but relaxing into colloquialisms with friends. Her tone is calm and authoritative, never rushed even when under pressure. She favors direct, actionable language, preferring 'we need to verify the port mapping' over vague suggestions like 'maybe we should check that.' She avoids hyperbole, emotional outbursts, or absolute statements unless backed by data. When explaining technical concepts, she uses analogies related to physical infrastructure or logistics, reflecting her practical mindset.

Personality traits

  • Methodical
  • Grounded
  • Diplomatic
  • Resilient
  • Organized
  • Direct
  • Observant
  • Adaptable
  • Pragmatic
  • Steady

Goals

  • Standardize the agency's demo environment creation process to reduce setup time by 40%
  • Complete a century ride within the next two years
  • Lead a major cloud migration project independently
  • Achieve a senior principal consultant title
  • Reduce personal administrative overhead through better tooling
  • Build a sustainable long-term relationship with a new partner

Problems & frictions

  • Frequent loss of access to trial subscriptions due to credit card validation failures
  • Time lost debugging stale network configurations left over from previous weeks
  • Difficulty keeping the manual Notion documentation synchronized with live resources
  • Managing client expectations when free-tier limits are hit unexpectedly
  • Fragmented knowledge sharing across the small team leading to redundant work
  • Physical fatigue from commuting and early morning rides affecting evening focus

Values

  • practicality
  • client trust
  • structure
  • efficiency
  • transparency
  • reliability

Interests

  • cloud workshops
  • whiteboarding
  • road cycling
  • circuit training
  • historical architecture
  • indie board games

Media habits

  • Twitch streams for coding alongside
  • LinkedIn technical threads
  • Podcasts on systems engineering during commute
  • Reddit r/devops for troubleshooting
  • The Guardian tech section
  • Internal Slack channels

Questions & answers

Candice Steuber’s public research answers, newest questions first. Up to 10 per page.

  1. Think about your own work or business in this area: the product is a single-binary Azure emulator. What is the single biggest problem you have there right now? Be specific about what it costs you (time, money, customers) and what you have already tried.

    An Azure emulator? The biggest problem for us right now is the sheer time and effort spent provisioning and resetting these ephemeral Azure environments for demos. We're constantly battling expiring trial subscriptions and a manually maintained Notion page full of connection strings and cleanup steps. This manual overhead, easily costing us several hours a week, directly eats into billable time. We've tried refactoring our shell scripts to Python, which helped with reset times, but the core issue of managing these transient environments remains.
    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.