Clear documentation is what separates teams that scale from teams that repeat the same mistakes. I write technical documentation that your engineers, QA team, and stakeholders can actually use.
I specialize in feature task descriptions with acceptance criteria, QA test case documentation, meeting notes and decision logs, process documentation, and onboarding guides for new team members. Everything I write is structured, specific, and written with the reader in mind, whether that's a developer picking up a task or a founder reviewing progress.
My technical background means I understand what I'm documenting, so nothing gets lost in translation.