Why this persona fits the audience
She works on a 6-person product team and uses a self-made bookmarklet, saved prompt snippets, and browser copy-paste to turn docs pages, release notes, and support articles into drafts for Claude and Copilot. Her process is lightweight and technical, with everything tracked in linear notes and a shared doc.
- Age: 33
- Location: Barcelona, Spain
- Occupation: Technical Writer
- Income: €61k salary
- Education: Master's degree in technical communication
- Company size: 6 employees
- Years in role: 4
“Documentation isn't just words on a page; it's the contract between what we build and what the world can actually do with it.”
Gloria Arenas Meza is a thirty-three-year-old technical writer embedded in the high-velocity environment of a Barcelona-based devtools startup. Holding a Master's degree in Technical Communication from Pompeu Fabra University, she spent her early career in corporate settings before realizing the rigid structures of large enterprises stifled the kind of iterative, hands-on work she craves. Four years ago, she joined the six-person startup, a move that immediately placed her in the unique position of being the sole voice for their entire user base. Unlike her predecessors, Gloria did not rely solely on traditional authoring tools; she recognized early on that the pace of development rendered standard workflows obsolete. Consequently, she engineered her own solution: a suite of browser-based automations and a rigorous system of prompt engineering using free-tier AI models. She spends her evenings coding JavaScript bookmarklets and Python scripts to streamline the ingestion of raw data into her documentation pipeline. This DIY approach allows her to maintain a level of precision and speed that would be impossible with a larger team or more bureaucratic processes. Despite earning a solid €61,000 annually, she remains financially conservative, viewing money primarily as a resource to buy time-saving technology or security. Her workspace is a testament to her philosophy: a clean, ergonomic setup dominated by dual monitors displaying code editors, documentation wikis, and chat interfaces. She is currently navigating the complexities of scaling her documentation practices as the company prepares for a Series A funding round, knowing that investor scrutiny will demand flawless, comprehensive guides. While she enjoys the autonomy her role provides, she frequently grapples with the isolation of being the only writer, often finding herself bridging the gap between frustrated developers and confused end-users. Her recent decision to invest time in learning Rust was driven by a desire to understand the underlying mechanics of the product, allowing her to write documentation that anticipates future architectural shifts rather than just reacting to current ones.
Background & daily life
A day in their life
The alarm goes off at 6:30 AM, and Gloria is already up for a 45-minute run through the quiet streets of Gràcia. Back home, she brews a strong coffee while scanning the overnight commit logs and Jira tickets. By 8:30 AM, she joins the daily stand-up via Zoom, listening intently to the engineers' updates on the new authentication module. Once the meeting ends, she dives into her core task: rewriting the SDK integration guide. She opens her custom bookmarklet, highlights a section of the live beta app, and pastes the context into her local AI agent to generate a draft structure. She spends the next two hours manually verifying every code snippet, ensuring the syntax matches the latest Rust release. Lunch is a quick salad eaten at her desk while watching a tutorial on vector databases. The afternoon is reserved for meetings with product management to clarify ambiguous features, followed by a final push to sync the Linear board with the shared Google Doc. She leaves the office by 6:00 PM, avoiding overtime unless absolutely necessary, and spends her evening reading fiction or working on a personal automation script.
Lifestyle
Gloria lives in a sunlit, slightly cluttered apartment in Barcelona's Gràcia district, sharing space with two fellow creatives who work remotely. Her days revolve around early morning runs along the Diagonal avenue, followed by a strict routine of coffee and code review. She maintains a minimalist digital life but keeps her physical desk crowded with ergonomic gear, a second monitor for documentation, and a notebook for rapid sketching of workflows. Financially, she is cautious but not frugal, prioritizing spending on high-quality hardware and software that saves time over luxury goods. Socially, she prefers small, intellectual gatherings over large parties, often meeting friends for tapas after work to discuss books or new AI models rather than office gossip.
Work life
As the sole technical writer in a six-person engineering-first startup, Gloria carries the entire burden of external documentation while acting as the bridge between complex backend logic and user understanding. Her days are a mix of reading raw release notes from engineers, interviewing product managers, and manually constructing API reference guides. She relies heavily on her custom-built bookmarklet to scrape context from internal dashboards, pasting it into LLMs to generate first drafts which she then rigorously edits for tone and accuracy. The pressure is constant; with a small team, any ambiguity in the docs leads directly to support tickets. She spends her mornings in Linear tracking tasks and her afternoons wrestling with version control conflicts in shared markdown files, constantly refining her own automation scripts to stay ahead of the documentation backlog.
Relationships
Gloria is close to her parents in Madrid, visiting monthly for Sunday dinners where they discuss family matters rather than tech. Her professional network is her primary social circle; she mentors junior writers on LinkedIn and has a tight-knit group of four peers in the Barcelona tech scene who meet bi-weekly for 'docs workshops.' She values her relationship with the engineering lead, who acts as her primary technical confidant, though their differing priorities (speed vs. clarity) sometimes cause friction. She has no children yet, focusing her energy on her career and her cycling club, which provides her with a necessary non-work outlet.
How they decide
Gloria approaches decisions with a methodical, evidence-based framework. She rarely adopts a new tool or habit based on marketing hype or peer pressure alone. Instead, she constructs a mental model of how a solution fits into her existing ecosystem, often running a low-stakes pilot or building a quick prototype to verify efficacy. She is willing to pay for solutions that demonstrably save time or reduce cognitive load, but she is deeply skeptical of tools that add friction or require significant learning curves without clear ROI. Her purchasing power is exercised only after extensive research and comparison against her current 'do-it-yourself' stack.
How they sound
Her speech is articulate and precise, often pausing to choose the exact word to avoid ambiguity. She speaks with a calm, measured cadence, typical of someone used to explaining complex systems clearly. In professional settings, she avoids jargon when speaking to non-technical stakeholders but switches effortlessly to dense acronyms and specific terminology with engineers. She tends to use phrases like 'Let's validate that assumption' or 'What's the edge case here?' She rarely raises her voice or engages in emotional debate, preferring to let data and logic drive the conversation. Her tone is helpful but firm when defending documentation standards.
Personality traits
- Meticulously organized
- Quietly analytical
- Tool-obsessed
- Pragmatically skeptical
- Deeply empathetic to users
- Efficient communicator
- Self-taught coder
- Process-oriented
- Calm under pressure
- Independent problem solver
Goals
- Achieve industry recognition for creating the most developer-friendly API docs in the fintech sector
- Automate 80% of repetitive documentation maintenance without sacrificing human oversight
- Transition into a Lead Documentation Engineer role within three years
- Contribute an open-source tool for automated documentation testing to the community
- Maintain a healthy work-life balance despite the fast-paced startup environment
- Master Rust to better understand the core product architecture
Problems & frictions
- Fragmented information sources requiring manual aggregation before drafting
- Time constraints preventing deep dives into complex architectural changes
- Difficulty maintaining consistency across multiple documentation channels
- Lack of dedicated resources for thorough user testing of documentation clarity
- Rapid feature velocity outpacing the speed of manual documentation updates
- Balancing the need for immediate fixes with long-term structural improvements
Values
- documentation quality
- precision
- useful tooling
- developer empathy
- process efficiency
Interests
- developer documentation
- browser automation
- AI-assisted writing
- Rust programming basics
- urban cycling
- indie game design
Media habits
- Reads the 'Changelog' podcast daily during commutes
- Scans Hacker News and Reddit r/technicalwriting before breakfast
- Watches deep-dive coding tutorials on YouTube late at night
- Subscribes to niche newsletters about API design patterns
- Uses GitHub to track personal productivity scripts
- Follows specific indie hackers on Twitter/X for workflow tips