Why this persona fits the audience
He is the technical writer at a startup with exactly five people total, founders included. Because the team is small, he writes docs, edits release notes, and occasionally helps support explain new features to users.
- Age: 29
- Location: Remote, US
- Occupation: Technical writer
- Income: $74k-$90k
- Education: Bachelor's degree in English
- Company size: 5
- Years in role: 3
“The most satisfying part of my job is taking something incredibly complex and making it understandable for someone else.”
Ricky Kris, 29, is a dedicated technical writer operating remotely from the US, a role he's held for three years within a lean, five-person developer tool startup. His journey into technical writing wasn't a direct path; he initially pursued an English degree with a passion for literature and storytelling. However, during college, he found himself drawn to the logical structure and problem-solving aspects of technology, particularly through his engagement with complex video games and early forays into coding. This blend of linguistic precision and technical curiosity led him to technical writing. He thrives in environments where clarity and accuracy are paramount, valuing the ability to distill intricate information into accessible guides. His current role perfectly encapsulates this, requiring him to not only write comprehensive documentation but also to act as a bridge between the development team and users, often assisting support with nuanced explanations. This hands-on involvement means he's deeply familiar with the product's intricacies, from its core architecture to its user interface. Ricky's income, between $74k and $90k, allows him a comfortable but not extravagant lifestyle, enabling him to save diligently for future goals like homeownership. He's highly conscientious, meticulously reviewing his work and striving for perfection, which sometimes leads to him spending extra time ensuring every detail is correct. His openness to new ideas, coupled with a reserved nature, means he's receptive to feedback but prefers to process information internally before offering his own insights. He's recently been focused on improving the onboarding documentation for a new API, a project that requires close collaboration with the lead developer and has involved several iterations to ensure it meets the needs of both novice and experienced developers.
Background & daily life
A day in their life
Ricky's typical weekday begins around 8:00 AM with coffee and reviewing his task list. He spends the morning writing or updating documentation, often diving deep into code examples. After a simple lunch, he might have a brief sync with the developers to clarify a feature or review a pull request for documentation changes. The afternoon could involve editing release notes, responding to support queries that require detailed explanations, or researching best practices for a new documentation format. He logs off around 5:30 PM, often feeling a sense of accomplishment from tackling complex information.
Lifestyle
Ricky maintains a structured, quiet lifestyle. He lives alone in a modest apartment, prioritizing a clean and organized living space. His evenings are often spent cooking elaborate meals, delving into science fiction novels, or immersing himself in complex video games. He's not a big spender, preferring to save money for future stability and occasional travel. Socially, he's selective, preferring deep conversations with a few close friends over large gatherings. He enjoys weekend hikes to decompress and clear his head.
Work life
As the sole technical writer at a five-person startup, Ricky wears many hats. His primary focus is crafting clear, accurate documentation for the company's developer tools. This involves writing tutorials, API references, and release notes. Due to the team's size, he also assists the support team by clarifying complex features for users and sometimes even jumping into customer calls to explain technical concepts. He works primarily with Markdown, Git, and a documentation generator, collaborating closely with the two developers and two founders via Slack and scheduled video calls.
Relationships
Ricky is close with his parents, whom he calls weekly. His core social circle consists of a few college friends he met through gaming, with whom he shares a strong bond. He values their opinions but makes most professional decisions independently.
How they decide
Ricky is a research-heavy decision-maker. He gathers information from multiple sources, weighs pros and cons meticulously, and often seeks out examples or case studies before committing to a course of action. He prefers to understand the 'why' behind a decision.
How they sound
Speaks clearly and deliberately, with a moderate pace. Avoids jargon unless explaining technical concepts. His tone is generally calm and measured, rarely raising his voice. He uses precise language and tends to explain his reasoning thoroughly. He might occasionally use mild slang common in online gaming communities but is generally formal in professional settings.
Personality traits
- meticulous
- analytical
- patient
- resourceful
- independent
- observant
- methodical
- calm under pressure
Goals
- Become a recognized expert in developer documentation for niche tools
- Contribute to open-source documentation projects
- Achieve financial independence to pursue personal projects
- Maintain a healthy work-life balance
- Mentor aspiring technical writers
Problems & frictions
- Balancing the need for comprehensive documentation with rapid development cycles
- Limited resources and time to address all documentation gaps simultaneously
- Ensuring technical accuracy when features are constantly evolving
- Communicating complex technical details to a non-technical support team
- Feeling isolated due to the remote nature of his work
Values
- clarity
- precision
- usefulness
- steady delivery
- thoroughness
Interests
- science fiction
- editing
- cooking
- video games
- learning new programming concepts
Media habits
- subscribes to several tech newsletters
- listens to podcasts on writing and software development
- follows specific tech influencers on Twitter
- reads online forums related to his company's product