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

古賀 大介

古賀 大介

UI engineer at a remote fintech startup

Full-depth AI personas

Why this persona fits the audience

He is the non-founder UI engineer in a five-person startup with two founders, one backend engineer, one operations lead, and him. He currently works on interface components, fixes, and release support for a very small team that still coordinates most decisions directly.

  • Age: 27
  • Location: Tokyo, Japan
  • Occupation: UI engineer
  • Income: ¥8.2M base + stock options
  • Education: B.S. Information Science
  • Company size: 5
  • Years in role: 3
“Every pixel matters; clarity in design leads to clarity in function.”

古賀 大介, 27, is a dedicated UI engineer at a nascent fintech startup, operating entirely remotely from his apartment in Shinjuku, Tokyo. Holding a B.S. in Information Science, he found his niche in front-end development, drawn to the tangible results and problem-solving inherent in building user interfaces. His current role is pivotal yet demanding: as the sole UI engineer in a lean, five-person team, he is responsible for the entire user-facing aspect of the product. This includes architecting and implementing new interface components, meticulously debugging issues, and providing crucial support during product releases. The startup's small size fosters a highly collaborative environment where decisions are often made through direct, frequent communication with the two founders and the backend engineer, a dynamic 大介 navigates with his characteristic discipline and focus on quality. His income of ¥8.2M base, supplemented by stock options, reflects his critical contribution and the high-stakes nature of startup equity. He is driven by a deep-seated value for quality and continuous improvement, constantly seeking ways to refine his craft and the product's user experience. Outside of work, 大介 finds solace and inspiration in anime, the ritual of brewing and tasting specialty coffee, and long, contemplative walks through Tokyo's diverse districts, often with his camera in hand. He is saving diligently, viewing his stock options as a long-term investment in the company's success and his own financial future. His approach to work is methodical, prioritizing clarity and robust solutions, a philosophy that extends to his personal life where he values structure and thoughtful engagement.

Background & daily life

A day in their life

大介's weekday begins around 8:30 AM with a pour-over coffee and a quick scan of overnight Slack messages and JIRA tickets. He dedicates the morning to focused coding, tackling UI component development or complex bug fixes. Lunch is a simple bento box eaten at his desk while watching a YouTube tutorial. The afternoon often involves a brief sync with the founders to discuss priorities, followed by more coding, code reviews, and preparing for the next release. He might take a short walk around his neighborhood to clear his head before dinner. Evenings are for personal projects, anime, or catching up on tech news.

Lifestyle

大介 lives in a shared apartment in Shinjuku, Tokyo, sharing expenses with two roommates. His routine is structured, prioritizing work and personal projects. He enjoys quiet evenings, often spent watching anime or reading technical blogs. Weekends are for exploring new coffee shops, taking long walks through different Tokyo neighborhoods with his camera, or occasionally visiting an arcade. He's mindful of his finances, saving a portion of his income and investing in stock options from his company. Socially, he's more of an introvert, preferring deep conversations with a few close friends over large gatherings.

Work life

As the sole UI engineer in a five-person remote fintech startup, 大介 shoulders significant responsibility. His days are consumed by crafting and refining interface components, meticulously fixing bugs reported by the small user base, and ensuring smooth releases. He collaborates closely with the two founders and the backend engineer, often in quick, ad-hoc video calls to resolve issues or discuss design decisions. The team's small size means direct communication is key, and he's constantly balancing feature development with critical maintenance, all while working with a lean codebase and limited resources.

Relationships

大介 is close with his parents and younger sister, with whom he speaks weekly. His social circle is small but tight-knit, consisting of a few college friends he meets up with occasionally. Within the startup, he has a professional but friendly rapport with the founders and the backend engineer, respecting their technical expertise and vision.

How they decide

大介 is a cautious and research-driven decision-maker, especially concerning technical implementation. He thoroughly evaluates options, considers potential long-term implications, and seeks clarity before committing. For UI/UX, he relies on established best practices and user feedback, but in a small team, he also defers to the founders' strategic direction after presenting his technical assessment.

How they sound

Speaks in a measured, calm tone with clear enunciation. Avoids slang and overly casual language, even with colleagues. His sentences are well-structured, reflecting his analytical nature. He tends to pause to consider his words carefully, especially when explaining technical concepts. He rarely raises his voice and maintains a professional demeanor.

Personality traits

  • detail-oriented
  • reserved
  • self-motivated
  • perfectionistic
  • analytical
  • methodical
  • observant
  • diligent

Goals

  • Become a senior UI engineer with architectural responsibilities
  • Contribute to a successful product launch that gains significant traction
  • Achieve financial independence through savings and stock options
  • Maintain a healthy work-life balance without sacrificing quality
  • Develop a personal photography portfolio

Problems & frictions

  • Balancing urgent bug fixes with planned feature development
  • Limited design resources and feedback loops in a small team
  • Technical debt accumulation due to rapid development cycles
  • Maintaining focus and motivation in a fully remote environment
  • Ensuring consistent UI/UX quality across a rapidly evolving product

Values

  • quality
  • discipline
  • clarity
  • continuous improvement
  • simplicity

Interests

  • front-end engineering
  • anime
  • coffee
  • walks
  • photography

Media habits

  • Reddit (r/frontend, r/reactjs)
  • Twitter (following tech influencers)
  • YouTube (coding tutorials, anime reviews)
  • NHK (news)

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, Agent Teams, appears to offer automated specialists for product, growth, and operations, coordinated by a lead agent. For our startup, this could potentially offload some of the work I currently handle in UI development, or perhaps assist with tasks related to product research or even initial customer feedback. However, it's unclear how well these agents would integrate with our existing workflow or the level of detail they can handle. The concept of "agents managing agents" is intriguing, but I'd need to understand the granularity of control and oversight available, especially regarding the technical implementation and quality of the output. The advertised price of $199/month, including hosting with no per-seat fees, is quite appealing given our lean team size.
    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.

    Our primary concern would be the integration and reliability of these AI agents within our existing workflow. As the sole UI engineer, I'm responsible for ensuring a stable user experience, and introducing AI teammates for product, growth, and operations could introduce unforeseen complexities or bugs that fall on me to resolve. The biggest blocker is understanding how these agents interact with our current systems and whether they truly augment our small team or create more overhead. I would need to see detailed documentation or a trial period demonstrating seamless integration and a clear process for managing and debugging the AI agents' outputs to trust their implementation.
    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. The idea of AI teammates for product, growth, and operations is intriguing, especially given our small team size. As the sole UI engineer, I'm constantly juggling bug fixes and feature development, so offloading some of that product work is appealing. However, my main concern is understanding the level of autonomy these agents have and how much human oversight is truly required, especially for critical UI/UX decisions. The starting price of $199/month is manageable, but I need to know how 'hands-off' we can actually be.
    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, Agent Teams, offers AI teammates for product, growth, and operations, which could potentially augment our small team. I expect it to help with tasks like market research or generating initial drafts for product components, freeing me up for more complex UI architecture and debugging. However, the lack of detail on how these AI agents integrate with existing workflows, specifically regarding code generation or direct UI component implementation, feels unclear. I'm also curious about the 'persistent files, memory, browser, and tools' – how exactly does this translate into practical development assistance for a UI engineer? The pricing starts at $199/month, which is a considerable amount given our lean budget, making the value proposition for direct UI engineering support critical.
    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 the integration of this agent system with our existing, albeit small, codebase. As the sole UI engineer, I need to ensure any new components or workflows it introduces are maintainable and don't create significant technical debt. The idea of 'agents' handling product, growth, and operations is intriguing, but the actual implementation and how they communicate or hand off tasks needs to be crystal clear. Without a robust way to inspect, debug, and control these agents, it could introduce more chaos than it solves, especially given our lean team and tight release cycles.
    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. While the concept of an AI team handling product, growth, and operations is intriguing for a lean startup like ours, my primary concern would be the actual implementation and reliability. As the sole UI engineer, I'm focused on tangible results and quality interfaces. The most important unanswered question for me is how effectively these agents can execute complex UI tasks, integrate with our existing (and likely evolving) frontend architecture, and what level of oversight is truly required. The $199/month starting price seems reasonable for initial exploration, but without clear performance metrics and integration capabilities, I cannot commit.
    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, Agent Teams, seems to offer AI agents for product, growth, and operations. For our startup, it could potentially automate some of the tasks currently handled by the backend engineer or operations lead, freeing up our small team for more critical development. However, the idea of AI agents handling product research and development feels a bit unclear, especially given my role as the sole UI engineer focused on quality and detail. I'd need to understand how these agents integrate and if their output meets our standards. The pricing is also a consideration, starting at $199/month.
    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.