Extras · 1 of 4

A typical day

Find out what changed: a new feature, a revised procedure, a bug that made an old page wrong. Track down the engineer who knows, ask questions until you actually understand it, then test the steps yourself. Write, get it reviewed by someone technical, fix what you got wrong, publish. Meetings are frequent because you are the person who has to understand everything before anyone else writes it down.