Senior Technical Writer

David Golden

I get your customers off the support page and back to their tasks.

Structured content your customers can find — and your AI support tools can actually use.

See my work Get in touch
Download résumé
20 yrs Technical Writing
90% Docs Shipped Same-Day
1,700+ Support Cases Cited (2018–2025)
145,086 Records Migrated

Selected Work

Each project below is a problem I was handed and a result I can point to. Samples are linked where they're publicly accessible.

Knowledge Base · MadCap Flare · Salesforce · XML

Enterprise Knowledge Base — Pitney Bowes Shipping & Mailing

Problem
Support volume was high and customers had no reliable self-service path for enterprise shipping and mailing products.
What I did
Owned and wrote the full knowledge base for multiple product lines — user guides, admin guides, installation guides, and KB articles — published in Salesforce Knowledge across SaaS and hardware product lines on an Agile release schedule. Used Microsoft 365 Copilot in the review cycle to improve article clarity and accessibility. Several releases included localization across 6 languages in addition to US English.
Result
Delivered docs and KB the same day as the product — 90% of releases. Articles resolved 1,700+ support cases (2018–2025). Top articles referenced 700+ times each.

Compliance Docs · 21 CFR Part 11 · Regulated

Clinical Research System Documentation — Pfizer

Problem
Enterprise clinical research systems required documentation that could survive an FDA audit — accurate and version-controlled throughout the review cycle.
What I did
Wrote and maintained compliance documentation and SOPs under 21 CFR Part 11, working directly with Regulatory Affairs, Legal, Quality, and Engineering throughout the review cycle.
Result
700+ global users trained; 100% completion rate. Documentation cleared regulatory review.

Interactive · Articulate Storyline · UX

Guided Troubleshooting Tool — Pitney Bowes

Problem
Users with hardware and software issues needed a faster path to resolution than reading a manual — especially under time pressure in shipping operations.
What I did
Designed and built an interactive solution finder in Articulate Storyline. Users answer a short branching sequence; the tool routes them to the right fix without involving support.
Result
Users get to a fix without calling support. The branching logic handles triage that would otherwise go to a technician.

Taxonomy Design · Information Architecture · Python · MySQL · Flask

Content Engineering & Taxonomy Design — WPKN 89.5 FM

Problem
No controlled vocabulary. No relational schema. No search. A 60-year music catalog (dating to 1963) had grown across paper cards, dBASE, Access, and Excel — with 23,772 digital files sitting on a server drive, completely uncatalogued.
What I did
Standardized 110,000+ genre tags into 43 controlled vocabulary terms. Catalogued the digital collection from scratch. Migrated 145,086 records into MySQL across 6 tables with referential integrity. Built a Flask search interface with artist, title, genre, style, and local-artists filters — presented as a live proof of concept to the board in April 2026.
Result
99,553 records now searchable in real time. Access and Google Drive spreadsheets retired. Deploying to library.wpkn.org.

The Speech Without the Elevator

Right now I'm writing and managing labeling for medical devices at Medtronic, on a contract through Planet Pharma. That means running two labeling updates and a new product introduction at the same time, working across quality, engineering, and marketing. Most of the job is interviewing: talking to engineers and other stakeholders to get the content right, then choosing formats that satisfy both the regulation and the reader. I also support CAPA documentation and audits.

My career has run through enterprise shipping and mailing software at Pitney Bowes and FDA-regulated clinical research systems at Pfizer — two environments where unclear documentation creates real, measurable problems. I get people off the support page and back to their tasks.

MadCap Flare has been at the center of how I work. Eighteen years of single-source authoring, conditional content, and localization across six languages. Knowledge base programs built to carry a company's primary support deflection load. Python and SQL come in when the documentation needs tooling around it: migration scripts, automation, the occasional Flask app.

Copilot and Claude Code are in the workflow. The content I produce is structured so AI tools can actually use it.

Based in Milford, CT, available for full-time roles and fractional engagements. If you're moving off Word and SharePoint into something topic-based and task-driven, I've done that migration work: FrameMaker, InDesign, and Word content into structured Flare projects. Get in touch.

Two ways to work together

I'm currently in a contract role at Medtronic, and I'm still looking for the right full-time opportunity, along with fractional engagements.

Full-time role

I'm in a contract role right now, but I'm actively looking for what's next. If you're hiring a senior technical writer or documentation lead with deep enterprise and regulated-environment experience, I'd like to hear from you. Remote, hybrid, and on-site in the CT/NY metro area all work.

Send me a note

Fractional retainer

If you need a senior writer for a specific project or quarter without a full-time commitment, that's the retainer model. I work with companies on a monthly basis.

Start the conversation

Typical engagement: 20–30 hrs/month