Nadege Pepin — Content Systems Engineer

"The right metric for content quality is time-to-understanding."

I've built documentation functions from scratch at AWS and Pachyderm: contributing to SageMaker, leading the DynamoDB docs team, and owning content and docs infrastructure at Pachyderm. Background in software engineering and technical program management.

I also build the infrastructure underneath — automated pipelines, agentic content systems, and tooling that boost productivity and keep documentation accurate as products move fast.

This is a portfolio of my documentation and content systems work — built from test accounts, design docs, and a working understanding of each system. Know your product, know your customer.

If any of it resonates, let's connect. The Philosophy page has more on how I think about the work.


Featured work All samples →
feature launch AWS

SageMaker Training Plans — Full Feature Documentation

Greenfield documentation for a new GPU capacity reservation feature. API shape was changed based on documentation feedback. Full authorial control from concept to launch at re:Invent 2024.

diagnostic framework AWS

DynamoDB Throttling Diagnostic Framework

Built from scratch on a new team. The four-category taxonomy and reason→metric reference table are deliberate information architecture decisions. First major deliverable on the DynamoDB team.

diagram Pachyderm — sole writer

Pachyderm Production Deployment System

Complete deployment documentation system built and maintained as sole technical writer: cloud-agnostic architecture diagram, infrastructure and ingress layer, full production deployment guides for AWS, GCP, and Azure, and updated documentation for a proxy architecture change. The architecture diagram was carried forward into HPE's official product documentation after the acquisition.

crisis response AWS

EMR + SageMaker Integration — Rebuilt from Stale to Production-Grade

Stale documentation had triggered a prospect escalation. PM and GM requested an urgent update. Went deep independently into IAM role chaining, trust policy construction, and cross-account topology — and delivered a complete rewrite across same-account and cross-account paths, with limited SME support and a hard deadline. The prospect acknowledged the improvement.