Technical Writer · Manville, New Jersey

Clear documentation for complex systems

Technical writer developing, editing and maintaining documentation for engineering and technology teams — user guides, standard operating procedures and reference content — with experience at NASA Headquarters and in industrial robotics.

NASA Headquarters
Technical writing intern
Premier Tech
Robotic systems documentation
MadCap Flare
Capture · Lingo
B.A. English
Alabama State University
Expertise

Areas of expertise

From first draft through approval and release — working with engineers and subject-matter experts to make technical information accurate, usable and consistent.

01

User guides & procedures

Operator guides, API quick-start guides and work instructions — prerequisites stated, steps in the order they happen, and warnings placed where they are needed.

User guidesAPI quick-startsWork instructions
02

SOPs & process documentation

Standard operating procedures with defined roles, review criteria, approval steps and document control — written so a team can actually follow them.

SOPsReview workflowsDocument control
03

Technical editing & QA

Reviewing documentation for accuracy, completeness, clarity and consistency, and verifying technical content with the engineers who own it before publication.

Technical editingDocumentation QASME review
Work samples

Recent portfolio projects

All work
First page of the UR3e Operator Quick-Start Guide
01 — Independent portfolio project

UR3e Collaborative Robot — Operator Quick-Start Guide

A ten-page quick-start guide covering the full operational cycle of a six-axis collaborative robot — pre-operation checks, power-on, arm initialization, running a program, shutdown and basic troubleshooting — written for operators using the system for the first time.

Audience
Trained operators new to the UR3e
Format
10-page guide, tables & checklists
Document
UR3e Quick-Start Guide, v1.0
Date
September 2026
First page of the Technical Documentation Review SOP
02 — Independent portfolio project

Technical Documentation Review — Standard Operating Procedure

A four-page standard operating procedure defining how technical documentation is reviewed, revised, approved and released — covering roles and responsibilities, five review criteria with assigned reviewers, a six-step approval sequence, and document control requirements.

Audience
Writers, SMEs, editors, approvers
Format
4-page SOP, roles & criteria tables
Document
SOP-DOC-001, v1.0
Date
September 2026
First page of the Open-Meteo API Quick-Start Guide
03 — Independent portfolio project

Open-Meteo Weather API — Quick-Start Guide

A five-page quick-start guide for developers new to the Open-Meteo Weather Forecast API — covering the base URL and endpoint, request parameters, a first forecast request, reading the JSON response, and troubleshooting error responses.

Audience
Developers new to the Open-Meteo API
Format
5-page guide, parameter & error tables
Document
Open-Meteo Quick-Start Guide, v1.0
Date
September 2026
Available for work

Open to new opportunities

Open to technical writing roles in software, hardware or process documentation — remote, or in the New York–New Jersey area.

Accuracy first

Specifications, tolerances and procedures verified with engineering before anything is published.

Built for the reader

Documentation structured around the task someone is performing, not around the system diagram.

Review-ready

Version control, approval status and revision history on every deliverable.