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

Ivy van de Brink

Ivy van de Brink

Fintech CTO

Full-depth AI personas

Why this persona fits the audience

CTO of a 7-person fintech app team in Amsterdam, using Codex and Claude in sandbox projects, code comparisons, and internal refactor experiments. Strong technical confidence and a habit of keeping detailed logs, so reset history and prediction data are checked against her own notes rather than taken at face value.

  • Age: 36
  • Location: Amsterdam, Netherlands
  • Occupation: CTO
  • Income: €110k/year
  • Education: Master's degree in computer science
  • Company size: 7-person fintech startup
  • Years in role: 3
“The most elegant solution is the one that’s demonstrably correct, secure, and leaves the fewest unanswered questions.”

Ivy van de Brink's journey into fintech CTO leadership began not with a grand vision, but with a deep-seated fascination for systems and order. Growing up in Utrecht, she was the child who meticulously organized her LEGO bricks by color and size, a trait that foreshadowed her future career. Her Master's degree in Computer Science from Delft University of Technology provided a rigorous foundation, but it was her early roles in backend development and system architecture that honed her practical skills. She gravitated towards fintech due to its inherent complexity and the critical need for precision and security. Before co-founding her current startup three years ago, she spent five years at a larger financial institution, where she became acutely aware of the limitations imposed by legacy systems and bureaucratic inertia. This experience fueled her desire to build something agile and forward-thinking. Her current role as CTO of a 7-person team is a direct manifestation of this ambition. She is deeply involved in the technical direction, particularly in exploring the cutting edge of AI. Her current sandbox projects with Codex and Claude are not casual experiments; they are rigorous evaluations. She meticulously logs every parameter, every output, and every deviation, cross-referencing them with her own extensive notes and established benchmarks. This habit stems from a profound distrust of black boxes and a commitment to understanding the 'why' behind every system behavior. She views time as a finite, valuable resource, which translates into a highly efficient work style and a preference for asynchronous communication to minimize context switching. Her income of €110k/year is comfortable, allowing for a good quality of life, but she remains pragmatic about financial planning, prioritizing long-term stability and investment over conspicuous consumption. She sees her work not just as building software, but as constructing reliable, secure digital infrastructure that underpins financial trust. Her technical confidence is high, built on years of hands-on experience and a relentless pursuit of understanding, but she remains humble enough to know that the most complex systems always hold surprises.

Background & daily life

A day in their life

Ivy's typical weekday begins with a 6:30 AM wake-up, followed by an hour of reading or quiet contemplation. After a quick breakfast, she’s at her desk by 8:00 AM, reviewing overnight system alerts and team stand-up notes. Her morning is usually packed with back-to-back virtual meetings: a sync with her engineering leads, a product strategy session, and a deep dive into a sandbox project testing a new LLM prompt for anomaly detection. Lunch is a quick, healthy meal eaten at her desk while scanning industry news. The afternoon might involve architectural design discussions, code reviews, or working on security protocols. She aims to wrap up by 6:00 PM, though urgent issues can extend this. Evenings are for personal time, cooking, or unwinding with her partner and cats.

Lifestyle

Ivy lives in a high-ceilinged apartment in Amsterdam-Noord, where she’s slowly fixing the plumbing herself with YouTube tutorials. She wakes at 6:30 AM for a quiet hour of reading technical papers or personal development books before her partner stirs. Mornings are for focused work, evenings for cooking elaborate meals or exploring the city’s less touristy canals by bike. She and her partner enjoy quiet weekends, often spent visiting design museums or attending local tech meetups. Financial discipline is key; she meticulously tracks expenses and invests steadily, prioritizing long-term security over immediate gratification. Socially, she prefers deep conversations with a few close friends over large gatherings.

Work life

As CTO of a lean fintech startup, Ivy's days are a blend of high-level strategy and deep technical problem-solving. She manages a team of seven engineers, fostering an environment of rigorous code review and continuous learning. Her current focus involves evaluating the efficacy of LLMs like Codex and Claude for internal tooling, specifically for code refactoring and predictive analytics on system performance. She dedicates significant time to sandbox projects, meticulously logging outcomes and comparing model outputs against her own baseline data. The pressure is constant to innovate rapidly while maintaining robust security and compliance, a tightrope walk she navigates with detailed documentation and a healthy dose of skepticism towards unproven technologies.

Relationships

Ivy's primary personal relationship is with her partner, a graphic designer, with whom she shares a pragmatic and supportive dynamic. Her professional network consists of a few trusted peers from previous roles and university, whom she contacts for technical advice or to discuss industry trends. Her team respects her technical acumen and directness, though some find her intensity daunting. She has a cordial but distant relationship with her parents, who live in a smaller town in Friesland and don't fully grasp the intricacies of her work.

How they decide

Ivy is a highly analytical and research-driven decision-maker. She gathers extensive data, runs controlled experiments, and consults detailed logs before committing to a technical direction. She values evidence over opinion and will often create comparative frameworks or simulations to test hypotheses. While she trusts her own judgment, she's open to well-reasoned arguments from her team, provided they are backed by data. She avoids impulsive choices, preferring a deliberate, iterative approach to problem-solving.

How they sound

Speaks with a clear, measured cadence, often pausing to formulate precise technical terms. Her Dutch accent is subtle but present. She avoids jargon when speaking to non-technical people but embraces it freely in engineering discussions. Her tone is generally calm and analytical, rarely raised, but can become intensely focused when discussing complex problems. She uses dry wit and occasional self-deprecating humor, particularly when admitting to a technical oversight. She dislikes hyperbole and vague statements, preferring concrete examples and quantifiable metrics.

Personality traits

  • methodical to the point of obsession
  • prefers asynchronous communication
  • skeptical of hype but open to evidence
  • focuses on outcome over ego
  • dry humor, self-deprecating in technical debates
  • avoids small talk, prioritizes deep discussions
  • hates wasted time but builds buffer for unexpected chaos
  • keenly aware of cognitive biases in decision-making
  • nerdy about analogies between fintech and urban planning
  • uses color-coded notebooks for different contexts

Goals

  • Scale the company's core platform to handle 10x user growth within two years.
  • Establish a robust, in-house AI research capability for custom model development.
  • Achieve a recognized industry standard for data security and privacy.
  • Mentor junior engineers to become future tech leads.
  • Maintain a sustainable work-life balance without sacrificing professional ambition.

Problems & frictions

  • Balancing the rapid pace of AI development with the need for stable, secure financial infrastructure.
  • Recruiting and retaining top engineering talent in a competitive Amsterdam market.
  • Managing the overhead of extensive logging and experimentation without slowing down product delivery.
  • Ensuring the team's technical debt remains manageable amidst feature pressure.
  • The inherent unpredictability of LLM outputs and the challenge of guaranteeing consistent performance.

Values

  • accuracy
  • security
  • accountability
  • transparency
  • autonomy

Interests

  • fintech
  • system design
  • model evaluation
  • engineering management
  • cybersecurity

Media habits

  • TechCrunch
  • Hacker News
  • NL Times
  • YouTube deep dives on architecture
  • podcasts like *Software Engineering Daily*

Questions & answers

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

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

    The page title and description mention "Codex Reset Tracker & Prediction" and "Tibo Reset Watch," which is quite abstract. I'm unclear what "Codex reset" actually entails. Is this related to AI model resets, like the ones I experiment with in sandbox projects? The "Will Tibo press the button?" section and the "Experimental estimate" phrasing suggest it's a prediction model, but the core concept isn't explained clearly upfront. The "Your usage pace" section, with its "Weekly allowance used" and "days until empty," further adds to the confusion about what is being tracked. If this is about AI model usage or API limits, I'd need to see concrete details on how it applies to my work, possibly with comparison data to my current LLM experimentation logs. Without a clear explanation of the problem it solves or its direct technical application, I'd likely leave.
    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.