Brian Schmidt

Why this persona fits the audience

Support engineer at a 40-person devtools startup in San Francisco. He spends part of each day in HubSpot, turns reproducible bugs into Linear issues, and follows one or two engineering threads until they are closed.

• Age: 28
• Location: San Francisco, California, US
• Occupation: Support engineer
• Income: $135k-$170k
• Education: BSc Computer Science
• Company size: 40
• Years in role: 3

“If you can't explain it simply, you don't understand it well enough – and that applies to bugs, too.”

Brian Schmidt, 28, is a dedicated support engineer at a 40-person devtools startup nestled in the vibrant tech scene of San Francisco. Holding a BSc in Computer Science from UC Davis, he found his niche not in pure development, but in the critical intersection of user experience and engineering execution. His role is defined by a rigorous process: meticulously logging customer issues in HubSpot, then transforming those reproducible bugs into detailed, actionable tickets within Linear. Brian doesn't just pass the buck; he actively engages with the engineering lifecycle, often following one or two specific bug threads from initial report through to final resolution, ensuring no detail is lost. This hands-on approach stems from his core value of learning by doing and a deep-seated passion for debugging. He thrives on understanding the 'why' behind a problem, not just the 'what.' His income places him comfortably within the city's professional class, allowing for a stable lifestyle, though he remains pragmatic about his spending, prioritizing long-term financial health and investments in tools that genuinely improve his efficiency. He recently championed the adoption of a new internal documentation standard, pushing for clearer, more concise write-ups for common issues, a decision that has already begun to streamline his daily triage process and reduce repetitive questions from the engineering team. Brian sees his role as more than just fixing problems; it's about building better systems and fostering clearer communication between disparate parts of the company. His career trajectory is focused on deepening his technical expertise and potentially moving into a more senior or specialized engineering role, perhaps even leading a support-focused engineering team in the future.

Background & daily life

A day in their life

Brian's typical weekday starts around 7:30 AM with coffee and news. He bikes to the office by 9 AM, immediately diving into HubSpot to triage new support tickets. By mid-morning, he's translating critical issues into Linear tickets, adding detailed reproduction steps and relevant logs. Lunch is usually a pre-prepped meal eaten at his desk while reviewing a Slack channel or a technical blog. The afternoon is often spent following up on engineering tickets he's 'on' – checking progress, answering clarifying questions, and testing fixes once they're deployed to a staging environment. He aims to wrap up by 6 PM, often with a quick bike ride home, followed by dinner and personal projects or relaxation.

Lifestyle

Brian lives a structured but active life in San Francisco. His mornings begin with a strong pour-over coffee and a quick scan of Hacker News before his bike commute across the city. He prioritizes efficiency, often meal-prepping lunches on Sundays to save time during the week. Evenings are a mix of unwinding with a book, tinkering with a personal coding project, or catching up with a few close friends. He's mindful of his finances, saving diligently for future goals, but enjoys the occasional craft brewery visit or concert. His apartment is minimalist but functional, reflecting his preference for order and calm.

Work life

As a support engineer at a growing devtools startup, Brian's days are a dynamic blend of reactive problem-solving and proactive system improvement. He navigates between HubSpot, meticulously logging customer issues, and Linear, where he translates those into actionable engineering tickets. A significant portion of his time is dedicated to deep-diving into specific engineering threads, ensuring bugs are fully understood and resolved before closing the loop. He collaborates closely with a small, dedicated engineering team, often acting as the bridge between user pain points and technical solutions. The pressure is on to maintain high customer satisfaction while also contributing to product stability and evolution.

Relationships

Brian maintains a close-knit circle of friends, mostly met through university or previous jobs, with whom he shares a passion for technology and problem-solving. He communicates regularly with his parents via text and weekly calls. Within his company, he has a good working relationship with the engineering team, built on mutual respect for each other's expertise, and a friendly rapport with the sales and marketing teams.

How they decide

Brian is a research-heavy decision-maker, especially for tools that impact his workflow. He'll thoroughly investigate options, compare features, read reviews, and often test free trials extensively before committing. He values practical utility and demonstrable efficiency gains over flashy marketing. Peer recommendations from trusted colleagues can sway him, but he ultimately relies on his own analysis of how a tool fits into his existing systems.

How they sound

Speaks clearly and deliberately, with a slight tendency to explain technical concepts thoroughly. Avoids excessive jargon unless speaking with fellow engineers. His tone is generally calm and measured, even when discussing frustrating issues. He uses phrases like 'So, what I'm seeing is...', 'The core of the problem seems to be...', and 'Let's trace this back.' He's not overly casual but is friendly and approachable.