Stewart Bednar

Why this persona fits the audience

Works on a small product engineering squad at a mid-size SaaS company and is actively preparing for internal and external PM interviews after work. Keeps a spreadsheet of job descriptions, rewrites STAR stories, and uses free case-study notes from online communities while balancing a full-time coding role.

• Age: 28
• Location: Seattle, WA, US
• Occupation: Senior software engineer
• Income: $165k base
• Education: B.S. in Computer Science
• Company size: Mid-size SaaS (approx. 500 employees)
• Years in role: 4

““Every line of code, every architectural decision, has to serve a purpose. My goal is to understand that purpose at its highest level.””

Stewart Bednar, 28, is a Senior Software Engineer residing in Seattle, Washington, earning a base salary of $165,000. He holds a B.S. in Computer Science from a reputable university, a degree that laid the foundation for his current career. Stewart works at a mid-sized SaaS company, where he's been a key contributor for four years, specializing in back-end development and system architecture within a small product engineering squad. His current work involves architecting a complex analytics module, a task that engages his deep technical acumen and problem-solving skills. Stewart is driven by a strong desire for career growth and a commitment to his craft, manifesting in his meticulous approach to software development and his proactive pursuit of new challenges. He values independence and reliability, both in his work and in his personal life. Recently, Stewart has embarked on a significant personal project: transitioning into a Product Management role. This ambition stems from a growing curiosity about the strategic 'why' behind the software he builds, a desire to influence product direction beyond code implementation. He meticulously prepares for this pivot after his demanding workdays. This involves maintaining a detailed spreadsheet cataloging product management job descriptions, diligently rewriting his accomplishment stories using the STAR method, and absorbing knowledge from free case study resources found in online developer and PM communities. He approaches this transition with the same systematic, conscientious rigor he applies to his engineering work. His personal life is characterized by efficiency and discipline; he prioritizes his health through regular running and his enjoyment through crafting the perfect cup of coffee. He lives alone in a rented apartment, managing his finances prudently with a focus on long-term financial security. His current focus is almost entirely on optimizing his skill set and interview readiness for PM roles, viewing his engineering position as a stable platform from which to launch his next career phase. He's consciously investing his time and energy into acquiring the necessary strategic and communication skills, driven by a clear vision of his future career trajectory.

Background & daily life

A day in their life

Stewart's weekday begins at 6:00 AM with a precisely timed pour-over coffee. He’s at his desk by 6:45 AM, tackling his most challenging coding tasks while his mind is fresh. By 8:30 AM, he logs into the company VPN, joining daily stand-ups and diving into code reviews or feature development for the next 8 hours. Lunch is a quick, healthy meal eaten at his desk while scanning tech news. His evenings are dedicated to his PM pursuit: 6:00 PM to 7:30 PM might be spent refining STAR stories or analyzing a case study from an online PM community. From 7:30 PM to 8:30 PM, he’ll often go for a run. The remaining evening hours are for dinner, light reading, or perhaps a quick chat with his parents before winding down by 10:30 PM.

Lifestyle

Stewart lives a structured, relatively solitary life in Seattle. His days are dominated by his demanding engineering role and his even more demanding self-imposed PM interview preparation. Evenings and weekends are a carefully managed mix of running along Lake Union to clear his head, brewing pour-over coffee with a critical eye for the perfect extraction, and dedicating focused hours to his career transition. He prioritizes efficiency, viewing his time as a finite resource to be invested wisely. Finances are managed pragmatically; he saves diligently, aiming for long-term security but allowing for quality coffee beans and occasional tech gadget upgrades. Social life is limited to a close-knit group of college friends and work colleagues, often centered around shared technical discussions or casual meetups.

Work life

As a Senior Software Engineer at a mid-size SaaS firm, Stewart works on a core product feature team. His days involve deep technical problem-solving, code reviews, and collaborating with his 5-person squad on sprint planning and execution. The pressure is on to deliver high-quality, maintainable code, and he takes pride in his ability to architect robust solutions. Lately, he’s been spending considerable effort architecting the backend for a new analytics module, a task he finds intellectually stimulating. While he respects his team, particularly his lead, he often finds himself wishing for more direct involvement in the 'why' behind the features his team builds, which fuels his PM aspirations.

Relationships

Stewart maintains a small but stable network. His primary relationships are with his parents, whom he calls weekly, and a core group of three college friends who understand his intense focus. At work, he has a professional rapport with his engineering team and manager, who views him as a reliable, high-performing engineer but is unaware of his career pivot. He's not currently dating but is open to it when his schedule allows.

How they decide

Stewart is highly analytical and research-driven. He meticulously gathers information, compares options, and weighs pros and cons before making a decision. He’s not easily swayed by trends or superficial appeals, preferring to understand the underlying logic and long-term implications. He trusts data and his own reasoned judgment, often creating detailed spreadsheets or outlines to process complex choices.

How they sound

Stewart speaks with a measured, precise cadence. He tends to use well-formed sentences and avoids excessive slang or filler words. His tone is generally calm and analytical, often pausing to consider his exact phrasing. He's not overly emotive but conveys competence and thoughtfulness. He avoids hyperbole and focuses on factual accuracy and logical progression in his speech.