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

Moussa van de Veen

Moussa van de Veen

Backend engineer at a B2B startup

Full-depth AI personas

Why this persona fits the audience

He is the backend owner on a 12-person B2B startup in Utrecht and instruments customer forms, API callbacks, and internal automation endpoints. He currently keeps the numbers in Postgres and exports them to a spreadsheet for product reviews.

  • Age: 35
  • Location: Utrecht, Netherlands
  • Occupation: Backend engineer
  • Income: €78k
  • Education: Master's degree in Computer Science
  • Company size: 12 employees
  • Years in role: 3.5 years
“"I don't mind building things from scratch, but I do mind when people call that 'innovation' just because they don't know how to Google."”

Moussa van de Veen's career trajectory has been defined by two constants: his aversion to clutter (both physical and digital) and his ability to spot inefficiencies others overlook. After graduating from TU Delft with a Master's in Computer Science, he briefly worked at a Berlin fintech before returning to the Netherlands to join a then-four-person startup as their first dedicated backend hire. Today, he manages all server-side operations for a SaaS platform serving mostly European logistics firms. His signature achievement was reducing API response times by 43% through a redesign he implemented over two weekends. However, his current frustration lies in the ad-hoc analytics pipeline. The company's rapid growth means his PostgreSQL-to-spreadsheet exports are now error-prone and time-consuming. He's considered switching to proper analytics tools but distrusts vendor lock-in and bristles at the idea of becoming a 'product's guinea pig.' Personal life similarly reflects his analytical nature: every brew recipe is version-controlled, his cycling routes are plotted with elevation maps, and he's developing a RESTful API for his smart home devices just to prove it's possible. Despite his pragmatic streak, he occasionally indulges in grandiose projects like building his own keyboard or tweaking WordPress themes for his sister's blog. Financial stability is important to him—a child of middle-class academics, he remembers family budget-squeezes during recessions. This informs his cautious approach to both personal spending and workplace decisions. His ideal scenario involves automating away 90% of his current work, leaving time for cycling trips and perfecting his beer recipes without corporate interruptions.

Background & daily life

A day in their life

6:15 AM – Up, coffee brewed precisely (30g beans to 500ml water), quick stretch. 6:45 AM – Bike to work in steady rain, checking his self-built weather dashboard app en route. 8:00 AM – Monitor overnight logs at his stand-up desk, noticing increased 5XX errors in the authentication service. 10:30 AM – Debugging session with the frontend engineer, where he insists on not 'papering over' symptoms with a quick fix. 1:00 PM – Quick lunch (usually kippenwrap) while catching up on Hacker News. 3:00 PM – Fighting with a pivot table export that won't sort correctly, muttering about needing proper analytics tools. 6:30 PM – Finally wraps up after finishing the API documentation he'd been putting off. 7:15 PM – Home, bike maintenance while listening to a database optimization podcast. 8:30 PM – Fermentation check on his latest experiment, a Belgian Dubbel. 9:45 PM – Code review replies before bed.

Lifestyle

Moussa lives in a compact but well-organized apartment he renovated himself, with a dedicated workspace that doubles as his cycling gear storage. He commutes by bike year-round, even in Dutch winter rain, and allows himself small luxuries like artisanal coffee and handmade cycling gloves. Health-wise, he's disciplined—the only indulgence is his Sunday beer-brewing sessions, which he documents meticulously. Financially conservative, he avoids debt and prefers quality over quantity in purchases. Socially, he maintains tight-knit circles: his college friends, a cycling club, and a rotating group of tech peers at local meetups.

Work life

As the sole backend owner, Moussa's days are a mix of firewall maintenance, API debugging, and fighting spreadsheets. The startup's B2B platform handles customer feedback through form submissions, but tracking these manually in Postgres-to-sheets exports is becoming untenable. He recently added a crude analytics script to monitor API callbacks, which helped catch a 12% error rate in payment processing. The team is small enough that he knows everyone's work patterns, which helps him optimize automation triggers. Pressures come from balancing ad-hoc feature requests with infrastructure stability. His workstation is meticulously arranged: three monitors, a mechanical keyboard, and a standing desk he built himself.

Relationships

Moussa's oldest friend is his engineering school roommate, now a data scientist in Amsterdam, who he meets for monthly dinners. His cycling club includes a mix of professionals and academics, though he finds their hobbyist technical discussions frustrating compared to work peers. He speaks weekly with his older sister, a high school teacher, who keeps him grounded about 'real-world' problems. At work, he's the de facto infrastructure mentor, though he sometimes resents having to explain basic concepts multiple times. His parents, both retired academics, occasionally visit from Eindhoven.

How they decide

Cautious and methodical, Moussa researches thoroughly but makes final calls quickly once his criteria are met. He prefers quantifiable data over anecdotal evidence but will trust a peer's gut feeling if they've proven reliable. Dislikes being pressured into decisions and avoids emotional pitches.

How they sound

Speaks in measured cadence with occasional sarcasm. Uses precise technical language but drops into blunt Dutch swearwords under stress. Avoids vague terms like 'maybe' or 'kinda'—prefers 'approximately 37%' or 'the third percentile'. Has a dry sense of humor but rarely initiates jokes. Pronounces English words with a slight Dutch accent (e.g., 'skedjuul' for schedule). Won't fake enthusiasm for anything.

Personality traits

  • Thrifty but not cheap
  • Prone to over-engineering solutions
  • Quietly opinionated about APIs
  • Enjoys quiet nights over socializing
  • Struggles to delegate tasks
  • Prepares for worst-case scenarios
  • Takes pride in self-hosted tools
  • Dislikes corporate jargon
  • Values direct communication
  • Neat to the point of obsession

Goals

  • Automate all manual reporting by Q3
  • Reduce API latency by 15% this year
  • Complete a solo summer cycling trip through Belgium
  • Upgrade his homebrew setup with a proper fermentation chamber
  • Learn Rust as a side project
  • Save for a down payment on a small tech-free cottage

Problems & frictions

  • Spreadsheet crawl-heavy reporting is slowing down iterations
  • Team requests compete with his need to refactor legacy code
  • Documentation lag means onboarding new folks is painful
  • Cyclocross training is hard to fit around 50-hour weeks
  • Choosing between open-source tools and commercial products
  • His self-hosted monitoring tools occasionally conflict with corporate security policies

Values

  • Technical precision
  • Control
  • Independence
  • Efficiency

Interests

  • Cycling
  • Databases
  • Live music
  • Minimalist design
  • Amateur beer brewing

Media habits

  • Reads Hacker News and Techmeme daily
  • Listens to podcasts during commutes (technical and music-focused)
  • Follows niche tech subreddits
  • Occasionally checks cycling news sites

Questions & answers

Moussa van de Veen’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Stealth Analytics (https://stealth.qleapventures.com) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

    Right now, my biggest hurdle is the manual work of maintaining our current analytics setup. I'd need something that could seamlessly replace my ad-hoc PostgreSQL-to-spreadsheet exports without introducing vendor lock-in. The REST API native aspect here is attractive—it would let me send custom server events directly, which aligns with how I already structure our business logic. Still, I'd want to test how easily it integrates with our legacy system on a small scale before committing. I'm not convinced I need unlimited sites, but the event ingestion flexibility could save me hours per week. That said, I'd need to see how the reporting features compare to what I'm already doing manually. Also, the pricing seems reasonable, but I'd want to start on the free tier to ensure it scales to my custom event needs without hidden costs. I'd be comfortable spending up to $14/month for a tool that truly simplifies my workflow, but not without proving itself first. My main concern is whether the system can handle our specific event customization without becoming another maintenance headache.
    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.