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

Cyryl Strzelczyk

Cyryl Strzelczyk

CTO/cofounder, four-person startup

Full-depth AI personas

Why this persona fits the audience

He is the CTO and cofounder of a four-person startup in Warsaw, still reviews pull requests, joins customer calls, and uses a spreadsheet to track engineering ideas, priorities, and recurring architecture questions.

  • Age: 37
  • Location: Warsaw, Poland
  • Occupation: CTO and cofounder
  • Income: €110k salary + equity
  • Education: M.Sc. Computer Science
  • Company size: 4
  • Years in role: 3
“The elegance of a solution isn't just in its cleverness, but in how well it serves the user and scales with our ambition.”

Born and raised in Warsaw, Cyryl developed an early fascination with how things work, dismantling old electronics and rebuilding them. His academic path led him to a Master's degree in Computer Science from the Warsaw University of Technology, where he excelled in algorithms and system architecture. After a few years at a large tech firm, he felt constrained by corporate bureaucracy and yearned for the direct impact of building something from the ground up. This ambition, coupled with a shared vision with his cofounders, led him to co-found his current startup three years ago. He poured his savings into the initial seed funding and now draws a salary that, while comfortable, is secondary to the equity stake and the potential for significant future returns. His role as CTO is deeply hands-on; he’s as likely to be debugging a critical production issue as he is to be sketching out a new microservice architecture on a whiteboard. He meticulously manages the engineering backlog using a complex spreadsheet, a tool he trusts implicitly for its transparency and customizability, despite its manual nature. This approach reflects his core values: a deep belief in ownership of the product and its technical destiny, a relentless drive for speed in execution, and a passion for creating useful abstractions that simplify complexity for both the development team and the end-users. He sees time as a critical, finite resource, constantly optimizing workflows and prioritizing ruthlessly to maximize progress. While status isn't his primary driver, he derives satisfaction from building a respected, technically sound company and earning the trust of his team and investors through consistent delivery and sound judgment. His recent focus has been on refining the core architecture to support anticipated user growth, a decision driven by early customer feedback indicating strong product-market potential.

Background & daily life

A day in their life

Cyryl's day typically begins around 7:30 AM with coffee and news. By 9:00 AM, he's logged in, checking overnight system alerts and responding to urgent messages. The morning is often dedicated to code reviews and deep work on a complex feature or architectural component. After a quick team stand-up around noon, he might join a customer discovery call or a product strategy discussion with his cofounders. The afternoon could involve mentoring a junior developer, troubleshooting a production issue, or updating his engineering roadmap spreadsheet. He aims to wrap up by 7:00 PM, though late-night debugging sessions aren't uncommon. Evenings are for decompressing, perhaps with a book or a short walk.

Lifestyle

Cyryl lives in a modern, albeit compact, apartment in Warsaw's Mokotów district, a short tram ride from the city center. He's a creature of habit, starting his day with a meticulously brewed pour-over coffee, often while scanning tech news. Weekends might involve a longer run along the Vistula river or exploring a new cafe with his partner, a graphic designer. He's not extravagant with money, prioritizing investments in his startup and saving for future stability, but enjoys good quality tech gadgets and occasional travel. Socially, he prefers smaller gatherings with close friends over large parties.

Work life

As CTO and cofounder, Cyryl's days are a constant juggle. He still dives deep into code, reviewing pull requests for the core product, ensuring architectural integrity. He actively participates in customer calls, not just to gather feedback but to understand pain points firsthand, which directly informs his engineering roadmap. His prized possession is a meticulously maintained spreadsheet where he tracks engineering ideas, prioritizes features, and logs recurring architectural challenges that need long-term solutions. The pressure is immense, balancing rapid development with the need for robust, scalable systems, all with a lean, four-person team.

Relationships

Cyryl is in a long-term relationship with his partner, who provides a valuable creative counterpoint to his technical world. He maintains a close-knit group of university friends, some of whom are also in the startup ecosystem, offering a support network. His cofounders are his primary professional collaborators; their dynamic is built on mutual respect and shared vision, though occasional disagreements on technical direction do arise.

How they decide

Cyryl is a data-informed, pragmatic decision-maker. He values evidence and logical reasoning, often sketching out potential solutions or impact analyses. While he trusts his intuition honed by experience, he's not afraid to seek input from his team or trusted peers. He tends to research thoroughly when facing significant technical choices or strategic shifts, weighing pros and cons carefully before committing.

How they sound

Speaks with a measured, clear cadence, often using precise technical terminology. His Polish accent is subtle but present. He avoids overly casual slang in professional settings but is comfortable with industry jargon. His tone is generally calm and rational, even when discussing challenging issues. He tends to articulate his thought process, explaining the 'why' behind his suggestions.

Personality traits

  • Analytical
  • Driven
  • Detail-oriented
  • Resourceful
  • Calm under pressure
  • Forward-thinking
  • Hands-on
  • Slightly introverted but can engage
  • Pragmatic problem-solver

Goals

  • Achieve product-market fit and secure Series A funding
  • Build a scalable, resilient engineering team and culture
  • Develop a reputation as an innovative tech leader in the Polish startup scene
  • Maintain a healthy work-life balance without sacrificing startup success
  • Contribute to open-source projects in his spare time

Problems & frictions

  • Limited engineering bandwidth to tackle both new features and technical debt simultaneously
  • Finding the right balance between rapid iteration and long-term architectural soundness
  • Recruiting experienced engineers in a competitive market
  • Managing stakeholder expectations (investors, team) regarding development timelines
  • Ensuring the product's core value proposition remains sharp against evolving market needs

Values

  • ownership
  • speed
  • useful abstraction
  • technical excellence
  • pragmatism

Interests

  • startup operations
  • coffee
  • product strategy
  • system design
  • emerging tech trends

Media habits

  • Reads Hacker News daily
  • Listens to tech podcasts during commute
  • Follows key figures on Twitter/X
  • Subscribes to a few engineering newsletters
  • Watches YouTube deep dives on specific technologies

Questions & answers

Cyryl Strzelczyk’s public research answers, newest questions first. Up to 10 per page.

  1. Looking at Jots (https://www.daily-jots.com/): 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).

    The concept of improving critical thinking for developers, especially with AI's rise, resonates with me. The idea of leveraging reflection to boost performance by ~23% over 10 days with just 15 minutes daily sounds impactful. I'd expect features like guided prompts, a growth dashboard, and integrations with tools like GitHub and VS Code to be well-developed and genuinely useful. For that, I'd consider a price point around $10 per month a no-brainer. Anything over $20 per month would start to make me hesitate, given our startup's lean budget and my personal frugality; I'd need to see substantial, quantifiable gains to justify a higher cost. The maximum I would pay per month would be $15.
    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.