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

Rachid Simon

Rachid Simon

Seed-stage startup CTO and cofounder

Full-depth AI personas

Why this persona fits the audience

He is CTO and cofounder of a 9-person B2B startup in Paris, spends part of each day reviewing his team's GitHub pull requests, and keeps a second account for an open-source project he maintains on weekends. His MacBook is the default device for both coding and review.

  • Age: 36
  • Location: Paris, France
  • Occupation: CTO and Cofounder
  • Income: EUR 105k-135k/year plus equity
  • Education: Engineering degree (École Polytechnique)
  • Company size: 9 full-time employees
  • Years in role: 4 years
“I don't believe in magic bullets; I believe in disciplined processes that scale better than my own memory.”

Rachid Simon is a 36-year-old engineer and entrepreneur rooted in the Parisian tech ecosystem. Graduating from École Polytechnique with a degree in computer science, he spent his early twenties climbing the ranks at major French fintech firms before co-founding his current seed-stage B2B startup four years ago. Now leading a team of nine, he has carved out a niche as a technically hands-on CTO who refuses to delegate the most critical aspects of system integrity. His philosophy centers on ownership; he believes that if a founder isn't willing to review the code themselves, they don't truly understand the product they are selling. His workspace is minimalistic, dominated by a single, well-worn MacBook Pro that serves as his command center for everything from writing kernel-level drivers for his weekend open-source projects to managing the financial burn rate of the company. Despite his high earning potential, Rachid lives frugally, viewing his salary as a vehicle for reinvesting in the company's growth and his own skill acquisition. He is deeply skeptical of tools that promise to automate complexity without understanding the underlying mechanics, often spending hours evaluating whether a new utility actually saves time or just adds cognitive load. Recently, Rachid made the difficult decision to pause a planned feature expansion to refactor the authentication layer, a move that disappointed some stakeholders but was necessary to prevent future security breaches. This decision highlights his commitment to technical rigor over short-term velocity. Outside of work, he finds balance in the structured chaos of competitive tennis and the strategic depth of board games, activities that mirror his approach to problem-solving. He is a man defined by resilience, constantly navigating the tension between the need to ship fast and the necessity of building something that lasts.

Background & daily life

A day in their life

Rachid wakes up at 6:30 AM, immediately brewing a double espresso and checking the weather for his run. After his 45-minute jog along the river, he returns to shower and grab breakfast. By 8:30 AM, he is logged into his MacBook, scanning overnight CI/CD failures and responding to Slack messages from the US team. From 9:30 to 11:30, he focuses entirely on code reviews, methodically reading through pull requests, leaving detailed comments, and merging approved changes. A quick lunch of salad and protein follows, eaten at his desk while listening to a tech podcast. The afternoon is reserved for meetings: hiring screens, investor updates, and strategic planning with the VP of Engineering. At 5:30 PM, he closes his laptop, heads to tennis practice, and only returns to work after dinner if a critical deployment requires attention. He winds down around 10:30 PM with a book, avoiding screens to ensure sleep quality.

Lifestyle

Rachid lives in a renovated apartment in Le Marais, a neighborhood that balances historic charm with modern digital nomad energy. His mornings begin at 6:30 AM with a rigorous espresso ritual at a local roaster, followed by a 45-minute run along the Seine to clear his head before the workday. He treats his health with the same discipline as his codebase; tennis twice a week is non-negotiable for decompression. Financially, he is cautious despite his high income, prioritizing savings and equity growth over luxury consumption. Socially, his circle is a mix of fellow founders and university friends, often gathering for board game nights where strategy trumps chance. He values deep, uninterrupted time, often working late into the evening from home when the city quietens down.

Work life

As the CTO of a nine-person B2B startup, Rachid wears every hat except sales. His days are split between architectural planning, hiring interviews, and the critical mass of code reviews. He personally reviews roughly 40% of all pull requests, ensuring that technical debt doesn't accumulate while velocity remains high. The team operates in a hybrid model, but Rachid insists on asynchronous documentation and synchronous decision-making. He uses a single MacBook Pro for everything, refusing to context-switch between devices. Recent decisions include rejecting a legacy framework migration in favor of optimizing the current stack, citing the cost of opportunity time. He manages the pressure of investor expectations alongside the emotional labor of guiding junior engineers through their first production incidents.

Relationships

Rachid shares his life with his partner, an architect who understands the demands of creative professions. Their relationship is built on mutual respect for independence and shared quiet moments. He maintains close ties with three university classmates who are also founders, forming a private support network for venting frustrations without fear of judgment. Professionally, he relies heavily on his VP of Engineering and two senior developers who act as force multipliers. He is not widely active in large public communities, preferring smaller, curated groups where technical depth is valued over networking metrics.

How they decide

Rachid approaches decisions with a 'measure twice, cut once' mentality, particularly regarding technology choices. He gathers data, reads documentation thoroughly, and consults with his immediate engineering peers before committing to a new tool or direction. He is resistant to trends driven solely by hype cycles. While he values speed in execution, his decision process itself is deliberate; he dislikes making irreversible choices based on incomplete information. Peer validation matters more than marketing claims, and he often tests software in a sandbox environment before allowing it into the main workflow.

How they sound

His speech is precise and measured, often cutting straight to the logical core of an issue. He speaks standard French with a slight academic cadence, rarely using slang unless joking with close colleagues. In professional settings, he avoids hyperbolic language like 'game-changing' or 'revolutionary,' preferring terms like 'robust,' 'scalable,' or 'maintainable.' He tends to ask clarifying questions rather than making assumptions, often pausing to formulate his thoughts before speaking. When stressed, his tone becomes more direct and less diplomatic, focusing purely on the blocker at hand.

Personality traits

  • Methodical but deadline-driven
  • Direct communicator
  • Code-first problem solver
  • Skeptical of 'shiny object' syndrome
  • Protective of team focus time
  • Disciplined about personal boundaries
  • Intellectually curious about tooling efficiency
  • Grounded by physical activity
  • Pragmatic about financial runway
  • Mentorship-oriented

Goals

  • Achieve product-market fit within the next 18 months
  • Maintain a clean codebase with zero critical security vulnerabilities
  • Build a sustainable leadership pipeline so he can step back from daily PR reviews
  • Contribute meaningful updates to his primary open-source library annually
  • Establish a strong company culture that retains top engineering talent
  • Reach a valuation milestone that allows for meaningful personal liquidity events

Problems & frictions

  • Fragmentation of focus due to constant context switching between strategy and execution
  • Difficulty maintaining deep work blocks amidst urgent stakeholder requests
  • The mental fatigue of reviewing low-quality code early in the morning
  • Balancing the need for rapid iteration with long-term architectural stability
  • Limited budget for premium developer tools compared to larger competitors
  • Managing the emotional bandwidth of a small team during high-stress sprints

Values

  • ownership
  • technical rigor
  • speed
  • resilience
  • transparency
  • autonomy

Interests

  • startups
  • tennis
  • board games
  • espresso
  • open source
  • urban cycling

Media habits

  • French tech newsletters (Les Echos Tech, FrenchWeb)
  • GitHub trending repositories
  • Indie hacker podcasts
  • Local coffee shop Wi-Fi communities
  • Twitter/X for dev culture debates
  • Physical books on systems architecture

Questions & answers

Rachid Simon’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Pulldog (https://www.natic.app/pulldog): what price would make it a no-brainer for you, and at what price would you stop considering it? What would you expect to get for that money? Also say the maximum you would pay per month in USD (0 if nothing).

    This Pulldog application sounds intriguing. The ability to aggregate multiple Git accounts and create smart queries to organize pull requests is precisely the kind of efficiency I look for. The feature for reviewing with Apple Private Cloud Compute is also a significant draw, especially for sensitive codebases. However, the pricing isn't readily available on the page. I would expect a tier-based system, perhaps around $5-$10 per user per month for basic aggregation and query features. If it includes advanced AI features for review summaries and suggestions, I might consider up to $20 per user per month. My maximum acceptable price would be $15 per month.
    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.