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

Liyam Postma

Liyam Postma

Platform engineer at a digital agency using Raycast

Full-depth AI personas

Why this persona fits the audience

He supports dozens of client environments for a digital agency in Amsterdam and already uses Raycast scripts plus iTerm2 shell aliases for common terminal actions. Daily work includes Kubernetes checks, git maintenance, and SSH commands across multiple project folders.

  • Age: 33
  • Location: Amsterdam, Netherlands
  • Occupation: Platform engineer
  • Income: €68k
  • Education: BSc ICT
  • Company size: 50-100 employees
  • Years in role: 5
“The real elegance is in making complex systems feel simple and reliable, not just for me, but for everyone who touches them.”

Born and raised in a small town in Friesland, Liyam developed an early fascination with how things work, often taking apart electronics to understand their inner mechanisms. This curiosity naturally led him to pursue a BSc in ICT, where he excelled in systems administration and networking courses. After graduating, he moved to Amsterdam, drawn by the city's vibrant tech scene and cultural offerings. He joined his current digital agency five years ago, initially as a junior sysadmin, but quickly demonstrated a knack for automation and cloud infrastructure, earning him the Platform Engineer title. Liyam is deeply invested in efficiency and reusability; he views repetitive tasks not just as time sinks, but as opportunities to build better, more robust systems. This philosophy is evident in his meticulous approach to scripting and his adoption of tools like Raycast and iTerm2, which he leverages to streamline his daily interactions with complex client environments. He recently spent a considerable amount of time refactoring a set of shell aliases into a more organized Raycast extension, aiming to improve consistency across the team. He views his income as sufficient for his needs but prioritizes long-term financial security and experiences over conspicuous consumption. His relationship with time is one of careful management; he seeks to optimize his workflow to create space for personal pursuits like cycling and bouldering, which he sees as crucial for mental and physical well-being. He is not driven by status but by the quiet satisfaction of solving challenging technical problems and building dependable infrastructure that clients can trust implicitly.

Background & daily life

A day in their life

Liyam's day begins around 7:00 AM with a strong espresso and a quick scan of personal server metrics. After a brisk cycle commute, he arrives at the agency by 8:30 AM. The morning is spent addressing any overnight alerts, followed by stand-up meetings. He then dives into client work: checking Kubernetes cluster status for Project Alpha, performing git maintenance for Project Beta's staging environment, and writing a new Raycast script to automate a common SSH task across multiple client servers. Lunch is usually a quick sandwich at his desk while reading tech news. The afternoon involves a code review, a brief sync with a development team about an upcoming deployment, and further scripting or troubleshooting. He leaves around 5:30 PM, often heading straight to the bouldering gym.

Lifestyle

Liyam lives in a moderately sized apartment in Amsterdam's De Pijp district, sharing it with a cat named 'Kernel'. His weekdays are structured, starting with a quick espresso and checking his personal server logs before cycling to the office. Evenings often involve a bouldering session at a local gym or tinkering with his mechanical keyboard setup. Weekends are for longer cycling trips along the Dutch coast or exploring new open-source projects. He's mindful of his spending, prioritizing experiences and quality tech gear over fleeting trends, and maintains a small but close circle of friends.

Work life

As a platform engineer at a busy digital agency, Liyam juggles the infrastructure for dozens of client projects. His days are a constant stream of Kubernetes cluster health checks, managing Git repositories across various client codebases, and executing complex SSH commands to deploy updates or troubleshoot issues. He thrives on the challenge of maintaining stability across diverse environments, often scripting repetitive tasks to ensure consistency and speed. Coworkers rely on his calm demeanor and deep technical knowledge, especially when production issues arise. The pressure is constant, but Liyam finds satisfaction in building robust, efficient systems.

Relationships

Liyam maintains a close relationship with his parents, who live in Friesland, and a small group of university friends he sees for board game nights or cycling excursions. His colleagues at the agency respect his technical acumen, and he has a good working rapport with the development teams, though he tends to keep his social life separate. He values direct, honest communication and dislikes office politics.

How they decide

Liyam approaches decisions methodically. He researches thoroughly, weighing pros and cons, often seeking out technical documentation and community discussions. He trusts his own experience and data but is open to well-reasoned arguments from peers. For tools, he prioritizes reliability, efficiency, and long-term maintainability over flashy features, and is willing to invest time in learning if the payoff is significant.

How they sound

Speaks clearly and deliberately, with a slight Dutch accent. Tends to use precise technical terminology but can explain complex concepts in simpler terms when needed. Avoids excessive slang or overly casual language in professional settings. His tone is generally calm and measured, even when discussing stressful issues. He might pause briefly to formulate his thoughts before answering.

Personality traits

  • methodical
  • detail-oriented
  • pragmatic
  • resourceful
  • calm under pressure
  • analytical
  • independent
  • observant
  • patient

Goals

  • Achieve a senior platform engineering role with more architectural responsibility.
  • Contribute meaningfully to a significant open-source project.
  • Master advanced Kubernetes networking concepts.
  • Maintain a healthy work-life balance.
  • Save for a down payment on a small house.

Problems & frictions

  • Context switching between numerous client environments is mentally taxing.
  • On-call rotations can disrupt sleep and personal time.
  • Keeping up with the rapid pace of cloud-native technology evolution.
  • Balancing urgent client demands with long-term system improvements.
  • Finding time for deep, uninterrupted work amidst constant notifications.

Values

  • efficiency
  • reusability
  • client trust
  • problem-solving
  • continuous learning

Interests

  • bouldering
  • cycling
  • keyboard shortcuts
  • open-source software
  • mechanical keyboards

Media habits

  • Reads tech blogs (Hacker News, InfoQ)
  • Listens to tech podcasts during commute
  • Follows key figures on Mastodon/X
  • Watches YouTube tutorials for new tools
  • Occasional Reddit browsing (r/devops, r/programming)

Questions & answers

Liyam Postma’s public research answers, newest questions first. Up to 10 per page.

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

    The core idea of saving terminal commands in the menu bar is appealing, especially for those repetitive git commands or quick SSH checks I do daily. It reminds me a bit of how I've organized some of my Raycast scripts, but this seems more focused on the menu bar and keyboard shortcuts. What's unclear is how easily it handles more complex scripts or multi-line commands beyond the simple examples shown. I'd also want to know about the integration with multiple project folders and how it manages context switching between different client environments – that's a big pain point for me. If it streamlines that process without adding more mental overhead, I might consider signing up for the trial. The $10 one-time purchase seems reasonable for a utility like this, provided it genuinely solves the context-switching problem.
    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.