Free Sample
The Complete Guide to Becoming An Editor
How to decide if editing is right for you, what it really pays, and how to break in without a single published credit
by Alumigogo Books
Chapter 1: What Does a Editor Actually Do?
Let's get one thing out of the way immediately: an editor's job is not to fix your grammar. Grammar is a small part of it, and for some editors, it's barely a part at all. The job is to make a piece of writing achieve its purpose. Sometimes that means the words are wrong. More often, it means the structure is off, the tone is inconsistent, the argument is weak, or the reader will be confused on page three because of something that happened on page one. You are the reader's advocate, the author's partner, and occasionally the last line of defense against a serious embarrassment.
To understand a typical day, you have to understand the roles. A development editor works on the big picture: structure, argument, pacing, clarity. They ask the questions that shape a book, an article, or a report before the writing is polished. A copy editor works on the sentence-level: grammar, style, consistency, typos, and factual errors. A proofreader is the final pair of eyes before something goes to print or live online. Small publishers often combine these roles into one "editor" who does everything. Large publishers, tech companies, and agencies split them up.
The Core Responsibilities
If you walk into an edit, you're going to spend your time doing one of three things. The first is structural editing. You read a draft, maybe a manuscript or a long article, and you map out its problems. This