Why this persona fits the audience
Provides day-to-day IT support for a 12-person nonprofit office. He handles help requests that involve moving PDFs, login steps, and setup notes between a Windows desktop, a Linux admin laptop, and an Android phone for staff who use different devices.
- Age: 46
- Location: Seattle, WA, US
- Occupation: IT support specialist
- Income: $72k-90k
- Education: Associate degree in information systems
- Company size: 12
- Years in role: 8
““Everything should be built to last, and that applies to systems and processes just as much as it does to the advice you give.””
Ruben Tremblay has been the linchpin of IT operations for a small Seattle-based environmental nonprofit for the past eight years. Hailing from a working-class background in a smaller Washington town, he developed an early fascination with how things worked, a trait that naturally led him towards computers. He earned an Associate's degree in Information Systems from a local community college, viewing it as a practical, efficient path to a stable career. Unlike many in his field, Ruben isn't driven by a desire for cutting-edge technology or rapid career advancement. His primary motivations are stability, security, and the satisfaction of ensuring systems run smoothly and reliably for his colleagues, who he sees as integral to the organization's mission. He meticulously manages the nonprofit's modest IT infrastructure, which includes a mix of Windows desktops, a handful of Linux workstations used by system administrators, and various mobile devices. His daily work involves bridging the gaps between these platforms, helping staff transfer files like PDFs, navigate login procedures across different systems, and set up new devices. He recently spearheaded the migration of their shared file storage from a clunky, outdated server to a more reliable cloud-based solution, a decision driven by concerns over data security and the increasing frequency of hardware failures. This project required extensive research into options that balanced cost with robust security features, a process Ruben relished for its detailed problem-solving. He’s a firm believer in open-source solutions, often leveraging them to extend the lifespan of existing hardware and reduce software licensing costs, a practice that aligns perfectly with the nonprofit's budget constraints. His approach to IT is deeply rooted in process discipline; he maintains detailed documentation, adheres to strict patching schedules, and prioritizes proactive maintenance over reactive fixes. He views his role not just as a technician, but as a guardian of the organization's digital infrastructure, ensuring its stability so that the vital work of the nonprofit can continue uninterrupted.
Background & daily life
A day in their life
Ruben's typical weekday begins around 6:30 AM. After coffee and a quick scan of overnight system logs on his personal laptop, he’s on his way to the nonprofit by 8:00 AM. His mornings are usually spent addressing urgent help desk tickets: a staff member can't access a shared drive, another needs a PDF converted, or someone’s laptop is behaving erratically. He meticulously documents each resolution in his ticket system. Lunch is a packed sandwich eaten at his desk while he might browse tech forums. Afternoons are dedicated to scheduled tasks like software updates, security scans, or user onboarding, interspersed with more user requests. He aims to leave by 5:30 PM, but often stays a bit later if a critical issue arises, ensuring the systems are stable before heading home.
Lifestyle
Ruben lives a quiet, structured life in a modest apartment in Ballard. His routine is predictable: early mornings with strong coffee, a careful review of overnight system alerts, then the commute to the nonprofit. Weekends are often spent tinkering with his home server, volunteering at a local food bank on Saturdays, and catching up on reading or documentaries. He's not one for spontaneous outings, preferring to plan social interactions. Financial habits are conservative; he prioritizes saving for potential future needs and maintains a solid emergency fund, viewing security as paramount. He enjoys the predictable rhythm of his life.
Work life
As the sole IT support for a small nonprofit, Ruben's days are a constant juggle of user-facing requests and underlying system maintenance. He’s the go-to for everything from forgotten passwords and printer jams to setting up new employee workstations and troubleshooting the occasional server hiccup. His coworkers, while appreciative, often have urgent, immediate needs that disrupt his planned tasks. He relies heavily on his meticulously organized internal knowledge base and a suite of open-source monitoring tools to keep operations smooth. The pressure comes from ensuring minimal downtime for mission-critical tasks, especially when resources are stretched thin.
Relationships
Ruben is single and lives alone, but maintains a cordial relationship with his sister who lives on the East Coast. His closest connections are formed through his volunteer work and online communities focused on Linux and IT. He has a few long-time acquaintances from previous jobs whom he occasionally exchanges technical articles with, but he's not deeply enmeshed in a social circle. His coworkers at the nonprofit appreciate his steady presence and problem-solving skills.
How they decide
Ruben is highly cautious and research-driven. He prefers to thoroughly evaluate options, often creating comparison spreadsheets or testing solutions in a sandbox environment before implementing them. He values proven reliability and efficiency over novelty, and will spend significant time understanding the underlying mechanics of any tool or process before committing to it. Peer recommendations carry some weight, but only if they are backed by detailed, technical justifications.
How they sound
Speaks in a calm, measured tone, often pausing to choose precise technical terms. Avoids slang and overly casual language, even in informal settings. His cadence is steady and unhurried, reflecting his methodical nature. He tends to explain the 'why' behind solutions, not just the 'how.' He is clear, concise, and avoids jargon when speaking with non-technical staff.
Personality traits
- methodical
- patient
- detail-oriented
- dependable
- resourceful
- reserved
- problem-solver
- pragmatic
Goals
- Develop a more robust disaster recovery plan for the nonprofit
- Become more proficient in Ansible for automation
- Contribute to an open-source project, even in a small way
- Maintain a stable and secure IT environment for his organization
- Save enough to eventually replace his aging car with a more reliable model
Problems & frictions
- Limited budget for essential software upgrades and hardware replacements
- Inconsistent technical literacy among staff, leading to frequent basic support requests
- Balancing urgent user needs with long-term system maintenance and security patching
- Lack of dedicated IT budget for advanced tools or external support
- Keeping up with evolving security threats on a small team with minimal resources
Values
- security
- process discipline
- service
- reliability
- efficiency
Interests
- Linux
- help desk tooling
- volunteering
- open-source software
- local history podcasts
Media habits
- Reads tech blogs (Ars Technica, LWN.net)
- Listens to podcasts during commute
- Checks Reddit for tech solutions
- Uses YouTube for tutorials
- Skims local news online