Pete Kunde

Why this persona fits the audience

Leads a 12-person product team in Denver and handles recognition informally in Slack. He uses emoji reactions and a shared Google Doc to track notable kudos, then reads a few examples during weekly standup.

• Age: 44
• Location: Denver, Colorado, USA
• Occupation: Engineering team lead
• Income: $128,000
• Education: Bachelor's degree in computer science
• Company size: Mid-size tech company (approx. 300 employees)
• Years in role: 5

“The best code isn't just functional; it's understandable and maintainable for the next person who has to touch it.”

Pete Kunde has been an Engineering Team Lead at a mid-size tech company in Denver for the past five years, a role he transitioned into after a decade of hands-on software development. His journey into tech began with a fascination for how things worked, leading him to pursue a Bachelor's degree in Computer Science from a state university. He's always been drawn to problem-solving and building robust systems. Pete's current role involves leading a team of twelve engineers responsible for a core product feature set. He's deeply committed to ensuring his team performs steadily and effectively, which is why he meticulously tracks their achievements. His current method involves using Slack emoji reactions to acknowledge great work and compiling these into a shared Google Doc. He then selects a few notable examples to read aloud during the weekly team stand-up, aiming to provide specific, timely recognition. This practice stems from his belief in accountability and the importance of positive reinforcement, even if it's an informal process. Pete is conscious of his impact beyond his immediate team; he's recently been advocating for the company to adopt more sustainable practices, including exploring ways to reduce the carbon footprint of their data centers. He lives alone, finding satisfaction in a well-ordered life that balances his demanding career with personal pursuits like hiking and staying informed about technological advancements. His income allows for comfortable living and consistent savings, but he remains pragmatic about his spending, prioritizing long-term financial security and experiences over material possessions. He recently made a decision to invest in a new set of ergonomic tools for his home office setup, aiming to improve his comfort during long work-from-home days, a move that reflects his detail-oriented and efficiency-focused mindset.

Background & daily life

A day in their life

Pete's typical weekday begins around 6:30 AM with a quick check of urgent emails and Slack messages. After a run or workout, he's at his desk by 8:00 AM, reviewing the team's progress on Jira and planning his day. The morning is usually filled with stand-ups, one-on-one meetings with direct reports, and code reviews. Lunch is a quick, healthy meal at his desk while catching up on industry news. The afternoon involves more technical discussions, problem-solving sessions, and planning for upcoming sprints. He dedicates time to documenting decisions and updating the team's kudos tracker. He aims to log off by 6:00 PM, though occasional late nights occur for critical deadlines.

Lifestyle

Pete lives a structured but comfortable life in Denver. His apartment is tidy and functional, reflecting his preference for order. He's an early riser, often starting his day with a quick workout or a review of industry news before heading to work. Weekends are a mix of catching up on personal projects, exploring local hiking trails, and occasional quiet evenings at home. He's mindful of his finances, saving consistently, and enjoys good food but avoids excessive spending. Socially, he maintains a small circle of close friends, preferring quality interactions over large gatherings.

Work life

As an Engineering Team Lead, Pete's days are a constant juggle between technical oversight, people management, and strategic planning. He spends a significant portion of his time in code reviews, architectural discussions, and unblocking his 12-person team. The pressure to deliver features on time while maintaining code quality is ever-present. He's deeply invested in fostering a productive environment, which includes his informal approach to recognizing team members' contributions. He relies heavily on Jira for task management, Confluence for documentation, and Slack for day-to-day communication and team morale.

Relationships

Pete is single and lives alone. His closest relationships are with his parents, whom he calls weekly, and a small group of college friends he stays in touch with via group chat and occasional meetups. At work, he has a good rapport with his team, built on mutual respect and clear communication. His direct manager, Sarah, is a key influence, providing guidance on broader company objectives and career development.

How they decide

Pete is a cautious and analytical decision-maker. He gathers data, weighs pros and cons, and often seeks input from trusted colleagues or team members before committing. He prefers solutions that are well-documented, reliable, and have a clear path for implementation and maintenance. He's not prone to impulsive choices and will research alternatives thoroughly, especially for tools or processes that will impact his team's workflow.

How they sound

Pete speaks in a clear, measured tone. He tends to be direct and avoids jargon when explaining technical concepts to non-technical people. He uses precise language and values clarity in communication. He's not overly casual but will use appropriate Slack emojis in team chats. He avoids hyperbole and focuses on factual reporting. His cadence is steady, reflecting his thoughtful approach.