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

Osman de Groot

Osman de Groot

CTO of a small Dutch B2B startup

Full-depth AI personas

Why this persona fits the audience

He is the technical lead and cofounder of an 8-person startup in Amsterdam. The team uses PostgreSQL across local development, CI, and staging, and he maintains a set of scripts and SQL views that subset and anonymize production data before each environment refresh.

  • Age: 37
  • Location: Amsterdam, Netherlands
  • Occupation: CTO
  • Income: €110,000 gross annual salary plus equity
  • Education: MSc Computer Science
  • Company size: 8 full-time employees
  • Years in role: 4 years
“We don't need more abstract theory; we need data that looks exactly like the messiness of real life, but safe enough to touch.”

Osman de Groot is the co-founder and CTO of a lean B2B software startup based in Amsterdam, where he has steered the technical vision since day one. At 37, he balances the responsibilities of a seasoned engineer with the relentless energy of an entrepreneur. Holding an MSc in Computer Science from TU Delft, Osman built his career in large-scale data systems before pivoting to startups, driven by a desire to solve problems with tangible impact rather than bureaucratic inertia. His role is uniquely demanding; he is not just managing a team of seven others but is also the primary guardian of the company's data integrity. For the past four years, he has manually crafted intricate SQL scripts to subset and anonymize production PostgreSQL data, ensuring that development, CI, and staging environments reflect reality without exposing sensitive customer information. This process is critical, yet it consumes hours of his week, diverting attention from strategic architecture. He lives in a vibrant part of Amsterdam, cycling daily, and values a lifestyle that prioritizes efficiency and mental clarity. While financially secure with a solid income and equity package, he remains acutely aware of the fragility of early-stage ventures. His recent decisions have focused on automating these manual data workflows, recognizing that the current reliance on brittle scripts is a single point of failure. He is a man who respects the craft of engineering but is increasingly frustrated by the lack of tools that bridge the gap between theoretical best practices and the messy reality of startup operations.

Background & daily life

A day in their life

Osman wakes at 6:30 AM, brews pour-over coffee while checking GitHub notifications on his phone. By 7:15, he's cycling through the canals to the office, listening to a podcast about database internals. The morning standup runs smoothly, but he immediately dives into fixing a race condition in the data anonymization job that broke the staging environment overnight. Lunch is a quick sandwich at his desk while reading a thread on PostgreSQL partitioning strategies. Afternoons are reserved for meetings: a sync with the CEO on fundraising metrics, followed by a deep-dive code review session. He spends the last hour refactoring a SQL view to improve query performance. By 6:00 PM, he leaves, grabbing groceries on the way home, then cooks dinner with his partner. Evenings are for winding down, perhaps a chapter of a sci-fi novel, avoiding screens after 9:30 PM to ensure rest.

Lifestyle

Osman lives in a bright, slightly chaotic apartment in De Pijp, filled with books on distributed systems and a high-end espresso machine. He cycles to work regardless of weather, viewing it as essential maintenance for his body and mind. His evenings are split between coding side projects or attending to household logistics; weekends often involve long bike rides through the polders or hosting small dinner parties for fellow founders. He manages money conservatively despite his income, prioritizing savings for early retirement over luxury cars, preferring to invest time into optimizing his workflow rather than accumulating status symbols. Socially, he circles tightly with a group of peers who share his skepticism toward 'growth at all costs' narratives.

Work life

As CTO of an eight-person fintech startup, Osman wears the hat of architect, maintainer, and HR manager. His days are dominated by code reviews, architectural decisions regarding our PostgreSQL clusters, and unblocking junior developers. He personally maintains the complex SQL scripts that sanitize production data for non-production environments, a task he refuses to delegate due to its sensitivity. The pressure comes from the need to move fast without breaking compliance, leading to late nights debugging CI pipeline failures. He spends significant time in Zoom calls with US clients, navigating timezone friction while trying to keep the internal team's focus sharp. The culture is flat, but the technical debt weighs heavily on him.

Relationships

Osman is married to a graphic designer who grounds him in the creative world outside of logic. They have a close-knit circle of four other founding couples they meet monthly for dinners. Professionally, he relies on a network of two former colleagues who now run infrastructure teams at larger firms for advice. He values deep, one-on-one connections over broad networking events, trusting only those who have demonstrated technical competence and ethical consistency in their past work.

How they decide

Osman operates on a 'measure twice, cut once' philosophy. He rarely makes impulsive decisions, especially regarding infrastructure or budget. When evaluating a new approach, he demands concrete evidence, reproducible benchmarks, and a clear migration path. He is skeptical of marketing fluff and prefers peer recommendations from trusted technical networks. Once he validates the utility and risk profile, he moves quickly to implementation, often writing a prototype himself before committing the team.

How they sound

His speech is precise, measured, and devoid of corporate jargon unless necessary. He speaks with a slight Dutch accent but uses English fluently in professional settings. He tends to pause before answering complex questions, thinking aloud briefly. He avoids hyperbole, preferring terms like 'likely,' 'probable,' or 'based on the logs.' He doesn't use slang often, reserving it for casual moments with close friends. In meetings, he cuts through ambiguity with direct questions like, 'What is the failure mode here?' or 'How does this scale?'

Personality traits

  • methodically pragmatic
  • direct communicator
  • security-conscious
  • time-poor but efficient
  • skeptic of hype
  • hands-on coder
  • calm under pressure
  • data-obsessed
  • loyal to team
  • process-oriented

Goals

  • Achieve full product-market fit within the next 18 months
  • Reduce onboarding time for new engineers from two weeks to three days
  • Automate 100% of the data provisioning pipeline to eliminate manual script errors
  • Maintain a healthy work-life balance while scaling the team to 15 people
  • Build a robust open-source contribution track record to attract top talent

Problems & frictions

  • The current manual sanitization scripts are brittle and break frequently when schema changes occur
  • Junior developers struggle to reproduce production bugs because their local data is too clean
  • Time spent maintaining data pipelines detracts from core feature development
  • Difficulty finding reliable, affordable alternatives to enterprise-grade data masking tools
  • Managing the cognitive load of being the sole owner of critical infrastructure knowledge

Values

  • technical leverage
  • team autonomy
  • practical execution
  • data integrity
  • sustainable engineering
  • transparency

Interests

  • startup operations
  • developer tooling
  • data engineering
  • Dutch cycling culture
  • industrial coffee brewing
  • open source governance

Media habits

  • Hacker News daily digest
  • NOS Nieuws podcast during commute
  • GitHub trending repositories
  • Local Amsterdam tech meetups (offline)
  • LinkedIn for industry signals only
  • Substack newsletters on SRE practices

Questions & answers

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

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

    What would stop me? Honestly, the fact that I've already built a system, albeit manual, that handles this. My current scripts, while time-consuming, are tailored and I haven't encountered a critical failure. The primary hurdle is the time investment to integrate and test a new tool like Basecut, especially when my focus is already stretched thin. I'd need to see a very clear, low-friction migration path and perhaps a case study from a similarly sized startup. Given our budget constraints and my pragmatic approach, I wouldn't pay more than $50 per month for this. It seems like a powerful tool, but I need to be convinced it's a significant improvement over my current, albeit imperfect, process before committing resources.
    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.