Technical Writer · Portfolio

Turning complex
systems into
clear language

I write documentation that non-technical users can act on confidently — and that engineers can trust for accuracy.

View my work →
3
Portfolio projects
End-User
Documentation focus
UX
Design background
EN
International markets
01

About

I'm transitioning into technical writing after years of explaining complex technology to non-technical people — including running a business that taught Android customization to everyday users. That experience taught me that the gap between expert and user is always a documentation problem.

I'm currently completing a diploma in English writing and literature, and building a portfolio that demonstrates real documentation skills: audience analysis, content restructuring, and writing that people can actually follow.

Core principles
→ What → Why → How: every unit of content answers all three
→ Define the audience before writing a single word
→ One concept per step; explain before you ask
→ Scope and non-scope: tell readers what this doc is and isn't
→ Active voice, specific verbs, sentences under 20 words
02

Selected work

UI documentation gap analysis
NextDNS Setup Screen Redesign

The NextDNS Setup screen displays a sensitive Profile ID with no security warning. Identified the gap through forum research, then redesigned the screen with a yellow Caution banner and consistent color coding — so users encounter the warning before the data.

Gap analysis Special Notices Visual risk communication Screenshot annotation
View project →
End-user guide rewrite
Cisco VPN End-User Guide

Cisco's original guide targets IT professionals. I rewrote it for the non-technical remote employee who simply needs to connect. Identified six documentation failures in the source, restructured around the reader's task flow, and added a troubleshooting section covering six common failure scenarios.

Audience analysis Procedure writing Troubleshooting docs Definition writing
View project →
API documentation
Rapyd Payment Links API

Rapyd's original API docs presented workflow steps before defining key concepts and included end-user content irrelevant to developers. Identified five documentation failures, restructured around the developer's task flow, and split the workflow by actor to clarify responsibility.

API docs Persona definition Information hierarchy Actor-based workflow
View project →
03

Skills & tools

I bring a combination of structured writing methodology, UX thinking, and technical fluency. My non-native English background is an advantage: I write with precision rather than habit, and I never assume a reader knows what a term means.
Documentation
  • Audience & persona definition
  • Procedure writing
  • API documentation
  • Content restructuring
  • Scope & non-scope framing
Writing craft
  • What → Why → How structure
  • Active voice & plain language
  • Definition writing
  • Callout & warning design
  • Parallel structure
Technical
  • Markdown & HTML
  • Python (Pillow, scripting)
  • DNS & networking concepts
  • REST API concepts
  • UX design coursework
Languages
  • Hebrew (native)
  • English (professional)
  • Diploma in English writing and literature (in progress)
04

Contact

Let's make your
docs work harder.

Available for junior technical writing roles, freelance documentation projects, and internships with Israeli tech companies.

Email ↗ LinkedIn ↗ GitHub ↗ Phone ↗