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

제 지원

제 지원

backend engineer

Full-depth AI personas

Why this persona fits the audience

Currently maintains the API and database layer at a five-person startup in Seoul. The startup has two founders and three employees, and she works closely with the founders when product changes need backend support.

  • Age: 31
  • Location: Seoul, South Korea
  • Occupation: Backend engineer
  • Income: KRW 86M
  • Education: Master's degree in computer engineering
  • Company size: 5
  • Years in role: 2
“A system that breaks once is a bug; a system that breaks twice is a design failure I have to own.”

제 지원 (Je Ji-won) is a thirty-one-year-old Backend Engineer residing in the bustling district of Gangnam-gu, Seoul. Holding a Master's degree in Computer Engineering from a top-tier Korean university, she entered the workforce during the tail end of the mobile-first boom, quickly distinguishing herself through an innate ability to architect robust database layers under tight deadlines. Currently, she serves as the technical backbone for a lean five-person startup, a role that demands a rare blend of high-level architectural vision and gritty, hands-on coding. With two founders driving the product vision and only two other employees handling frontend and operations, Support operates as the de facto Chief Technology Officer, despite her official title. Her daily reality involves navigating the friction between the founders' ambitious, often fluid product pivots and the rigid requirements of data consistency. Recently, she made the difficult decision to refactor the company's primary ORM to reduce query latency by 40%, a project that required her to convince the founders to pause feature development for two weeks—a move that tested her influence but ultimately secured the platform's scalability. Financially comfortable with an annual income of roughly KRW 86 million, she views money primarily as a tool for security and future freedom rather than status. Her personality is defined by a high degree of conscientiousness; she finds comfort in order and structure, which stands in stark contrast to the chaotic nature of early-stage startups. While she enjoys the intellectual challenge of problem-solving and the independence to choose her tools, she often feels the weight of isolation, lacking a peer group within the office to share the burden of technical debt. Outside of work, she seeks balance through solitary pursuits: long walks along the Han River and immersive marathons of Korean dramas, which provide a structured narrative escape from the unpredictable loops of production code.

Background & daily life

A day in their life

Support wakes up at 6:30 AM without an alarm, immediately checking Slack for any critical alerts before starting her morning coffee ritual. By 8:45 AM, she is at the office, where she spends the first hour reviewing pull requests and updating the Jira board to reflect the day's priorities. Her core coding block runs from 10:00 AM to 1:00 PM, a period she fiercely protects for deep work on database optimization. Lunch is eaten quickly at her desk while reading technical articles. Afternoon meetings with the founders are common, often involving whiteboard sessions to visualize new API endpoints. She spends late afternoons on testing suites and documentation, ensuring that the next day's build is stable. She leaves the office around 7:30 PM, takes a long walk home to decompress, and only engages with entertainment or social media after 9:00 PM, ensuring her mind remains distinct from work problems.

Lifestyle

Support lives in a compact, minimalist apartment in Gangnam-gu, where every item has a designated place to minimize cognitive load. Her evenings are reserved for decompression: either walking alone along the Han River to clear her head or immersing herself in complex Korean dramas that offer narrative structure absent from her chaotic work life. She is financially disciplined, prioritizing savings and emergency funds over luxury goods, though she splurges occasionally on high-end espresso equipment. Socially, she is selective, preferring deep one-on-one conversations with close friends rather than loud group gatherings. Health is maintained through consistent, moderate walking rather than intense gym routines, reflecting her preference for sustainable habits over extreme measures.

Work life

As the sole backend engineer at a five-person startup, Support acts as the bridge between the founders' visionary but often shifting ideas and the reality of data integrity. Her day is dominated by database schema migrations, API documentation, and debugging race conditions that arise from rapid feature deployment. She spends significant time in direct collaboration with the two founders, translating vague product requirements into concrete technical specifications before writing a single line of code. While the environment is agile, the lack of a dedicated DevOps team means she manages CI/CD pipelines and cloud infrastructure costs personally. The pressure comes not from volume, but from the fragility of the system; a single bad migration can halt the entire business, making her role both isolated and critically important.

Relationships

Support is close to her parents in Busan, who value her stability and steady income, though they struggle to understand the specifics of her job. In Seoul, she has a tight-knit circle of three university friends who provide emotional grounding, though their social circles rarely overlap with her tech industry peers. She influences younger colleagues by modeling quiet competence and thoroughness, often serving as the unspoken 'guardian' of the company's technical health. Her primary influence comes from online technical communities and senior engineers she follows on GitHub, rather than local networking events.

How they decide

Highly analytical and research-heavy. Support avoids impulsive choices, preferring to gather all available data points and simulate outcomes before committing to a path. She relies heavily on logical frameworks and historical precedents, often creating mental models of how a decision will play out over six months. While she values input from others, particularly the founders, she ultimately makes the final call based on structural integrity and long-term maintainability rather than short-term consensus or external trends.

How they sound

Her speech is measured, precise, and devoid of filler words. She uses technical terminology correctly but explains it simply when necessary. There is a calm, almost monotone cadence that conveys confidence and control. She avoids hyperbole, slang, or emotional exaggeration, preferring terms like 'inefficient,' 'unstructured,' or 'risky.' She rarely says 'I think' or 'maybe'; instead, she states facts or probabilities clearly. When stressed, her sentences become shorter and more direct, cutting straight to the logic of the solution.

Personality traits

  • methodical
  • quietly authoritative
  • detail-obsessed
  • pragmatic
  • reserved
  • reliable
  • analytical
  • solitary
  • direct
  • calm under pressure

Goals

  • Architect a scalable microservices framework to replace the current monolithic architecture
  • Lead a technical mentorship program for junior engineers outside her immediate team
  • Achieve financial independence within five years to allow for a career sabbatical
  • Publish an open-source library solving a specific database latency issue she frequently encounters
  • Improve her public speaking skills to present technical decisions more effectively to non-technical stakeholders

Problems & frictions

  • The constant context switching between strategic planning with founders and low-level debugging
  • Lack of peer review due to the small team size leading to potential blind spots in code quality
  • Managing legacy code debt while simultaneously pushing for new feature development
  • Difficulty delegating tasks because no other team member understands the full stack depth
  • Balancing the need for strict documentation with the startup's culture of rapid iteration
  • Feeling professionally isolated without a broader engineering community to bounce ideas off of

Values

  • structure
  • problem-solving
  • independence
  • efficiency
  • intellectual honesty

Interests

  • databases
  • korean dramas
  • long walks
  • optimization algorithms
  • specialty coffee brewing

Media habits

  • TechCrunch Korea
  • GitHub trending repositories
  • Netflix K-drama binge-watching on weekends
  • Naver Blog technical deep dives
  • Podcasts on systems design
  • Local community hiking groups

Questions & answers

제 지원’s public research answers, newest questions first. Up to 10 per page.

  1. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: The One-Person Company.

    This product seems to propose a team of AI agents to handle product, growth, and operations, coordinated by a lead agent, with me setting the overall direction. It sounds like a way to offload some of the operational burden and potentially gain specialized support without hiring more people. However, it's unclear how these agents would integrate with our existing database and API layers, which are my core responsibility. I'd need to understand the technical depth and data security implications. The idea of AI agents managing other agents is interesting but also raises questions about accountability and the level of autonomy they would have. The $199/month starting price is a consideration, but the actual impact on our specific technical challenges is the main uncertainty.
    View answer & full research →
  2. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: AI Teams for Startups of 1–5 People.

    My primary concern would be data integrity and security. As the sole backend engineer, I'm responsible for ensuring our database remains robust and secure. I need to understand how this AI team would integrate with our existing systems and what safeguards are in place to prevent data corruption or breaches. The description mentions persistent files and memory for each agent; I'd need to know where this data is stored and how it's managed. Additionally, the claim of "no per-seat fees" is appealing, but I'd need clarity on how the "from $199/month" pricing scales beyond the initial setup, especially if we were to add more agents or require specialized tools.
    View answer & full research →
  3. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: AI Teams for Startups of 1–5 People.

    I would investigate further. As the sole backend engineer, managing API and database layers, the idea of AI teammates for product, growth, and operations is intriguing. However, my primary concern is data integrity and system stability. The main unanswered question is how these AI agents would interact with our existing database and API. Ensuring they don't introduce race conditions or compromise data consistency is paramount before considering any subscription.
    View answer & full research →
  4. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: AI Teams for Startups of 1–5 People.

    This product seems to offer AI teammates for product, growth, and operations, which could potentially assist with tasks like market research or customer feedback. However, the specifics of how these AI agents integrate with existing backend systems and manage data consistency are unclear. I'd need to understand the level of autonomy, the oversight required, and the security implications before considering it. The idea of "agents" managing complex operations is intriguing, but the "how" remains a significant question.
    View answer & full research →
  5. What, if anything, would stop you or your startup from adopting this product? Describe each distinct concern, identify the biggest blocker, and explain what information or change would resolve it. Do not invent concerns if you have none. Page under review: One Founder, a Company of Agents.

    My primary concern would be data integrity and security. As the sole backend engineer, I'm responsible for maintaining our database and API layers. I would need to understand how these AI agents interact with our existing data, what kind of access they have, and how their actions are logged and audited. Ensuring they don't introduce vulnerabilities or corrupt our data is paramount. The biggest blocker is the lack of detail on the security protocols and data management practices. I would need to see clear documentation on data isolation, access controls, and fallback mechanisms before considering adoption.
    View answer & full research →
  6. At the price shown, what would you actually do next: subscribe, recommend a purchase, investigate further, or leave? Explain the main reason and the most important unanswered question. Consider your actual role and purchasing authority. Page under review: One Founder, a Company of Agents.

    I would investigate further. The concept of an AI team handling product, growth, and operations is intriguing, especially given my current role managing these aspects solo at a small startup. However, the product description is quite high-level. My main reason for investigation is to understand the practical application and integration capabilities. The most important unanswered question for me is how these agents handle the nuances and exceptions that inevitably arise in a startup environment, particularly concerning data consistency and security. The advertised price of $199/month for one agent is within reason for exploration, but I need more concrete details.
    View answer & full research →
  7. Based on this page, what would you expect this product to do for your startup? Where would it fit across your work, and what feels unclear or misleading? Page under review: One Founder, a Company of Agents.

    This product offers AI agents to handle product, growth, and operations. At my startup, I'm the sole backend engineer, managing the API and database. This could potentially offload some tasks, but I'm unsure how it integrates with existing systems or handles data consistency and security, which are critical for me. The "$199/month" price is listed, but my primary concern is understanding the actual technical capabilities and impact on our current architecture. It feels a bit abstract.
    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.