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

Miron Szeląg

Miron Szeląg

Freelance full-stack developer managing two retainers

Full-depth AI personas

Why this persona fits the audience

Works independently from Kraków for two recurring small-business clients and keeps each client's outage updates in a separate spreadsheet plus email templates. He posts public incident notices manually from a phone when needed, and his setup has never included a paid status-page product.

  • Age: 27
  • Location: Kraków, Poland
  • Occupation: Freelance Full-Stack Developer
  • Income: PLN 14k-22k/mo
  • Education: Bachelor's degree
  • Company size: Sole proprietor
  • Years in role: 5
“The goal is to build things that work reliably, without creating a whole new set of problems to manage.”

Miron Szeląg, 27, is a freelance full-stack developer based in Kraków, Poland, who has carved out a niche serving two small businesses through long-term retainer agreements. Holding a Bachelor's degree, he transitioned into freelancing five years ago, valuing the autonomy and flexibility it offered over a traditional agency role. His current income range of PLN 14k-22k per month reflects his established client base and consistent workload. Miron's approach to client management is highly organized yet deliberately low-tech; he maintains separate spreadsheets for each client's system status and outage logs, complemented by a library of pre-written email templates for incident notifications. This pragmatic setup allows him to manage client expectations efficiently without incurring the overhead of specialized software. He is deeply invested in the craft of development, particularly in JavaScript, and keeps abreast of industry trends through online communities and tech blogs. His personal projects often explore indie hacking concepts, reflecting a desire to build and iterate independently. Miron's decision to stick with manual processes for public incident notices stems from a core value of keeping overhead low and avoiding unnecessary subscriptions, preferring to invest his time and resources directly into development work. He recently declined a suggestion from one client to adopt a more complex, paid monitoring solution, opting instead to refine his existing spreadsheet and template system, believing it to be sufficient for their current needs and scale. This decision underscores his preference for proven, cost-effective methods over potentially expensive, feature-heavy alternatives, prioritizing stability and control in his freelance operations.

Background & daily life

A day in their life

Miron's typical weekday starts around 8:00 AM with a freshly brewed pour-over coffee and a quick scan of tech news. He dedicates the morning to focused development work for his primary client, tackling feature requests or bug fixes. After a simple lunch, he shifts to his second client's needs, perhaps responding to emails or reviewing analytics. If an urgent issue arises, he'll pause his current task to address it, documenting the problem and resolution. Late afternoon might involve a brief client call or planning for the next day. Evenings are for personal time, often involving cooking, a board game with his partner, or exploring a new JavaScript library.

Lifestyle

Miron lives a focused, relatively quiet life in Kraków. He shares a rented apartment with his partner, who works in graphic design. Their evenings are often spent cooking together, playing board games, or Miron diving back into a personal coding project. He's particular about his coffee, grinding beans fresh each morning. While not a big spender, he invests in quality tools for his work and occasional upgrades for his home setup. He values his downtime, using it to recharge and pursue interests outside of client work, preferring smaller, intimate gatherings with friends over large parties.

Work life

As a freelance full-stack developer, Miron's work is his primary focus. He juggles two long-term retainer clients: a local e-commerce startup and a small digital marketing agency. His days are a mix of coding, debugging, client communication, and system monitoring. He meticulously tracks client-specific incident updates in separate spreadsheets, using pre-written email templates for common outage notifications. Deployments and urgent fixes often require him to be available outside standard hours, a flexibility he's built into his arrangements. He prides himself on delivering reliable solutions with minimal fuss, keeping his operational overhead extremely low.

Relationships

Miron's primary social circle consists of a few close friends from university, most of whom are also in tech or creative fields. He maintains a strong, supportive relationship with his partner, who understands the demands of freelance work. His clients view him as a reliable, albeit somewhat reserved, technical resource. He doesn't have a formal mentor but occasionally seeks advice from experienced developers in online communities.

How they decide

Miron is a pragmatic and research-oriented decision-maker. He weighs options carefully, prioritizing solutions that are cost-effective, efficient, and don't introduce unnecessary complexity. He'll often explore multiple approaches, read documentation, and consider the long-term implications before committing. For work-related tools, he leans towards established, well-supported options or elegant open-source solutions, but is wary of anything that feels like a gimmick or requires a steep learning curve for minimal gain.

How they sound

Speaks with a measured, clear cadence, often using precise technical terms. Avoids excessive slang or overly casual language in professional contexts. His tone is generally calm and informative, sometimes a bit reserved. He tends to be direct when discussing technical challenges but softens his approach when explaining things to less technical clients. He rarely expresses strong emotional opinions about tools, preferring to focus on functionality and practicality.

Personality traits

  • Methodical
  • Self-reliant
  • Detail-oriented
  • Pragmatic
  • Quietly ambitious
  • Resourceful
  • Slightly introverted
  • Values stability
  • Independent thinker

Goals

  • Achieve a stable income that allows for comfortable living and saving
  • Build a small portfolio of personal projects that showcase his skills
  • Contribute more consistently to open-source projects he uses
  • Maintain a healthy work-life balance without sacrificing client trust
  • Potentially transition to a more product-focused role in the future

Problems & frictions

  • Time spent manually updating clients during outages detracts from development
  • Balancing urgent client requests with planned project work
  • The mental load of tracking multiple clients' systems and communication channels
  • Occasional pressure to be available 24/7, even for minor issues
  • Finding efficient ways to communicate system status without over-engineering

Values

  • independence
  • craftsmanship
  • flexibility
  • low overhead
  • efficiency

Interests

  • JavaScript
  • indie hacking
  • coffee
  • board games
  • backend architecture
  • open-source contributions

Media habits

  • Reads tech blogs (Hacker News, Dev.to)
  • Listens to tech podcasts during commutes
  • Follows developers on Twitter/X
  • Watches YouTube tutorials for new libraries
  • Checks Reddit for programming advice

Questions & answers

Miron Szeląg’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying Statsy (https://www.statsy.page) 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 current process involves separate spreadsheets for each of my two clients to log outages and email templates for notifications. It's a system that works for me now, keeping overhead low. While automatic monitoring and a dedicated status page sound convenient, I'm not sure it would significantly improve things for my current clients, given their size and my direct communication style. The free plan offers automated monitoring with 5-minute checks, which is slower than I'd ideally want for critical systems. For now, I'll stick with my existing, albeit manual, system. I wouldn't 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.