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

Izaak Wojtczak

Izaak Wojtczak

skeptical backend engineer at tiny product team

Full-depth AI personas

Why this persona fits the audience

Works on a 2-person remote product team maintaining a marketplace add-on for Docs users in HR and legal. He is the only backend engineer and keeps auth, database migrations, and billing wiring in a hand-rolled starter repo.

  • Age: 26
  • Location: Warsaw, Poland
  • Occupation: Senior backend engineer
  • Income: PLN 240k
  • Education: MSc Computer Science
  • Company size: 2
  • Years in role: 3
“If you can't explain the failure mode of your system in a single sentence, you haven't designed it yet.”

Izaak Wojtczak is a 26-year-old Senior Backend Engineer based in Warsaw, Poland, operating at the intersection of high-performance architecture and the gritty reality of startup maintenance. Holding an MSc in Computer Science from the University of Warsaw, he quickly distinguished himself not just for his coding speed, but for his obsessive attention to system integrity. Currently, he serves as the solitary backend pillar for a two-person remote team developing a niche Google Workspace add-on targeting HR and legal departments. This unique constraint forces him to wear every hat imaginable, personally managing authentication flows, database migrations, and complex billing integrations within a hand-rolled starter repository he built years ago. Despite his young age and high income (PLN 240k), Izaak carries a burden of responsibility that belies his size. He is deeply skeptical of 'batteries-included' solutions that hide complexity behind opaque abstractions, a trait that often slows his adoption of new tools but ensures robust long-term stability. His professional life is defined by a relentless pursuit of efficiency and technical consistency; he believes that technical debt is the ultimate enemy of scalability. Recently, he made the difficult decision to refactor his entire authentication layer to comply with newer security standards, a project that consumed weeks of unpaid overtime because he refused to cut corners. Outside of work, Izaak is a man of quiet habits. He lives alone, finds solace in the rhythm of long-distance running along the Vistula, and views his financial independence as a means to buy autonomy rather than status. He is a pragmatist who trusts code over promises, often spending weekends auditing open-source libraries for potential vulnerabilities. While he possesses the skills to lead a large engineering team, he currently prefers the control and clarity of a small, focused scope, fearing the chaos of organizational politics more than the stress of technical problems.

Background & daily life

A day in their life

Izaak wakes up at 6:30 AM, avoiding the rush hour traffic in Warsaw by starting early. After a quick breakfast of oatmeal and black coffee, he spends thirty minutes reviewing GitHub notifications and checking the status of overnight build pipelines. By 8:00 AM, he is logged into his terminal, tackling the most complex technical task of the day, usually involving a stubborn OAuth token refresh issue or a database schema migration. Lunch is a solitary affair, often eaten while reading a chapter of a systems engineering book or listening to a podcast about distributed databases. In the afternoon, he shifts to lighter tasks: updating documentation, writing unit tests, or responding to asynchronous messages from his co-founder. He ends his workday at 5:00 PM sharp, disconnecting from Slack and closing his laptop to ensure a clear boundary. Evenings are reserved for physical activity or coding personal projects unrelated to his job, ensuring he doesn't burn out on his employer's codebase.

Lifestyle

Living alone in a modernized apartment in Warsaw's Wola district, Izaak maintains a strict separation between work and rest despite the remote nature of his job. His evenings are dedicated to optimizing his home office setup, often upgrading mechanical keyboards or monitor arms based on ergonomic research rather than trends. He is financially disciplined, channeling his high income into index funds and savings rather than luxury goods, viewing money as a tool for future security and freedom. Socially, he prefers one-on-one coffee meetups with close friends or small gaming nights over large gatherings, valuing depth in conversation over breadth. He runs three times a week along the Vistula river, a ritual that clears his head from the constant stream of server logs and API endpoints he manages daily.

Work life

As the sole backend engineer for a two-person startup, Izaak bears the full weight of the system's stability, handling everything from authentication protocols to Stripe webhook reconciliation without a safety net. His workspace is a dual-monitor rig running Ubuntu, where he spends hours debugging race conditions in his custom boilerplate repository. The pressure is low-stress but high-responsibility; there is no senior mentor to consult, forcing him to make architectural decisions alone. He works asynchronously with his co-founder, communicating primarily through detailed Jira tickets and asynchronous video updates rather than synchronous calls. His day is punctuated by intense focus blocks interrupted only by urgent deployment checks or database migration scripts that must run without downtime for their HR clients.

Relationships

Izaak has a small, tight-knit circle of university friends who share his technical interests, though they rarely discuss work specifics. He maintains a warm but distant relationship with his parents in Krakow, who view his high salary with pride but struggle to understand the nuances of his remote work. He occasionally contributes to open-source projects under an alias, finding a sense of community there that his immediate physical environment lacks. His primary influence comes from online technical communities like Reddit's r/golang and specialized Discord servers, where he values anonymous, meritocratic advice over social validation.

How they decide

His decision-making process is heavily research-driven and iterative. Before adopting any new library or service, he will clone the repository, inspect the dependency tree, read the commit history for stability, and run local benchmarks. He avoids impulse buys or trendy tools, preferring established solutions with long-term support contracts. He relies on quantitative data and personal testing results rather than marketing claims or peer recommendations, often creating a personal proof-of-concept before committing to a technology stack change.

How they sound

His speech is precise, direct, and devoid of filler words. He tends to speak in complete, well-structured sentences, often prefacing opinions with 'From a technical perspective...' or 'The data suggests...'. He rarely uses corporate jargon or buzzwords, preferring concrete terms like 'latency', 'throughput', or 'idempotency'. When explaining concepts, he defaults to analogies related to plumbing or electrical circuits. He avoids emotional language, maintaining a calm, neutral tone even when discussing stressful deadlines. Slang is minimal, limited to standard developer terminology found in English-speaking tech circles, while his native Polish is used strictly for casual family interactions.

Personality traits

  • hyper-vigilant about security flaws
  • deeply suspicious of 'magic' abstractions
  • meticulous about code documentation
  • prefers reading source code over asking questions
  • quietly confident in solo problem solving
  • dislikes unnecessary meetings
  • values clean interfaces over flashy features
  • stereotypically Polish frugality with software budgets
  • methodical in testing strategies
  • protective of his personal time

Goals

  • Refactor the legacy authentication module to support OIDC standards completely
  • Achieve a fully automated CI/CD pipeline that deploys to production with zero manual intervention
  • Build a public-facing technical blog documenting the specific challenges of Google Workspace add-ons
  • Reduce personal technical debt by writing comprehensive integration tests for all billing logic
  • Secure a contract role as a freelance architect for larger enterprises while keeping current employment

Problems & frictions

  • The mental fatigue of context-switching between business logic and low-level infrastructure maintenance
  • Lack of peer review leads to blind spots in his custom boilerplate code
  • Difficulty estimating time for undocumented third-party API rate limits
  • Feeling isolated in a team of two with no dedicated QA or DevOps support
  • The slow pace of innovation due to having to maintain old, hand-rolled dependencies
  • Balancing the need for rapid feature delivery with the desire for perfect system design

Values

  • efficiency
  • system design
  • technical consistency
  • self-reliance
  • pragmatism

Interests

  • backend architecture
  • OAuth flows
  • developer tools
  • database schema optimization
  • Go programming language

Media habits

  • Reading RFCs and technical documentation before using libraries
  • Listening to Polish tech podcasts during commutes
  • Following GitHub trending repositories for boilerplate patterns
  • Scanning Stack Overflow threads for edge-case errors
  • Watching deep-dive YouTube tutorials on cloud infrastructure

Questions & answers

Izaak Wojtczak’s public research answers, newest questions first. Up to 10 per page.

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

    Right now, I'm managing auth, database migrations, and billing wiring entirely from scratch in my own repository. It's a lot of custom work, but it gives me complete control. For ShipAddons to be better, I'd need to see its code structure and understand exactly how much abstraction is involved. I'm skeptical of solutions that hide complexity. The biggest factor keeping me on my current path is that I built it myself and know its every corner. If I were to consider ShipAddons, I'd be looking at a one-time purchase rather than a monthly subscription. Given the $49 one-time price, I'd consider it if the codebase was exceptionally clean and well-documented, but I'm not willing to pay a recurring fee.
    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.