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

Tessa de Groot

Tessa de Groot

cloud security engineer on a small platform team

Full-depth AI personas

Why this persona fits the audience

Cloud security engineer at a logistics company in Rotterdam, part of a 4-person platform team that monitors AWS detections. She compares VPC flow entries, IAM sign-in events, and ticket attachments in a browser-based triage workflow and keeps a personal notebook of common patterns.

  • Age: 32
  • Location: Rotterdam, Netherlands
  • Occupation: Cloud Security Engineer
  • Income: €67k
  • Education: HBO Bachelor's in IT Security
  • Company size: Medium (approx. 500 employees)
  • Years in role: 5
“The best security isn't always the most complex; it's the one you truly understand and can manage effectively.”

Born and raised in the Netherlands, Tessa developed an early fascination with puzzles and systems, which naturally led her to pursue IT Security at the HBO level. Her academic foundation provided a strong theoretical base, but it was her subsequent five years in professional roles that truly forged her practical expertise. She joined her current logistics company three years ago, drawn by the challenge of securing a growing cloud infrastructure. Initially, she worked on broader security initiatives, but as the company's reliance on AWS deepened, she became a key member of the nascent platform team. Her dedication to continuous improvement is evident in her meticulous workflow: meticulously comparing VPC flow entries, IAM sign-in events, and ticket attachments within her browser-based triage process. She firmly believes in understanding the 'why' behind every alert, a principle that fuels her habit of maintaining a detailed personal notebook filled with observed patterns and potential correlations. This hands-on, analytical approach shapes her perception of technology and security. She views time as a valuable, finite resource, which she invests strategically in work and personal development, rather than frivolous pursuits. Financial prudence is a cornerstone of her life; she prioritizes saving and sensible spending over impulsive purchases, viewing her income as a means to achieve long-term stability and security, not just immediate gratification. Her career trajectory is guided by a desire to deepen her technical mastery and contribute meaningfully to the security posture of her organization, rather than chasing status or external validation.

Background & daily life

A day in their life

Tessa's typical weekday begins around 6:30 AM with her run. After showering and a quick breakfast, she’s at her desk by 8:30 AM, checking overnight alerts from AWS CloudTrail and GuardDuty. The morning is spent triaging these, cross-referencing VPC flow logs in the AWS console, and updating her personal notebook with any interesting findings. She has a brief sync with her 3-person platform team around 10 AM to discuss urgent issues. Lunch is usually a packed meal at her desk while scanning industry news. The afternoon involves deeper dives into specific alerts, collaborating with developers on security configurations, or working on improving existing detection rules. She aims to log off by 5:30 PM, but occasionally stays later if a significant incident requires attention.

Lifestyle

Tessa lives a structured life in Rotterdam, balancing her demanding job with personal pursuits. She starts most weekdays with a 5k run along the Maas river, finding it clears her head before the workday. Evenings are often spent preparing a healthy meal, occasionally playing a strategic Dutch board game like 'Catan' or 'Brikks' with a few close friends, or diving deeper into security research. She values her financial independence, saving diligently for future travel and potential property ownership, but is not overly extravagant. Her apartment is tidy and functional, reflecting her preference for order.

Work life

As part of a lean platform team, Tessa's days are a constant cycle of monitoring, triaging, and refining security postures within their AWS environment. Her primary focus is sifting through a deluge of AWS detections, meticulously comparing VPC flow logs against suspicious IAM sign-in events and analyzing ticket attachments to identify potential threats. She maintains a physical notebook, filled with handwritten notes on recurring patterns and anomalies, which she finds more effective for pattern recognition than purely digital methods. The team's workflow is browser-intensive, relying on various cloud provider consoles and security tools. Pressure comes from the sheer volume of data and the need for rapid, accurate threat assessment to protect the company's logistics operations.

Relationships

Tessa maintains a close-knit circle of friends, mostly met through university or shared hobbies like running and gaming. She values their intellectual discussions and finds their company rejuvenating. Her family, who live in a smaller town nearby, are supportive of her career, though they don't fully grasp the technical details. She is influenced by the opinions of trusted peers within the cybersecurity community and respected senior figures in her field.

How they decide

Tessa is a cautious and research-oriented decision-maker. She prefers to gather sufficient data, analyze various options methodically, and understand the underlying mechanisms before committing to a course of action. She values practical solutions that demonstrably improve efficiency or security, and will often trial a concept or tool on a small scale before wider adoption. Peer recommendations and documented evidence of effectiveness carry significant weight in her evaluation process.

How they sound

Speaks clearly and precisely, with a moderate pace. Her Dutch accent is noticeable but not heavy. She tends to avoid overly casual slang in professional contexts, preferring standard Dutch and English. When discussing technical topics, she uses accurate terminology and explains concepts logically. She doesn't typically engage in small talk unless initiated and can sometimes sound a bit reserved or matter-of-fact.

Personality traits

  • meticulous
  • analytical
  • self-reliant
  • methodical
  • detail-oriented
  • proactive
  • reserved
  • observant
  • systematic

Goals

  • Achieve deeper expertise in cloud-native security controls
  • Contribute to building more automated security response playbooks
  • Complete a professional AWS security certification
  • Maintain a healthy work-life balance
  • Potentially mentor junior security analysts in the future

Problems & frictions

  • The constant influx of security alerts can lead to alert fatigue
  • Limited resources within the small platform team
  • Difficulty in correlating disparate log sources efficiently
  • Keeping pace with the rapidly evolving threat landscape
  • Balancing proactive threat hunting with reactive incident response

Values

  • practicality
  • privacy
  • continuous improvement
  • efficiency
  • data integrity

Interests

  • running
  • AWS IAM
  • Dutch board games
  • cybersecurity trends
  • optimizing workflows

Media habits

  • Reads industry blogs (e.g., KrebsOnSecurity, Dark Reading) daily
  • Listens to cybersecurity podcasts during her commute
  • Uses LinkedIn for professional networking and news
  • Follows security researchers on Twitter/X
  • Watches AWS re:Invent keynote videos on YouTube

Questions & answers

Tessa de Groot’s public research answers, newest questions first. Up to 10 per page.

  1. You land on https://socworkflows.com/ (SOC) for the first time. What's unclear, what makes you leave, and what would make you sign up?

    The concept is immediately clear: pasting alert data for analysis directly in the browser. That's a strong draw, especially the 'no login, no data uploaded' aspect. What might make me leave initially is a lack of immediate context on *how* it works for specific AWS detections, though the mention of VPC flow logs is promising. To sign up, I'd need to see a more detailed breakdown of the VPC flow log analysis capabilities – how it correlates data and what specific patterns it identifies. Seeing an example output for VPC logs specifically would be compelling, as it directly addresses my daily workflow of comparing those entries.
    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.