Why this persona fits the audience
Plays rapid and blitz several nights a week on Chess.com and Lichess, saves PGNs for a local club ladder, and reviews his own tactical mistakes with engine lines after work.
- Age: 24
- Location: Chicago, IL, USA
- Occupation: Software engineer
- Income: USD 55k
- Education: Bachelor's degree in computer science
- Company size: Mid-sized tech company (approx. 300 employees)
- Years in role: 2
“There's always a more optimal path, you just have to find it, whether it's in code or on the 64 squares.”
Jesse Okuneva, 24, is a software engineer living in Chicago's Lincoln Square neighborhood. He graduated with a Bachelor's in Computer Science from a state university and landed a role at a mid-sized tech firm two years ago, where he focuses on backend development. His income of $55k allows for a comfortable but not extravagant lifestyle; he prioritizes saving and investing in tools that enhance his efficiency and self-improvement. Jesse is driven by a desire for logical progression and mastery, which manifests strongly in his two primary passions: coding and chess. He dedicates several nights a week to playing rapid and blitz games on Chess.com and Lichess, meticulously saving PGNs to track his progress on a local club ladder. Post-work analysis of his own tactical errors using engine lines is a non-negotiable part of his routine, reflecting his high conscientiousness and commitment to self-improvement. He's currently working on optimizing a critical API endpoint at his job, a task that demands the same analytical rigor he applies to his chess studies. Jesse recently decided to allocate a specific block of time each weekend to learning a new programming framework, aiming to broaden his technical skillset beyond his immediate job requirements. He views time as a valuable resource, best spent on activities that yield tangible results or contribute to long-term goals. His apartment is functional and tidy, reflecting his preference for order and predictability. While not overtly social, he values genuine connection and intellectual stimulation, finding it in his coding side projects and the strategic depth of chess. He's pragmatic about money, viewing it as a tool for security and enabling future opportunities rather than an end in itself.
Background & daily life
A day in their life
Jesse's typical weekday begins around 7:00 AM with a quick check of his phone for overnight notifications, followed by a simple breakfast. He commutes to work by public transport, listening to a podcast or reviewing chess opening theory on his phone. His workday involves coding, attending meetings, and problem-solving, often requiring deep focus. Lunch is usually a packed meal eaten at his desk while browsing tech news. After work, he might spend an hour reviewing PGNs from his recent online games, analyzing critical moments with a chess engine. Evenings are for dinner, perhaps a short coding session on a personal project, or playing a few rapid games on Lichess before winding down with a book or some NBA highlights. He aims to be in bed by 11:00 PM.
Lifestyle
Jesse lives a relatively routine-driven life, balancing his demanding software engineering job with his personal pursuits. He rents a modest one-bedroom apartment in Lincoln Square, prioritizing location and quiet over luxury. His evenings and weekends are structured around his interests: coding on personal projects, playing chess online, and occasionally catching up on NBA highlights. He's not a big spender, preferring to save money for future goals and investing in tools that enhance his efficiency. Socially, he's more of an introvert, preferring smaller gatherings with close friends over large parties, though he does enjoy the camaraderie of his local chess club.
Work life
As a software engineer at a mid-sized tech company, Jesse's workdays are filled with coding, debugging, and attending stand-ups and sprint planning meetings. He works primarily with Python and JavaScript, focusing on backend services. His team is small and collaborative, but he often finds himself diving deep into complex problems independently. He values clear requirements and efficient workflows, sometimes getting frustrated by ambiguous tasks or unnecessary meetings. He's currently working on optimizing a critical API endpoint, a task that requires meticulous attention to detail and iterative testing. He uses Git for version control and Jira for task management.
Relationships
Jesse maintains a small circle of close friends, mostly met through university or his coding interests. His parents are supportive but live out of state, so their interactions are primarily via phone calls. He has a friendly, professional relationship with his colleagues, respecting their technical skills but not engaging in extensive social interaction outside of work. His chess club acquaintances are more casual, based on shared interest and occasional banter during games.
How they decide
Jesse approaches decisions methodically, weighing pros and cons based on logic and efficiency. He's not impulsive and will often research options thoroughly, comparing features and performance metrics. While he values peer recommendations, especially from technically proficient individuals, his final decision is usually based on his own analysis of what offers the best long-term value and reliability for his specific needs.
How they sound
Speaks in a clear, measured tone, often with a slight upward inflection at the end of sentences when posing a question or seeking confirmation. Uses precise language, avoiding excessive slang or jargon unless discussing technical topics with peers. Tends to be concise, but can elaborate when explaining a complex concept or strategy. His speech is generally calm and even-keeled, reflecting his analytical nature.
Personality traits
- Analytical
- Methodical
- Patient (with systems, less so with people)
- Detail-oriented
- Quietly competitive
- Pragmatic
- Self-disciplined
- Observant
- Systematic
- Reserved
Goals
- Achieve a senior engineering role within the next five years.
- Develop and launch a successful personal coding project.
- Reach a higher Elo rating in chess (aiming for 1800 rapid).
- Become proficient in a new programming paradigm (e.g., functional programming).
- Save enough for a down payment on a condo.
Problems & frictions
- Difficulty finding time to dedicate to both coding side projects and chess improvement.
- Occasional burnout from intense work sprints and the pressure to constantly learn new technologies.
- The challenge of translating theoretical chess knowledge into practical, consistent play during rapid/blitz games.
- Navigating office politics and less structured communication within his team.
- Balancing the desire for self-improvement with the need for social downtime.
Values
- efficiency
- self-improvement
- reliability
- logic
- progress
Interests
- blitz chess
- coding side projects
- NBA highlights
- strategy video games
- learning new programming languages
Media habits
- Follows tech news sites (The Verge, Ars Technica)
- Listens to podcasts during commute (e.g., 'Reply All', 'Lex Fridman Podcast')
- Watches Twitch streams (chess streamers, tech talks)
- Uses Reddit for niche communities (r/chess, r/cscareerquestions)
- Occasional YouTube deep dives on specific programming topics or chess openings