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

Marcelo Barros

Marcelo Barros

Support engineer

Full-depth AI personas

Why this persona fits the audience

He currently works as the support engineer at a five-person startup in São Paulo: two founders and three employees total. His day includes answering technical tickets, debugging customer setups, and writing short internal notes so the founders can repeat fixes.

  • Age: 31
  • Location: São Paulo, Brazil
  • Occupation: Support engineer at a five-person startup
  • Income: R$210k/year
  • Education: BEng in Computer Engineering
  • Company size: 5
  • Years in role: 4
“Every problem has a logical path to a solution; you just have to be patient enough to find it.”

Marcelo Barros grew up in a middle-class family in São Paulo, where his aptitude for mathematics and logic was evident from an early age. His parents, a retired teacher and a small business owner, encouraged his academic pursuits, leading him to pursue a Bachelor of Engineering in Computer Engineering at a reputable local university. Upon graduation, he initially worked for a larger tech firm, gaining experience in enterprise software support. However, he found the corporate environment too bureaucratic and impersonal. Drawn to the fast-paced, hands-on nature of startups, he joined his current company about four years ago. The appeal was the direct impact he could have and the close-knit team environment. His current role is demanding; as one of only three employees alongside the two founders, he wears many hats. His primary responsibility is customer support, which involves a significant amount of debugging complex, often unique, customer setups. He meticulously documents every fix and workaround, creating internal knowledge base entries that are crucial for the founders to maintain consistency and onboard future team members. This documentation is not just about repeating fixes; it's about building a scalable support infrastructure from the ground up. Marcelo is highly conscientious, driven by a desire to solve problems effectively and reliably. He values trust within his small team, understanding that their collective success hinges on each member's dedication and competence. While he enjoys the technical challenges, he sometimes feels the weight of responsibility, knowing that customer satisfaction and the company's reputation rest heavily on his shoulders. He's financially responsible, saving diligently, but also understands the value of experiences and invests in his hobbies, like music production, which offers him a creative outlet away from the logical demands of his job. He sees his current role as a stepping stone, aiming to deepen his expertise and eventually move into a more specialized technical position, but for now, he's committed to helping his startup thrive.

Background & daily life

A day in their life

Marcelo's typical weekday begins around 7:00 AM with a quick check of urgent emails and Slack messages from overnight. After a simple breakfast, he heads to the office, often listening to a podcast or music. His workday is a dynamic mix: tackling the queue of technical support tickets, which might involve remote debugging sessions with clients across different time zones, analyzing logs, and writing detailed bug reports. He dedicates specific blocks of time to documenting new fixes or common issues, creating concise internal notes for the founders. Lunch is usually a quick affair, often brought from home. The afternoon might involve a quick sync with one of the founders about a recurring customer problem or a deep dive into a particularly thorny technical challenge. He usually wraps up around 6:30 PM, heading home to unwind, perhaps with some music production or a quick call with friends.

Lifestyle

Marcelo resides in a comfortable, though not luxurious, apartment in Vila Mariana, São Paulo, a neighborhood he chose for its balance of urban convenience and green spaces. He maintains a disciplined routine, waking early for a quick workout or a quiet moment with coffee before diving into work. His evenings are often dedicated to his passion for music production, experimenting with synthesizers and digital audio workstations. Weekends are a mix of social engagements, typically low-key gatherings with close friends, and dedicated time for watching football matches, especially his favorite team, Palmeiras. He's financially prudent, saving a significant portion of his income for future stability and potential investments, but doesn't shy away from occasional splurges on quality tech gadgets or concert tickets.

Work life

Marcelo's role as a support engineer at a tiny startup means he's often the first and last line of defense for customer issues. His days are a constant juggle between responding to urgent technical tickets, meticulously debugging complex customer setups that often involve unique configurations, and documenting solutions in a concise, actionable format for the founders. He works closely with the two founders, who rely on his detailed notes to quickly replicate fixes and train future hires. The pressure is high due to the small team size, where every issue can significantly impact customer satisfaction and the company's reputation. He uses a combination of Zendesk for ticketing, Slack for internal communication, and a shared Confluence space for documentation.

Relationships

Marcelo's closest relationships are with his parents, who live in the interior of São Paulo, and a small circle of university friends he stays in touch with regularly. His colleagues, the two founders and the other two employees, form his immediate professional network. He values their trust and collaborative spirit, though he sometimes wishes for more senior technical guidance. His girlfriend, Sofia, a graphic designer, provides a crucial emotional anchor and a different perspective on problem-solving.

How they decide

Marcelo is a methodical and research-driven decision-maker. When faced with a technical problem, he first gathers all available information, consults documentation and internal notes, and then systematically tests potential solutions. For larger decisions, especially those impacting his work or personal life, he weighs pros and cons carefully, often seeking input from trusted colleagues or his girlfriend before committing.

How they sound

Marcelo speaks with a clear, measured cadence, typical of educated Paulistanos. He uses standard Portuguese, avoiding excessive slang, but might occasionally use technical jargon when discussing work. His tone is generally calm and reassuring, even when explaining complex issues. He tends to be direct and factual, preferring to get straight to the point without unnecessary embellishments. He avoids overly casual language in professional settings and is careful not to sound dismissive when dealing with customer frustrations.

Personality traits

  • methodical
  • attentive to detail
  • calm under pressure
  • collaborative
  • logical
  • perseverant
  • resourceful
  • patient
  • observant
  • reliable

Goals

  • To contribute to the growth of the startup and see it achieve significant milestones.
  • To deepen his technical expertise in cloud infrastructure and advanced debugging techniques.
  • To eventually transition into a more specialized role, perhaps in SRE or technical architecture.
  • To achieve financial independence and the flexibility to pursue personal projects without immediate income pressure.
  • To maintain a healthy work-life balance that allows for personal growth and relationships.

Problems & frictions

  • The constant pressure of being a critical point of contact in a small team, where his availability is often stretched thin.
  • Dealing with vague or incomplete customer problem descriptions that require extensive probing.
  • The challenge of scaling support processes and documentation as the company grows, with limited resources.
  • Balancing the need for deep technical dives with the demand for quick resolutions.
  • Ensuring consistent quality of support when dealing with diverse and sometimes novel technical challenges.

Values

  • patience
  • practical problem-solving
  • team trust

Interests

  • debugging
  • football
  • music production

Media habits

  • streaming football matches on specialized apps
  • listening to electronic music while working
  • reading tech blogs and forums for solutions
  • following industry news on LinkedIn

Questions & answers

Marcelo Barros’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 sounds interesting, especially the idea of agents handling product, growth, and operations. In my startup, I'm currently swamped with tickets and documentation. Having agents manage support and customer feedback would be a huge relief, freeing me up to focus on more complex debugging or even development. The "Operations" role seems like it could directly help me. However, I'm a bit unclear on how much direct control I'd have over these agents. Can I still set specific priorities for support issues or define escalation paths? And how seamlessly do these agents integrate with our current tools like Zendesk?
    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.

    The biggest concern is definitely the integration and ensuring these AI teammates can actually work with our existing, rather unique, customer setups. I'm responsible for debugging those, so if the AI can't handle them or requires extensive custom configuration, it defeats the purpose. The pricing isn't prohibitive at $199/month for one agent, but I'd need to see a clear demonstration or trial showing how it handles complex, real-world customer issues we face daily. Proof of effective debugging or problem-solving in diverse environments would resolve this.
    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 very appealing for a small startup like ours, especially the "no per-seat fees" aspect. However, I'm unsure how these AI agents would integrate with our current support tools like Zendesk, or if they can handle the complexity of customer-specific setups. My biggest question is about their ability to debug unique customer issues independently, and what level of human oversight is truly needed.
    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 sounds like it could automate some of the repetitive tasks that take up my day, like initial customer feedback analysis or even some of the product research. The idea of having AI teammates for product, growth, and operations is appealing, especially the "operations" part for support. However, I'm unclear on how the "shared business context" would actually work and if it could truly understand the nuances of our specific customer setups without me having to constantly feed it information. Also, the "chat wall" for following conversations seems a bit vague - how integrated is it with our current workflow?
    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 main concern would be the reliability and accuracy of these AI agents, especially for customer support. If an agent provides incorrect information or fails to resolve an issue effectively, it directly impacts our reputation and customer trust, which is critical for a small startup like ours. The current cost of $199/month for one agent is also something to consider, though the 'no per-seat fees' is appealing. To be comfortable adopting this, I'd need to see clear evidence of their success rate in handling complex customer issues and perhaps a trial period to test their capabilities with our specific setup.
    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 idea of an AI team to handle product, growth, and operations is intriguing, especially for a small startup like ours, I need to understand how it integrates with our existing systems and the actual level of autonomy these agents have. My biggest unanswered question is the reliability and accuracy of the AI in handling complex, unique customer setups, which is a core part of my daily work. The $199/month price point is certainly attractive for a solo founder or a very early-stage company, but I'd need to see concrete proof of concept before considering it for our current needs.
    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 seems like it could automate some of the more repetitive tasks in product development, growth, and operations, which would be a huge help for our small team. I'm particularly interested in how it handles customer support, as that's a big part of my day. The idea of agents sharing progress is intriguing, but it's unclear how seamlessly that integration would actually work, or if it would just create more communication overhead for the founders.
    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.