Technical Writer · UX Editor · Content Strategist
Complex instructions into intuitive steps. Editorial systems that hold at scale.
Technical writer and editorial lead with 10+ years turning complex product information into documentation people can actually follow. At Google (via Accenture), I led global help center writing teams, and coached nearly every senior writer on my team into a lead role.
How I work
Help content works when a stressed reader can follow it. I write and edit to a 7th grade reading level, free of jargon and nested conditions, so instructions survive translation into other languages.
One-off saves don't scale. I build living checklists, review rhythms, and post-mortems that feed back into the reference, so the same mistake never needs correcting twice.
A lead who reviews everything becomes the bottleneck. I set up office hours where senior writers coached juniors, and nearly all of those seniors became team leads.
Style rules compete. Knowing which rule wins when two collide is the hard skill, so I codify what's codifiable and make space to discuss what isn't.
250+ projects in six months against shifting launch deadlines. Trackers, priority push-back, and honest status updates keep high-volume work moving without drama.
On my own time, I'm teaching Claude to coach me through building editorial workflows and vibe-coding. Never stop learning.
Process
Selected work
Inconsistent work and blind workloads turned editorial review into a bottleneck, and risked embargoed launch docs going live before their products were announced. I built the checklist, the review rhythm, and the coaching structure that fixed it.
Fifty hard-to-read help articles kept losing to launch work: a low-priority, high-volume job with no firm deadline that other teams had repeatedly deferred. A tracker, a cross-shift sync used as a handoff mechanism, and a manufactured deadline shipped all of them.
Developed the content framework and editorial calendar for the website, blog, and social media. Established the company's brand voice, writing standards, and templates, then worked with technical staff and SMEs to close knowledge gaps in the content library.
What managers say
“Through her deep understanding of our workflows and style guide, she helped develop the specialized team's workflow… she has shown a commitment to the growth of the team members by mentoring and supporting junior and senior writers.”
Jimmy Morales Jr., managed Eugene directly at Google
“Eugene's ability to address capacity issues within the pod and her role in boosting team morale were truly commendable… I was not surprised when Eugene was recommended for promotion to a Lead Writer by multiple Team Leads, including myself.”
Steven Martinez, managed Eugene directly at Google
Background
Technical writing · UX writing · Copyediting · Plain language · Style guides · Editorial review
Project tracking · Workload balancing · Coaching & mentoring · Cross-time-zone teams · Standard operating procedures
Google CMS · Google Workspace · HTML · Figma · Salesforce · Asana · HubSpot · Mailchimp · Notion
Claude · ChatGPT · NotebookLM · Wispr Flow. Self-taught, not yet work experience, and labeled honestly.
Austin, TX
The fastest way to reach me is email. I read everything.