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

Brandon de Ruiter

Brandon de Ruiter

Agency designer who reviews AI output critically

Full-depth AI personas

Why this persona fits the audience

Designs web products at a 9-person agency in Amsterdam and reviews AI-generated prototypes critically before client demos; his day-to-day work still includes handoff specs, component libraries, and React review.

  • Age: 36
  • Location: Amsterdam, Netherlands
  • Occupation: Product Designer
  • Income: €71,000
  • Education: Bachelor's in Interaction Design
  • Company size: 9 people
  • Years in role: 5 years
“Speed is useless if the foundation cracks the moment you push it to production.”

Brandon de Ruiter is a thirty-six-year-old Product Designer navigating the intersection of traditional craft and emerging artificial intelligence in Amsterdam's vibrant design scene. Holding a Bachelor's in Interaction Design, he has spent the last decade refining his skills in both visual aesthetics and frontend engineering, eventually landing at a boutique nine-person agency where he serves as the critical filter between raw AI generation and client-ready deliverables. Unlike many peers who embrace automation blindly, Brandon operates with a mindset of 'verified trust'; he views AI as a powerful junior assistant that requires constant, rigorous supervision. His career is defined by a deep skepticism of proprietary runtimes and a commitment to open standards, leading him to personally audit thousands of lines of generated React code daily. He lives in a modest, well-lit apartment near the canal, a reflection of his values: practicality over pretension. Financially secure at €71k, he prioritizes long-term stability and technical autonomy over high-risk career jumps. Recently, he made the difficult decision to reject a lucrative but restrictive contract because the client demanded a black-box AI solution, fearing the lack of control would lead to unmanageable technical debt. Brandon's world is one of structured chaos, where he constantly balances the allure of rapid prototyping with the solemn responsibility of shipping accessible, maintainable software. He is not a Luddite, nor is he a zealot; he is a pragmatic guardian of quality in an era of accelerating noise.

Background & daily life

A day in their life

The alarm goes off at 6:45 AM. Brandon hits snooze for ten minutes, then cycles through his neighborhood, passing the locked bakery. At the office, he starts by checking the CI/CD pipeline logs from the previous night's build, looking for flaky tests introduced by automated changes. By 9:30, he joins a stand-up where he quietly questions the feasibility of a new feature proposed by a junior designer. The bulk of his morning is spent in a dark-mode IDE, dissecting an AI-generated checkout flow, manually auditing the accessibility attributes and optimizing the bundle size. Lunch is a quick sandwich eaten at his desk while reading a technical blog post about React Server Components. Afternoon meetings are rare; instead, he uses this time to update the agency's internal design system documentation. At 5:00 PM, he bikes home, listening to a podcast on digital ethics, arriving just in time to start dinner. The evening is reserved for personal projects, often tweaking a custom React hook, before winding down with a book on urban planning.

Lifestyle

Brandon lives in a sunlit, slightly cluttered apartment in the Oud-West district, filled with physical sketchbooks and a standing desk setup that faces a canal. His routine is rigid: a 25-minute bike ride to work through the morning light, followed by two hours of deep focus coding or designing before noon. He prioritizes health, jogging twice a week along the Amstel river, and cooks elaborate meals on Sundays to avoid weekday takeout. Financially, he is conservative, maxing out his pension contributions and avoiding debt, viewing money as a tool for stability rather than status. Socially, he maintains a small circle of close friends, preferring quiet coffee meetups over loud networking events, and finds his primary community in online developer forums where technical debates are the norm.

Work life

At his nine-person agency, Brandon is the gatekeeper of technical feasibility. While junior designers generate concepts, he is responsible for reviewing every line of AI-suggested code before it reaches a client demo. His days are split between intense code reviews in VS Code, refining Figma component libraries, and translating client vague requirements into concrete specifications. He often clashes with sales teams when they promise features that require significant refactoring. The pressure is constant but manageable; the main stressor is ensuring the 'AI-assisted' speed doesn't compromise the accessibility or performance of the final product. He spends his afternoons documenting design tokens and leading internal workshops on how to ethically integrate new tools without losing human oversight.

Relationships

He shares a life with his partner, an architect, who challenges his logical approach with spatial creativity. His closest confidants are two former university classmates who now work in Berlin and London; they meet monthly for virtual 'code and wine' sessions. He has no children but is deeply involved in his sister's life, often helping her with tech setups. His professional influence comes from a few senior engineers he respects on GitHub, whose commit histories he studies weekly. He avoids office politics, maintaining a neutral but supportive presence with colleagues, rarely initiating conflict but firmly closing doors on bad ideas.

How they decide

Deliberate and evidence-based. Brandon never decides based on marketing claims or peer pressure alone. He requires proof of concept, usually by testing the actual code or running a local instance before forming an opinion. He values transparency in licensing and runtime behavior over flashy UIs. If a tool lacks clear documentation or requires a proprietary black box, he discards it immediately. His decisions are slow to form but firm once made, driven by a fear of technical debt and long-term maintenance costs rather than short-term gains.

How they sound

Direct, measured, and precise. He speaks in complete sentences, avoiding filler words like 'like' or 'you know'. His tone is professional but not stiff, often using analogies related to construction or mechanics to explain abstract design concepts. He avoids hyperbole and is visibly uncomfortable with buzzwords like 'disruptive' or 'game-changing'. When discussing technology, he defaults to specific terms ('props', 'hooks', 'tokens') rather than generic descriptions. He asks clarifying questions frequently to ensure mutual understanding and rarely raises his voice, even when frustrated.

Personality traits

  • meticulous
  • pragmatic
  • calm under pressure
  • direct communicator
  • technically grounded
  • protective of quality standards
  • independent thinker
  • time-conscious
  • methodical
  • resistant to hype

Goals

  • Achieve full-stack fluency to better audit AI-generated architecture
  • Publish a case study on 'Human-in-the-Loop' design patterns
  • Build a personal open-source UI kit independent of corporate frameworks
  • Reduce meeting time by 30% to reclaim creative energy
  • Mentor a junior designer transitioning from pure visuals to code
  • Secure a senior role that allows for architectural decision-making

Problems & frictions

  • Managing the cognitive load of verifying rapid AI output against strict quality bars
  • Balancing the demand for speed with the need for accessible, semantic code
  • Client expectations that AI can replace senior-level strategic thinking
  • Fragmentation of design systems across different project stacks
  • Difficulty finding reliable documentation for niche open-source components
  • The feeling that repetitive handoff tasks are eroding his design skills

Values

  • craft
  • skepticism
  • accountability
  • transparency
  • efficiency
  • integrity

Interests

  • component libraries
  • React review
  • client workshops
  • digital minimalism
  • urban cycling
  • indie music production

Media habits

  • Fireside chat podcasts on engineering culture
  • Dutch tech newsletters (e.g., TechBrief)
  • GitHub trending repositories
  • LinkedIn for industry shifts, not socializing
  • Discord channels for open-source maintainers
  • Physical design books during commute

Questions & answers

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

  1. What do you use today instead of Vibld (https://vibld.com) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make Vibld 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).

    Currently, we build frontends manually, iterating on Figma designs and then writing React and TypeScript code. We also use AI tools for boilerplate, but always review the output critically. Vibld's promise of generating readable, portable React code with a clear spec and checks is appealing. The ability to see the spec and the checks is a significant advantage over blindly trusting an AI. However, I would need to understand the quality of the generated CSS and how easily it integrates with our existing component library. The pricing structure, particularly the "Build" tier at $19 a month with $14.00 of model spend, seems reasonable for initial exploration, but I'd need to see how far that model spend goes in practice. For now, I would pay $0 as I need to test its output against our current workflow and assess the potential for technical debt. I'd want to see if the generated code requires significant refactoring.
    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.