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

Luka Hazes

Luka Hazes

Cloud support engineer with a cautious tool style

Full-depth AI personas

Why this persona fits the audience

He supports a 3-person internal tools team and usually validates service behavior against live Azure test subscriptions first, then recreates issues locally with Azurite, dockerized dependencies, and a spreadsheet of known differences. The team’s daily workflow includes repeated local repro attempts and careful note-taking rather than one standardized lab stack.

  • Age: 41
  • Location: Amsterdam, Netherlands
  • Occupation: Cloud support engineer
  • Income: €79k
  • Education: B.Sc. Computer Science
  • Company size: Mid-sized tech consultancy (approx. 250 employees)
  • Years in role: 7
“The most reliable path forward is paved with verifiable data and a clear understanding of how things *actually* work, not just how they're supposed to.”

Luka Hazes, 41, is a seasoned Cloud Support Engineer based in Amsterdam, holding a B.Sc. in Computer Science. His career has been defined by a commitment to stability and meticulous problem-solving, particularly within the complex ecosystem of Microsoft Azure. He currently supports a lean internal tools team of three, a role that demands a high degree of responsibility and precision. Luka's professional ethos is characterized by a cautious, evidence-based approach to tooling and validation. Before declaring a service behavior as 'resolved' or 'understood,' he meticulously validates it against live Azure test subscriptions. This is followed by a rigorous local reproduction process, leveraging tools like Azurite for emulating Azure Storage, dockerized dependencies for isolated environments, and an extensive, personally maintained spreadsheet that meticulously documents known differences between local setups and the live cloud. This detailed comparison is crucial, as his team eschews a single, standardized lab stack in favor of individual setups, making his comparative analysis indispensable. His daily workflow is a testament to his conscientiousness, involving repeated local reproduction attempts and painstaking note-taking, a stark contrast to more streamlined, automated approaches. This methodical nature extends beyond his immediate work; he is a keen reader of nonfiction, particularly on topics of system architecture and history, and harbors a passion for classic cars, appreciating their engineering and enduring design. Financially, Luka is conservative, prioritizing saving and stability over speculative investments, reflecting his overall aversion to unnecessary risk. He lives alone in a rented apartment, finding contentment in his ordered routines and the intellectual stimulation of his work and personal interests. His career goal is to ascend to a senior architect position, leveraging his deep understanding of cloud systems to design more robust and predictable solutions. He is driven by a desire to ensure the reliability of the systems he supports, viewing each resolved incident as a reinforcement of his commitment to stability and responsibility.

Background & daily life

A day in their life

Luka's weekday begins around 7:00 AM with a quick breakfast and scanning tech news. He cycles to the office, arriving by 8:30 AM. The morning is dedicated to reviewing overnight alerts and tackling the most critical support tickets, often involving deep dives into Azure logs and attempting local repros. Lunch is a simple affair, usually eaten at his desk while reading a technical article. The afternoon might involve collaborating with a developer on a particularly tricky bug, updating his team's knowledge base, or refining his spreadsheet of Azure differences. He leaves around 5:30 PM, cycles home, and spends his evening reading or working on a personal project, rarely deviating from this routine.

Lifestyle

Luka lives a quiet, ordered life in Amsterdam. His apartment is neat, filled with books and a few carefully maintained classic car models. He cycles to work most days, enjoying the crisp air. Evenings are typically spent reading nonfiction or tinkering with a personal coding project. He's not one for spontaneous outings, preferring planned social gatherings with a small circle of close friends. Financially, he's prudent, saving consistently and avoiding unnecessary debt, which provides him a sense of security. He prioritizes his health with regular cycling and a balanced diet.

Work life

As a cloud support engineer, Luka's days are consumed by troubleshooting complex Azure issues for internal tools. He works closely with a small, dedicated team of three, where meticulous documentation and reproducible steps are paramount. His approach is deliberately cautious; he always starts by verifying behavior in live Azure test subscriptions before attempting local reproduction. This involves Azurite, Docker, and a detailed spreadsheet tracking environmental differences. The pressure comes from minimizing downtime and ensuring the stability of the tools his colleagues rely on daily. He spends significant time documenting findings, often feeling the weight of responsibility for critical systems.

Relationships

Luka maintains a small but strong circle of friends, mostly from university, with whom he shares intellectual discussions and occasional quiet evenings. He has a good working relationship with his immediate team, built on mutual respect for their technical skills and shared commitment to stability. His family lives in a different province, and they communicate weekly via phone calls.

How they decide

Luka is a highly research-driven and cautious decision-maker. He meticulously gathers evidence, compares options, and considers potential risks before committing to a course of action. He values stability and predictability, preferring proven methods over experimental ones. Peer consultation is minimal; he trusts his own analysis and documented findings.

How they sound

Speaks with a measured, calm cadence. His Dutch accent is subtle but present. He uses precise technical language, avoiding slang or overly casual phrasing. He tends to be thorough in his explanations, sometimes to the point of being slightly verbose, ensuring all details are covered. He rarely expresses strong emotions, maintaining a professional and objective tone.

Personality traits

  • methodical
  • detail-oriented
  • patient
  • reserved
  • analytical
  • reliable
  • risk-averse
  • observant

Goals

  • Achieve a senior architect role within his company
  • Complete a personal project involving automated cloud infrastructure testing
  • Maintain a stable and predictable work-life balance
  • Become a recognized subject matter expert in Azure service reliability
  • Save enough for a down payment on a small house outside the city

Problems & frictions

  • The lack of a standardized, reliable local development environment across the team
  • Time constraints due to the volume of support tickets and the need for deep investigation
  • Difficulty in isolating intermittent cloud service behaviors
  • Keeping up with the rapid pace of Azure service updates and deprecations
  • Balancing thoroughness with the need for quick resolutions

Values

  • evidence
  • stability
  • responsibility
  • thoroughness
  • predictability

Interests

  • incident response
  • classic cars
  • nonfiction reading
  • system architecture
  • historical documentaries

Media habits

  • Reads tech blogs (e.g., Hacker News, specific Azure blogs)
  • Listens to podcasts during commute (tech news, history)
  • Follows key figures on LinkedIn for industry updates
  • Occasional YouTube tutorials for specific technical problems
  • Reads physical books in the evenings

Questions & answers

Luka Hazes’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.

    A single-binary Azure emulator? My biggest challenge is the inconsistency between local setups within my team. We all use Azurite and Docker, but subtle differences always creep in, leading to time spent reconciling discrepancies instead of solving the actual issue. This often means extra hours trying to reproduce a bug that only appears in the cloud. We've tried standardizing our Docker configurations, but it's a constant battle to keep them perfectly aligned. The cost is primarily wasted time for myself and my colleagues, delaying our ticket resolution.
    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.