Why this persona fits the audience
Keeps technical articles, RFCs, and conference videos in Chrome bookmarks and a shared doc for a 3-person engineering pod; checks the list from laptop, tablet, and work phone.
- Age: 31
- Location: Austin, United States
- Occupation: Senior Software Engineer
- Income: $145k base
- Education: B.S. in Computer Science
- Company size: 15-20 employees (grew from 3 when he joined)
- Years in role: 4
“I'd rather spend 10 hours solving a problem in a way that scales than 10 minutes with a hack that'll come back to bite us.”
Felix Spinka grew up in a suburban Ohio town where his interest in computers began with taking apart his family's Dell desktop. He earned his Bachelor's in Computer Science at Ohio State, where he discovered a knack for distributed systems and started attending open source contributor meetups. After stints at a fintech company and a healthcare startup, he joined a three-person team in Austin that was building container orchestration tools. Four years later, that team has grown to 15, and Felix is one of its most respected technical leaders. His current project is leading a complete rewrite of their scheduler component, a challenge he's relishing despite the pressure. Felix is meticulous about documentation - he maintains extensive notes on every architectural decision his team makes, though he's frustrated by how these notes have become fragmented across tools. His current workflow involves heavy Chrome bookmark use, a shared Google Doc, and various .md files, but he's increasingly spending time searching rather than using the information he's collected. On weekends, you'll find him either on his mountain bike or at his desk working on personal projects, particularly anything involving Rust. Felix has a strong preference for open source tools, though he's pragmatic about when to build versus buy. He's flown under the radar professionally, preferring to let his code speak for him, but lately his colleagues have been encouraging him to increase his technical visibility. His biggest professional frustration is finding quality technical writing - he'd rather watch a conference talk than read a blog post, but managing his collection of reference materials has become a significant time sink. Personally, he's perfectly happy with his current living situation, though his parents occasionally hint that 'the next step' would be finding a long-term partner. His largest financial investment is in his bike (a Santa Cruz Chameleon), but he's also saving for a possible future home with space for a proper basement server rack. What keeps him up at night isn't technical challenges, but rather the nagging feeling that he's falling behind in keeping up with the ever-evolving landscape of software development.
Background & daily life
A day in their life
Felix's day starts with a 5:30 AM bike ride to his standing desk, where he'll write code without interruptions until the 10 AM daily standup. Between that and the 2 PM sync, he'll work through his carefully prioritized JIRA tickets, pausing to update his shared doc with new findings. He uses a specific Chrome profile for work bookmarks, but keeps finding himself saying 'I know I saw that article' while researching a design issue. After work, he'll swing by a local coffee shop to meet friends, or if alone, work on his home automation project until 9 PM. He'll wind down by reading technical books on his Kindle (physical books are too hard to carry when traveling) before falling asleep to ambient bike trail videos.
Lifestyle
Felix lives in a minimalist condo near Lady Bird Lake, where his biggest luxury is a dedicated home office with a standing desk and three monitors. He wakes up at 5:30 AM to ride his gravel bike 30 minutes to work most days, using the time to process the day ahead. His weekends alternate between mountain biking around Barton Creek with friends and working on side projects in Rust. He budgets meticulously, builds his own desktops from parts, and strongly prefers quality tools that 'just work.' Socially, he's more comfortable in small groups, often hosting 'tech tasting' nights where colleagues compare development tools over barbecue. He's single but content, having dated one woman seriously since moving to Austin and maintaining a few close friendships from college.
Work life
As one of three senior engineers at a startup that builds container orchestration tools, Felix spends most days deep in architectural decisions for a major refactor. His pod uses a shared spreadsheet for tracking decisions (with tabs for RFCs, meeting notes, and backlog items), but the system feels increasingly brittle as they scale. He's currently frustrated by how often he finds himself saying 'I know I bookmarked that' while hunting through Chrome bookmarks during design reviews. The team's sync time is sacred, but outside of that, Felix prefers async communication via Slack threads and GitHub PRs. He's the de facto documentation keeper, maintaining a Notion space that's become the source of truth for their system.
Relationships
Felix's closest relationships are with his three engineering colleagues, whom he sees more than his family. He talks to his parents in Ohio every other Sunday, though they don't understand what he does. His best friend from college is now in Seattle, but they meet up quarterly to bike and argue about programming languages. He has a loosely defined social circle through Austin tech meetups and mountain biking groups. His ex-girlfriend (now a project manager at a different company) still occasionally consults him about technical questions, which he finds both flattering and awkward.
How they decide
research-heavy but pragmatic; builds evaluation spreadsheets for major purchases but defaults to 'good enough' for personal tools; trusts peer recommendations but verifies claims himself; values long-term reliability over shiny features
How they sound
Spoken like a slightly more energized version of documentation he writes - clear, precise, occasionally self-deprecating. Uses technical jargon appropriately but will explain concepts patiently when necessary. Cadence is measured, with frequent pauses to think. Avoids small talk, but when engaging, becomes opinionated and thorough. Often uses phrases like 'The way I've been thinking about this is...' or 'I don't mean to be that guy, but...'.
Personality traits
- constantly fact-checks his own opinions
- builds homebrew utilities to automate personal workflows
- insists on reading documentation before asking for help
- gets frustrated when people skip debugging steps
- keeps a list of every technical debt item in his projects
- prefers working early mornings before team stands up
- mentally refactors code while falling asleep
- has a spreadsheet for spreadsheet templates
- will happily debate system design choices for hours
- writes detailed but slightly dry commit messages
Goals
- Complete the complete rewrite of their core scheduler component
- Release one meaningful open source contribution this year
- Get his mountain biking skill to the point where he can handle rocky descents
- Build a proper automated home lab for testing distributed systems
- Take a proper vacation without checking work emails (hasn't in 3 years)
- Learn enough about supply chain security to give a talk at a local meetup
Problems & frictions
- Chronic 'information accumulation' without proper organization
- Team documentation is becoming a bottleneck as they scale
- Physical inbox of receipts/tech manuals is threatening to overflow
- Finding time for personal projects while balancing intense work demands
- Difficulty keeping up with all the tools his team is expected to know
- Needs a better way to track learning materials across devices
Values
- technical depth
- efficiency
- autonomy
- lifelong learning
- work-life harmony
Interests
- open source
- dev tooling
- mountain biking
- Austin indie music scene
- bulletproof coffee
Media habits
- subscribes to 12 tech newsletters
- listens to tech podcasts during commutes
- watches conference talks on 1.5x speed
- bookmarks everything but rarely goes back