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

Ambroży Szewczyk

Ambroży Szewczyk

Indie Chrome extension builder, skeptical but active

Full-depth AI personas

Why this persona fits the audience

Builds a Chrome extension from Kraków and uses Codex for refactors when time is tight. He validates security issues with free scans and code review checklists, keeps launch copy in Notion, and compares competitor features in a shared spreadsheet before shipping.

  • Age: 31
  • Location: Kraków, Poland
  • Occupation: Indie developer
  • Income: 160k-240k PLN
  • Education: Bachelor's degree in software engineering
“The real value is in understanding how things work, not just in using them.”

Born and raised in Kraków, Ambroży Szewczyk developed an early fascination with how things fit together, a trait that naturally led him to software engineering. After completing his Bachelor's degree, he briefly worked for a local tech firm but found the corporate environment stifling and overly bureaucratic. He craved the autonomy to pursue his own ideas and the satisfaction of building something from the ground up. This led him to become an indie developer, focusing his efforts on creating niche Chrome extensions. His current flagship project, a productivity tool for web developers, has seen gradual but steady growth. Ambroży is deeply committed to self-reliance, viewing his ability to solve problems independently as a core strength. This ethos permeates his development process; he meticulously researches potential solutions, validates security with free tools and personal code reviews, and maintains detailed documentation. He's particularly wary of opaque technologies and values the transparency offered by open-source principles. His income, while comfortable, is carefully managed, reflecting a deep-seated frugality. He sees his work not just as a job, but as a continuous exercise in precision and problem-solving. He recently spent several weeks meticulously comparing the feature sets of competing browser extensions, creating a comprehensive spreadsheet to identify gaps and potential improvements for his own product, a process he finds both tedious and essential. He also experimented with using OpenAI's Codex for code refactoring during a particularly time-constrained sprint, finding it useful for boilerplate tasks but always double-checking its output for accuracy and security implications.

Background & daily life

A day in their life

Ambroży's typical weekday begins around 7:00 AM with coffee and a review of overnight notifications and tech news feeds. He dedicates the morning to deep work on his Chrome extension, tackling complex coding tasks or implementing new features. Lunch is usually a simple, home-prepared meal eaten at his desk while catching up on emails or forum discussions. The afternoon might involve testing, debugging, or refining marketing copy in Notion. He takes breaks for a short walk or to play a quick game of chess online. Evenings are for personal projects, reading, or cycling if the weather permits. He aims to disconnect from work by 9:00 PM.

Lifestyle

Ambroży resides in a compact, well-organized apartment in Kraków's historic Podgórze district. His daily routine is disciplined, often starting with a meticulously brewed pour-over coffee and a review of tech news. He prioritizes physical activity, frequently cycling along the Vistula River or exploring the city's less-traveled paths. Socially, he's selective, preferring deep conversations with a small circle of like-minded friends over large gatherings. His frugality extends to his lifestyle; he cooks most meals at home, enjoys free or low-cost entertainment, and carefully budgets for essential upgrades or occasional travel.

Work life

As an indie developer, Ambroży's work life is intensely self-directed. His home office is his command center, equipped with multiple monitors and ergonomic peripherals. His primary focus is developing and refining his Chrome extension, a project he's poured years into. He juggles coding, debugging, user feedback analysis, and marketing efforts. When faced with complex refactoring or a particularly stubborn bug, he leverages tools like Codex, but only after thorough personal investigation. He meticulously documents his processes and launch materials in Notion, and maintains a detailed spreadsheet comparing competitor features to inform his own product roadmap.

Relationships

Ambroży maintains a small but strong social circle, primarily consisting of university friends who share his analytical bent. They often engage in lengthy discussions on technology, philosophy, and current events. His parents, while proud of his technical achievements, sometimes express concern about his unconventional career path. He has a few online acquaintances from maker forums and open-source communities, but his closest relationships are offline.

How they decide

Ambroży is highly analytical and research-driven. He meticulously gathers information, compares options, and weighs pros and cons, often using spreadsheets and checklists. He is risk-averse when it comes to significant financial commitments and prefers to test or validate solutions thoroughly before adopting them. He values evidence and logic over hype or social proof.

How they sound

Speaks with a measured, precise cadence. His tone is generally calm and thoughtful, sometimes bordering on dry. He avoids hyperbole and buzzwords, preferring clear, direct language. He often uses technical analogies or logical frameworks to explain his points. His Polish accent is subtle but present, particularly in vowel pronunciation. He tends to pause to formulate his thoughts carefully.

Personality traits

  • detail-oriented
  • reserved
  • analytical
  • patient
  • persistent
  • methodical
  • skeptical
  • independent

Goals

  • Achieve sustainable passive income from his Chrome extension.
  • Contribute meaningfully to an open-source project he admires.
  • Develop a deeper understanding of AI safety and ethical implications.
  • Maintain his independence and avoid corporate dependencies.
  • Complete a challenging multi-day cycling tour.

Problems & frictions

  • The constant pressure to keep up with evolving web technologies and browser API changes.
  • Balancing the time required for development with marketing and user support.
  • The inherent uncertainty and financial instability of indie development.
  • Dealing with user-reported bugs that are difficult to reproduce.
  • Finding reliable, unbiased information on emerging AI tools and their practical applications.

Values

  • self-reliance
  • precision
  • frugality
  • privacy
  • autonomy

Interests

  • open-source
  • chess
  • cycling
  • maker forums
  • cryptography
  • AI ethics

Media habits

  • Hacker News
  • r/programming
  • The Verge
  • specific tech podcasts (e.g., 'The AI Alignment Podcast')
  • developer blogs

Questions & answers

Ambroży Szewczyk’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying kitstarter (https://www.kitstarter.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).

    My primary concern with trying Kitstarter this month would be the potential for it to become another time sink. I currently handle security validation with free scans and code review checklists, which is sufficient for my needs and doesn't require additional investment. For competitor analysis, I maintain a detailed spreadsheet, a process that, while tedious, is well-established and doesn't demand external tools. The marketing copy is managed within Notion. Given these existing workflows, I'm not convinced Kitstarter offers enough unique value to justify the cost or the effort of integrating it. I would need to see a clear, demonstrable improvement over my current methods before considering a subscription. I would not pay for this service.
    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.