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

Badr Postma

Badr Postma

Growth engineer on a travel startup

Full-depth AI personas

Why this persona fits the audience

Works on a 6-person product-and-growth team in Amsterdam. He owns a pipeline that generates hotel and city pages from structured data, and he reviews releases with git diffs, test scripts, and crawl samples because the site changes several times a week.

  • Age: 28
  • Location: Amsterdam, Netherlands
  • Occupation: Growth Engineer
  • Income: €74k
  • Education: MSc Software Engineering
  • Company size: 20 people total (travel startup)
  • Years in role: 2
“I'd rather spend two hours fixing a broken template than spend two seconds explaining why it broke in the first place.”

Badr Postma grew up between Leiden and Rotterdam, the son of university professors who encouraged his early interest in computers. He built his first website at 12 and then spent a decade systematically turning that curiosity into a career. His Master's in Software Engineering from TU Delft honed his obsession with clean systems, though he quickly realized he preferred building things that directly impacted users. After working briefly at a fintech scaleup, he joined his current Amsterdam-based travel startup as their first dedicated growth engineer. The role was a perfect fit—it combined his engineering rigor with his interest in how search engines interact with dynamic content. His current focus is optimizing their programmatic SEO pipeline, which generates thousands of hotel and city pages daily. He's particularly proud of the validation system he built that catches template inconsistencies before they get indexed. Outside work, Badr is equally methodical. His climbing progress log grows daily with detailed notes about grip positions and foothold techniques. He takes the same approach to technology—he maintains a personal wiki of Git workflows he's developed, obsessively testing each variation for efficiency. His peers describe him as a 'human checklist' who can spot elusive bugs without breaking into a sweat. He's uncomfortable with uncertainty (once spent a weekend optimizing a 2% improvement in crawling speed) but embraces the challenge of making complex systems understandable. Currently, he's facing the universal problem of balancing speed with quality as his company grows. He's testing automated crawl validation tools but remains skeptical about anything that might miss edge cases. His ideal weekend would involve a solo trip to a Nordic country he hasn't visited, where he could both climb and research new city page templates.

Background & daily life

A day in their life

6:30 AM: Wakes up to timer, makes coffee. 7:00: Climbs stairs 5 flights to warm up. 7:45: Bike to office with backpack full of cables and a hardcover coding book. 9:00: Reviews new crawl reports, flags 3 template variations that might trigger duplicates. 11:00: Sync with PM about upcoming feature that will affect hotel page structure. 1:00: Lunch at desk while watching a Python webinar. 2:30: Writes new validation script to catch template inconsistencies. 4:45: Reviews pull request with 200-line Git diff, finds potential crawler pitfall. 6:30: Climbing gym, works specifically on right-side toe hooks. 8:15: Pasta at home while watching YouTube about Nordic travel. 10:00: Light reading on Rust concurrency models before sleep.

Lifestyle

Badr lives in a compact but well-organized apartment near Amsterdam Centraal, where he can walk to work in 15 minutes or ride his bike in 7. His mornings start with a meticulous pour-over coffee ritual using beans from his favorite local roastery. He hits the climbing gym 3 times a week (always on Mondays, Wednesdays, and Fridays) and has been working on his toe-hook technique for months. Financially, he's comfortable but deliberate—he splits his discretionary spending between climbing gear and tech tools. Weekends often involve hacking on personal projects or exploring Europe's lesser-known cities, always with a pre-researched itinerary. His social life is small but tight-knit, mostly consisting of fellow tech workers and climbing partners who appreciate his dry humor.

Work life

As the sole growth engineer at a travel startup, Badr's days are a mix of maintaining their programmatic SEO pipeline and launching experiments. His workstation is a chaos of monitors displaying GitHub, crawler results, and spreadsheet dashboards. He spends mornings reviewing crawl samples for template inconsistencies and afternoons building new page-generator scripts. The startup culture is casual but intense—the small team deploys multiple times a week, which means constant vigilance. He's currently optimizing their hotel page templates after noticing some got flagged for thin content. His biggest frustration? Product managers who don't understand how their changes affect crawlers. Despite this, he enjoys the ownership and the fact that he can see his work's impact directly in traffic numbers.

Relationships

Badr's immediate community consists of his co-workers (who he considers competent but sometimes sloppy) and his climbing gym buddies. He's close with his sister, who's a doctor in Rotterdam, but his parents back in Leiden worry he's too 'isolated' in Amsterdam. He follows a few thought leaders in growth engineering and climbing, but mostly learns through experimentation. His colleagues appreciate his precision, though some find his directness a bit blunt. He's the go-to person for Git workflow advice and the unofficial office barista.

How they decide

Analytical and methodical, but with room for intuition when data is inconclusive. Prefers to test small changes before committing, values peer input on technical decisions, and will change course quickly if evidence contradicts initial assumptions. Hates decisions made purely on 'gut feeling' but respects experience when it's demonstrated with results.

How they sound

Speaks in measured, precise sentences with occasional dry humor. Avoids jargon when talking to non-technical people but will switch to deep technical language with peers. Uses simple metaphors for complex concepts. Pronounces 'Amsterdam' correctly (not 'Amster-dam'). Gets slightly impatient with vague language. Laughs quietly at his own jokes. Sometimes ends sentences with 'right?' as a conversational tic.

Personality traits

  • prefers deep dives over small talk
  • tests everything before deploying
  • annoyed by vague requirements
  • finds peace in structured routines
  • speaks clearly but dryly about technical topics
  • secretly enjoys spreadsheet hacking
  • always has a backup plan
  • gets frustrated when people don't follow best practices
  • values precision in language and code
  • tends to over-prepare for presentations

Goals

  • Build a scalable system that doesn't need constant babysitting
  • Climb a 7a grade route consistently
  • Learn enough Rust to build something useful
  • Visit all Nordic countries (Sweden still needs checking)
  • Reduce time spent on manual crawl validations

Problems & frictions

  • Template changes propagate unpredictably across the site
  • Team doesn't always document crawl impacts of new features
  • Some city pages get flagged as thin content despite similar structure
  • Struggles to find time for personal coding projects
  • Climbing progress plateaus when work is intense

Values

  • engineering rigor
  • experimentation
  • ownership
  • autonomy
  • curiosity

Interests

  • travel tech
  • git workflows
  • Python
  • climbing
  • minimalist design
  • coffee brewing

Media habits

  • listens to tech podcasts during commutes
  • reads Hacker News and SEO blogs
  • uses RSS for niche growth engineering content
  • follows climbing documentary accounts

Questions & answers

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

  1. What do you use today instead of pseolint (https://pseolint.dev) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make pseolint better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

    I currently use a combination of custom scripts and manual crawls to check for programmatic SEO issues. My scripts flag near-duplicates and thin content, but they aren't as template-aware as pseolint. What makes pseolint appealing is its ability to group findings by template, which would save me time fixing structural issues in bulk. However, I'm skeptical about relying solely on an external tool for this critical task—especially without seeing more about how it integrates with our CI/CD pipeline. If it can reliably flag template-level issues before deployment, I'd consider it. I'd cap my budget at $30/month for this, but only if it proved faster and more accurate than my current setup.
    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.