About Kennedi Ezeji

A technical writer with experience developing, editing and maintaining documentation for engineering and technology-focused environments, including NASA Headquarters and industrial robotics.

Background

From editorial work to technical documentation

Kennedi began in editorial work as News Editor at Alabama State University’s student newspaper, coordinating writers against a fixed publication schedule while holding a consistent standard across every piece. She completed a B.A. in English with a minor in Political Science in 2021.

At NASA Headquarters she edited IT and communications documentation, standard operating procedures and project guides for accuracy, clarity and readability — and presented editorial revisions and documentation recommendations to senior engineers and scientists.

She then moved into industrial robotics at Premier Tech, creating technical documentation for robotic systems in MadCap Flare and working with engineering teams to verify technical data, tolerances and safety-related instructions before publication.

After stepping back from full-time work to manage family caregiving responsibilities, Kennedi is returning to technical writing. The three portfolio projects on this site were developed independently in 2026 to demonstrate current work.

Kennedi Ezeji
Technical Writer

Kennedi Ezeji

Manville, New Jersey · open to remote

Focus
Technical documentation, SOPs, user & API guides
Industries
Aerospace & government, industrial robotics
Toolchain
MadCap Flare, Capture, Lingo, Microsoft Office
Education
B.A. English, Alabama State University
Download résumé
Experience

Professional experience

Technical writing

Mar – May 2022Montgomery, AL

Technical Writer

Premier Tech
  • Created technical documentation for robotic systems, translating engineering specifications into clear, standardized reference content.
  • Collaborated with engineering teams to verify technical data, tolerances and safety-related instructions before publication.
  • Used MadCap Flare, Capture and Lingo to develop and maintain documentation in accordance with internal quality standards.
Aug 2021 – Apr 2022Virtual

Technical Writing Intern

NASA Headquarters
  • Edited IT and communications documentation, SOPs and project guides for accuracy, clarity, consistency and readability.
  • Developed and maintained documentation across concurrent projects while working within established deadlines and review processes.
  • Presented editorial revisions and documentation recommendations to senior engineers and scientists.

Additional experience

Apr – Nov 2025Cincinnati, OH

Project Manager

BiaRoz Consulting LLC
  • Tracked campaign progress, reviewed promotional materials for accuracy and compliance, and communicated actionable findings to cross-functional stakeholders.
CurrentMorristown, NJ

Substitute Teacher

Morristown School District
  • Follows detailed instructional plans, documents attendance and incidents accurately, and adapts quickly across changing classroom environments.
2018 – 2020Montgomery, AL

News Editor

The Hornet Tribune, Alabama State University
  • Edited and curated content for clarity, accuracy and publication standards while coordinating with writers across multiple deadlines.
Capabilities

Skills & toolchain

Documentation

  • Technical documentation
  • Standard operating procedures
  • User & operator guides
  • Technical editing
  • Documentation QA

Tools

  • MadCap Flare
  • MadCap Capture
  • MadCap Lingo
  • Microsoft Office

Collaboration

  • SME collaboration
  • Engineering review
  • Cross-functional communication
  • Review-cycle management

Content quality

  • Proofreading
  • Content review
  • Information organization
  • Technical research

Education

Alabama State University

Bachelor of Arts in English

Minor in Political Science · December 2021 · GPA 3.5 / 4.0

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.