Why this persona fits the audience
On a Mac at a mid-sized fintech in Seattle, she runs curl, jq, and grep-heavy commands during incident triage and weekly vulnerability checks. She keeps repeatable command lines in a spreadsheet and a private gist that she updates as procedures change.
- Age: 30
- Location: Seattle, WA, US
- Occupation: Security analyst
- Income: US$124k
- Education: BSc Cybersecurity
- Company size: Mid-sized fintech (approx. 450 employees)
- Years in role: 4
“The difference between a disaster and a resolved ticket is usually just three well-written lines of code and the discipline to document them properly.”
Tonya Miller-Johns is a 30-year-old Security Analyst based in Seattle, Washington, where she navigates the high-stakes environment of a mid-sized fintech firm. Holding a BSc in Cybersecurity, she has spent the last four years honing her craft in incident response, specializing in the gritty, unglamorous work of parsing terabytes of log data. Her workspace is a testament to her personality: a clean MacBook Pro flanked by mechanical keyboards and a monitor array displaying cascading terminal windows. Unlike her peers who rely heavily on point-and-click dashboards, Tonya thrives in the command line, constructing intricate pipelines with `curl`, `jq`, and `grep` to extract actionable intelligence during security breaches. Despite her technical prowess, Tonya struggles with the fragmentation of her own knowledge base. She currently manages a sprawling ecosystem of repeatable commands stored across a color-coded spreadsheet and a private GitHub Gist that she updates religiously whenever procedures shift. This manual curation, while effective, consumes valuable time during critical incidents. She recently declined a request to adopt a new enterprise dashboard because its pricing model required a five-year commitment, a decision that highlighted her aversion to vendor lock-in and her preference for modular, scriptable solutions. Outside of work, Tonya is a dedicated runner and amateur radio operator, hobbies that demand patience and technical precision. She views her income of $124k not as a status symbol but as a means to fund her equipment and savings goals, including a future home purchase. Her life is defined by a relentless pursuit of preparedness; whether it's a backup power supply for her ham radio gear or a redundant data pipeline at work, she believes that systems fail, and the only variable within her control is how well she has prepared for that failure.
Background & daily life
A day in their life
Tonya wakes at 5:00 AM, lacing up her worn-out running shoes for a 45-minute jog along the lake, listening to ambient sounds rather than podcasts. By 6:30, she is brewing pour-over coffee and scanning overnight alerts on her dual-monitor setup. At work, she spends the morning triaging a potential phishing campaign, writing a custom `jq` filter to isolate affected accounts. Lunch is a quick salad eaten at her desk while reading a new CVE report. Afternoon hours involve meeting with the engineering lead to explain a vulnerability, followed by updating her private Gist with the new command sequences she developed. Post-work, she might stop at the radio shop to test a new antenna or head to the gym. Evenings are reserved for decompression—reading, cooking, or planning weekend hikes. Before bed, she checks her automated backup scripts to ensure nothing has failed.
Lifestyle
Tonya lives in a quiet, sunlit apartment in Capitol Hill, sharing space with her partner, a graphic designer. Her mornings begin with a 5 AM run along the Burke-Gilman Trail, a ritual she maintains regardless of Seattle's drizzle, followed by black coffee and a review of overnight logs. She is financially prudent, maximizing her 401k match and avoiding debt, but willing to spend on high-quality hardware that extends her workflow. Socially, she prefers small gatherings or one-on-one deep dives over large parties, often bonding over shared hobbies like amateur radio clubs or local running groups. Her weekends are split between maintaining her home lab, tinkering with vintage cameras, and hiking the Cascades to disconnect from digital noise.
Work life
At her mid-sized fintech, Tonya operates as a critical node in the security operations center. Her day is dominated by terminal windows where she constructs complex pipelines using `curl`, `jq`, and `grep` to parse massive JSON logs during incident triage. She spends significant time manually documenting these workflows in a private GitHub Gist and a meticulously maintained spreadsheet, treating them as living documentation rather than static notes. While she collaborates with developers to patch vulnerabilities, she often works independently, troubleshooting false positives and refining detection rules. The pressure is constant but manageable, driven by the need for absolute precision in a sector handling sensitive financial data.
Relationships
Tonya is married to David, whose creative perspective balances her logical approach to life. They have a tight-knit circle of four friends, mostly from university and early career days, who meet monthly for board games or hiking. She is an active member of the local amateur radio club, where she mentors beginners, finding joy in teaching others the intricacies of radio waves. Her professional network is robust but selective; she values peer reviews on her code over social validation, often engaging in technical debates on specialized forums rather than broad social media platforms.
How they decide
Decisions are made through a methodical, research-heavy process. She rarely acts on impulse, preferring to gather data, read documentation, and simulate outcomes before committing to a new tool or strategy. She trusts verified sources and community consensus over marketing hype, often spending weeks testing a potential solution in a sandbox environment. Financial decisions are calculated based on long-term ROI, and she is wary of vendor lock-in, prioritizing flexibility and data portability in all choices.
How they sound
Her speech is precise and measured, favoring clarity over flourish. She uses technical terminology naturally but explains concepts simply when necessary. There is a distinct lack of filler words; she pauses only to think, not to hedge. She avoids hyperbole, rarely saying things like 'amazing' or 'terrible,' preferring 'effective' or 'inefficient.' She tends to speak in short, declarative sentences, especially when discussing protocols or data structures, and her tone remains calm even when discussing stressful incidents.
Personality traits
- Hyper-organized
- Quietly observant
- Deeply focused
- Skeptical of shortcuts
- Meticulous note-taker
- Technically self-reliant
- Calm under pressure
- Privacy-conscious
- Systematic
- Introverted but socially competent
Goals
- Achieve OSCP certification within the next 18 months
- Automate 40% of manual triage tasks using Python scripts
- Build a home emergency communication system using amateur radio
- Run a half-marathon without injury this year
- Contribute to an open-source security tool used by peers
- Save enough for a down payment on a condo in the Pacific Northwest
Problems & frictions
- Fragmented knowledge across spreadsheets, gists, and sticky notes makes retrieval slow during high-stress incidents
- Time-consuming context switching between different CLI tools and GUI dashboards
- Difficulty standardizing command syntax across team members leading to inconsistent reporting
- Limited budget approval for enterprise-grade automation tools despite clear efficiency gains
- Keeping personal documentation secure while ensuring it remains accessible during off-hours
- Fatigue from repetitive manual parsing of log files that could be scripted more elegantly
Values
- preparedness
- privacy
- methodical work
- efficiency
- intellectual rigor
Interests
- amateur radio
- running
- security blogs
- mechanical keyboards
- analog photography
Media habits
- Follows specific security researchers on Twitter/X
- Subscribes to the 'Darknet Diaries' podcast
- Reads r/hacking and r/sysadmin daily
- Listens to lo-fi beats while coding
- Skims The Hacker News for regulatory updates
- Uses RSS feeds for niche technical newsletters