Salvador Reilly

Why this persona fits the audience

He is a master's student in computer science in Seattle who has to write literature reviews, lab reports, and a capstone paper even though most of his day is coding. He is comfortable with spreadsheets and citation managers, and usually drafts directly from source notes.

• Age: 23
• Location: Seattle, WA, USA
• Occupation: Computer science master's student and teaching assistant
• Income: $22k/year from a TA stipend and internships
• Education: Current master's student
• Company size: N/A (Academic Institution)
• Years in role: 1 year as TA, 2 years total in Master's program

“If you can't automate the data collection, you shouldn't be writing the paper; the noise will drown out the signal.”

Salvador Reilly is a 23-year-old Computer Science Master's student based in Seattle, navigating the high-stakes environment of Pacific Northwest academia with a pragmatic, engineer's mindset. Currently living in a modest shared apartment in the University District, he subsists on a $22,000 annual income derived from a Teaching Assistantship and summer internship stipends. This financial constraint forces him to be highly selective with his spending, prioritizing hardware and essential software subscriptions over luxury. Academically, Salvador is a hybrid practitioner; while 60% of his time is dedicated to writing Python and C++ code for machine learning research, the remaining 40% is consumed by the rigid demands of academic writing—literature reviews, lab reports, and his capstone thesis. Salvador's workflow is defined by his reliance on automation and structured data. He is deeply proficient in spreadsheet manipulation and citation management tools like Zotero, often creating custom scripts to parse bibliographies or organize PDF metadata. Unlike many peers who struggle with the transition from coding to writing, Salvador views the latter as another system to be optimized, albeit a messy one. He typically drafts directly from his annotated source notes, avoiding the temptation to rely on generative text that lacks factual grounding. However, the sheer volume of reading required for his research creates a bottleneck; managing the semantic connections between hundreds of papers is a constant friction point. Recently, Salvador faced a decision regarding his research methodology: whether to adopt a new automated summarization tool or stick to manual extraction. Given his high conscientiousness and skepticism toward black-box algorithms, he opted for a middle ground, manually verifying summaries generated by open-source models before integrating them into his notes. This decision highlights his core value of technical rigor; he refuses to compromise the integrity of his data for speed. Despite the pressure of impending deadlines and the grueling schedule of a TA, Salvador remains focused on his long-term goal of publishing in a top-tier conference. He is not looking for a magic wand to write his paper for him, but rather a tool that respects the precision of his workflow and ensures that every citation he includes is verifiable. His life is a balance of code, caffeine, and the relentless pursuit of a clean, efficient solution to complex problems.

Background & daily life

A day in their life

Salvador wakes up at 6:30 AM to avoid the rush, grabbing an instant oatmeal while checking GitHub notifications. By 7:30, he is at the university library, setting up a dual-monitor rig with a local Jupyter notebook server. From 8:00 AM to 12:00 PM, he focuses on training a model for his capstone, constantly refactoring code to optimize memory usage. Lunch is a quick sandwich eaten at his desk while reading the latest arXiv abstracts. Afternoons shift to TA duties: grading quizzes and responding to Slack messages from undergraduates. Around 4:00 PM, he switches contexts to writing, pulling notes from his Zotero library to draft sections of his literature review. He works until 8:00 PM, then heads home to cook a simple meal, occasionally gaming or reading sci-fi to decompress. Before bed, he spends 20 minutes updating his Trello board for the next day, ensuring no tasks are missed.

Lifestyle

Salvador lives in a cramped, third-floor walk-up in Seattle's University District, sharing rent with two fellow engineers. His weekends are rarely free; Saturday mornings often involve cleaning the shared kitchen or grocery shopping at a discount store, while evenings are reserved for the capstone project. He is frugal, treating his $22k annual income as a strict budget where every dollar spent on software must yield immediate utility. He maintains decent health through occasional runs around Gas Works Park but often sacrifices sleep for debugging sessions. Socially, he prefers one-on-one coffee chats over large gatherings, finding small talk draining but enjoying deep technical debates with peers.

Work life

His days oscillate between coding Python scripts for his research and grading undergraduate assignments as a TA. The reality is a jarring split: 60% of his time is spent building models in VS Code, while 40% is consumed by the bureaucratic nightmare of academic writing. He uses Zotero religiously, organizing hundreds of PDFs into tagged collections. His greatest friction is the transition from logical code blocks to fluid academic prose; he finds manual citation formatting tedious and prone to human error. Coworkers are mostly silent in the library or engaged in heated debates about transformer architectures. The pressure comes from the capstone deadline looming alongside mid-term grading loads.

Relationships

Salvador is close to his parents in Oregon, who call weekly to check on his well-being rather than his grades. He has a tight-knit group of three graduate friends who meet for dinner once a month, mostly to vent about advisor expectations. His primary influence is his thesis advisor, Dr. Aris Thorne, whose high standards drive Salvador's meticulous approach. He has few casual acquaintances outside the CS department, viewing social circles as energy drains unless they contribute to professional networking or intellectual exchange.

How they decide

Salvador employs a rigorous, hypothesis-testing approach to all decisions. He does not impulse buy; instead, he seeks documentation, reads user reviews on niche forums, and tests free trials against his own specific workflow constraints before committing. He values transparency in pricing and feature sets over marketing fluff. If a tool promises efficiency gains, he expects proof via benchmark data or a clear logic flow. He is influenced heavily by peer recommendations within the technical community, particularly those who have demonstrated long-term utility rather than short-term novelty.

How they sound

His speech is precise, measured, and devoid of filler words. He tends to speak in complete sentences with a slightly formal cadence, even in casual settings. He avoids hyperbole, preferring qualifiers like 'statistically significant' or 'probabilistically.' When discussing technology, he uses jargon freely but explains it clearly if asked. He rarely uses slang, viewing it as imprecise. In arguments, he remains calm and relies on evidence rather than emotion. He speaks slowly when explaining complex ideas, pausing to ensure logical clarity.