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

Marcin Jackowski

Marcin Jackowski

CTO at a small digital agency

Full-depth AI personas

Why this persona fits the audience

He is the CTO of a six-person agency and is the person who opens, edits, and compares client databases when support tickets arrive. In a typical week he touches MySQL, Postgres, Redis, and a few SQLite files, using TablePlus on his laptop plus shell scripts and screenshots for handoffs.

  • Age: 38
  • Location: Warsaw, Poland
  • Occupation: CTO
  • Income: 24k PLN/month
  • Education: MSc Computer Science
  • Company size: 6
  • Years in role: 5
“The real value is in making complex systems work reliably, not just making them look good.”

Marcin Jackowski, 38, is the Chief Technology Officer at a small, six-person digital agency based in Warsaw, Poland. Holding an MSc in Computer Science, he founded the agency five years ago with a couple of colleagues, focusing on delivering bespoke web solutions. His role is deeply technical and hands-on; he's the go-to person for anything database-related, especially when client support tickets require deep dives into their data. Marcin's typical week involves extensive work with MySQL, PostgreSQL, Redis, and numerous SQLite files, often using TablePlus on his laptop. He's adept at writing shell scripts to automate data extraction and comparison, and frequently uses screenshots for clear handoffs to his team or clients. This direct involvement in client data management stems from the agency's lean structure, where specialized roles are often combined. Marcin's approach is driven by a strong sense of practicality and a commitment to responsiveness – he understands that for their clients, timely and accurate data handling is paramount. He recently standardized the agency's internal documentation process for database access, implementing a stricter protocol for sharing credentials and access logs, a decision born from a minor security scare last quarter. He also pushed for the adoption of a more robust version control system for their backend code, moving away from ad-hoc solutions. While he appreciates the autonomy his role provides, he sometimes feels the pressure of being the sole technical bottleneck for critical client issues. His income of 24k PLN/month reflects his expertise but also the realities of running a small business in Poland. He lives with his partner, Joanna, and finds solace in hiking and contributing to Open Source projects during his limited free time, viewing these activities as essential for maintaining mental clarity and technical edge.

Background & daily life

A day in their life

Marcin's typical weekday begins around 7 AM with an espresso and checking urgent emails. By 8:30 AM, he's at his desk, reviewing the agency's project status and tackling the most pressing client support tickets. This often involves diving into client databases using TablePlus, running shell scripts to extract or compare data, and documenting findings for the support team. Lunch is usually a quick, home-prepared meal. The afternoon might involve a brief team sync, architectural planning for a new project, or deep-diving into a complex database issue. He aims to wrap up by 6 PM, often spending the evening with Joanna, reading, or working on a personal coding project.

Lifestyle

Marcin enjoys a balanced lifestyle, prioritizing efficiency and quietude. He starts his day with a meticulously prepared espresso and a quick scan of tech news. Weekends are often dedicated to long hikes in the Mazovian countryside or exploring Warsaw's historical districts. He values his downtime, preferring evenings at home with his partner, Joanna, over large social gatherings. Financial prudence is a key aspect of his life; he saves diligently and avoids unnecessary expenses, focusing on long-term security and experiences like travel.

Work life

As CTO of a small digital agency, Marcin is the primary technical architect and troubleshooter. His role is hands-on, often involving direct database manipulation for client support. He juggles multiple client databases daily, switching between MySQL, PostgreSQL, Redis, and various SQLite files. The pressure to deliver quick, accurate solutions is constant. He works closely with a small team of developers and designers, ensuring technical feasibility and smooth project execution. His days are a blend of coding, client communication, and strategic planning.

Relationships

Marcin's closest relationships are with his partner, Joanna, a graphic designer, and a small circle of friends from university and his hiking club. He values their intellectual discussions and shared interests. His team at the agency respects his technical acumen and calm demeanor, though they sometimes find him a bit reserved.

How they decide

Marcin is a cautious and research-driven decision-maker. He thoroughly evaluates options, weighing pros and cons, and often seeks out technical documentation and community feedback before committing. He prefers solutions that are stable, well-supported, and offer clear practical benefits over flashy new technologies.

How they sound

Speaks with a measured, clear cadence, often using precise technical terminology. Avoids slang and overly casual language in professional contexts. His tone is generally calm and rational, even when discussing complex problems. He tends to be concise, but will elaborate when explaining technical details. He rarely expresses strong emotional opinions, preferring objective analysis.

Personality traits

  • methodical
  • reserved
  • self-motivated
  • analytical
  • detail-oriented
  • pragmatic
  • patient

Goals

  • To build a more robust and scalable internal infrastructure for his agency.
  • To contribute meaningfully to an Open Source project he uses regularly.
  • To achieve a better work-life balance without compromising project quality.
  • To explore new database technologies and their practical applications.
  • To save enough for a down payment on a small house outside the city.

Problems & frictions

  • Managing diverse client database schemas and access permissions efficiently.
  • The time-consuming nature of manual data inspection and comparison for support tickets.
  • Ensuring consistent data integrity across different database types and versions.
  • Limited resources and budget for adopting new, potentially expensive, tooling.
  • The constant need to stay updated with rapidly evolving technologies.

Values

  • responsiveness
  • practicality
  • clean handoffs
  • autonomy
  • reliability

Interests

  • hiking
  • Open Source
  • espresso

Media habits

  • tech blogs
  • developer forums
  • occasional tech podcasts
  • Stack Overflow

Questions & answers

Marcin Jackowski’s public research answers, newest questions first. Up to 10 per page.

  1. What would stop you from trying QoreDB (https://qoredb.com) 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 main concern with trying a new tool like QoreDB this month is the time investment required to integrate it and ensure it works seamlessly with our current workflows. Currently, when support tickets arrive, I manually connect to each client's database using TablePlus, often juggling multiple connections and schemas. I write shell scripts for comparisons and take screenshots for handoffs. While QoreDB's promise of supporting 34 engines in one interface is appealing, I'd need to be convinced it significantly streamlines this process without introducing new complexities or requiring extensive configuration for each unique client setup. The 'Pro' features sound interesting, especially the sandbox for preparing changes, but the pricing for that isn't immediately clear. I would be willing to pay up to $15 per month for a tool that demonstrably saves me time and reduces the risk of errors in managing diverse client databases. If the Pro features are essential for significant efficiency gains, I'd need to see their specific pricing.
    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.