Free editor interview questions for small businesses: six sets on accuracy, judgment, writers, and deadlines, plus a paid test edit brief and a scorecard.
Six question sets written for the employer side: accuracy, editorial judgment, working with writers, deadlines and capacity, plus a paid test edit brief and a 1-to-5 scorecard. Every question states why it is worth asking. Download as DOCX.
The first editor I ever interviewed talked beautifully about prose for forty minutes, and I hired on the strength of the conversation. Three weeks later I understood the problem: she was a proofreader with excellent taste, and I had needed someone to decide what we published at all. The interview had never tested the thing the job actually required, because I did not know how to ask.
Editing is unusually hard to interview for. The finished work proves the writer more than the editor, everybody sounds articulate about writing, and if you are not an editor yourself you have no way to grade the answers as you hear them. So the questions have to do the work instead.
At FirstHR, we build for small businesses hiring without an HR department, where the owner runs the interview between everything else. These six sets are written for the employer side: every question states why it is worth asking and what a strong answer sounds like, plus a paid test edit brief and a scorecard.
TL;DR
Interview an editor on four things: accuracy and mechanics, editorial judgment, how they work with writers, and reliability against a deadline. Ask why each change was made rather than whether the writing sounds good, request a before-and-after pair with tracked changes instead of a finished sample, and run one short paid test edit that every finalist gets identically. Six question sets and a scorecard, as DOCX.
Which Editor Are You Actually Hiring?
Editor is four jobs under one title, and the first decision is which one you are buying. A copy editor works on correctness and consistency. A line editor works on how sentences carry meaning. A managing or content editor decides what gets commissioned, shapes structure, runs the calendar, and manages the writers. Specialist editors work in video, photo, or technical documentation.
The distinction matters because the pools barely overlap. An excellent copy editor is often a poor content owner, and a strong content editor may be a mediocre proofreader. If you hire for accuracy and then expect someone to own the publishing schedule, you will conclude within a quarter that the hire failed, when in fact the brief did. Settle the split before you post, and write it into the editor job description.
Responsibility
Copy Editor
Managing Editor
Grammar, spelling, punctuation, house style
Fact and consistency checks before publication
Restructures a draft around its real argument
Decides what gets commissioned and what gets killed
Owns the editorial calendar and writer assignments
This page covers written-content editors across that range. If the role is really about footage or images, the video editor questions and the photo editor questions test the right craft instead.
For documentation, help centers, and product content, the technical editor set goes after accuracy against a specification rather than voice. Pick one page and run it properly rather than sampling three.
The Four Things to Assess in an Editor
Every useful editor interview tests four areas: accuracy and mechanics, editorial judgment, how they work with writers, and reliability against a deadline. A candidate can be outstanding in one and useless in another, which is exactly why a loose conversation about writing tells you so little.
Accuracy and mechanics
Catches errors consistently, not occasionally
Follows house style over personal preference
Checks headings, links, captions, and numbers
Editorial judgment
Finds the point a draft has not found
Cuts good material that does not serve the piece
Sends work back instead of polishing emptiness
Working with writers
Explains the reasoning behind heavy edits
Holds accuracy, concedes on taste
Handles late or defensive writers directly
Speed and reliability
A capacity number they will stand behind
Warns before a deadline, not after
Keeps status visible without being asked
Weight the four to the job rather than treating them equally. For product copy, documentation, or anything regulated, accuracy outranks the rest. For a blog or newsletter you want read, judgment carries the most weight. Decide the weighting before the first structured interview, not while you are comparing candidates afterward and rationalizing a favorite.
6 Free Editor Question Sets to Download
Download all six as a single Word document, or copy the sets you need. Each one follows the same structure: when to use it, the questions with a stated reason and a strong-answer note, what to listen for, and space for notes. Set 6 adds the test edit brief, the rubric, and the red-flag list.
Download All 6 Editor Question Sets
Core, accuracy, judgment, working with writers, workflow, plus a test edit brief and scorecard. All in one DOCX.
Set 1: Core Editor Questions
The base set for any editor hire: process, style guide, triage under deadline, fact checking, disagreement, and what happened the last time a mistake reached publication. Start here for every candidate.
Core Editor Interview Questions
CORE EDITOR INTERVIEW QUESTIONS
Candidate: __
Business: __
Interviewer: __
Date: _
HOW TO USE THIS SET
This is the starting set for any editor hire, whether the person will copyedit a
weekly newsletter or own the whole content calendar. Ask 6 to 8 of these, in the
same order, of every candidate. Each question lists why it is worth asking and
what a strong answer sounds like, so you can judge editing skill without being an
editor yourself. Score on the rubric in Set 6.
QUESTIONS
1. Tell me about the last thing you edited that you were proud of. What did you
change, and why did each change help?
Why ask: separates an editor who improves a piece from one who only removes
typos.
Strong answer: names specific changes and the reason behind each one, at the
level of structure and argument, not only wording.
2. Walk me through your process from receiving a draft to signing it off.
Why ask: a real editor has a repeatable sequence, and the sequence tells you
what they think editing is.
Strong answer: reads for structure first, then works at the line level, then
proofreads last, with a separate check for links, headings, and captions.
3. Which style guide do you work from, and what would you do if we do not have one?
Why ask: consistency is most of the value an editor adds at a small company.
Strong answer: names AP, Chicago, or a house guide, and offers to build a
short one-page style sheet for us in the first week.
4. How do you decide when a draft needs a rewrite rather than an edit?
Why ask: tests judgment about effort and about the writer relationship.
Strong answer: has a threshold, usually tied to whether the argument or
structure is sound, and talks to the writer before rewriting.
5. A draft lands two hours before it has to publish and it needs real work. What
do you do?
Why ask: this happens constantly at a small company and reveals triage skill.
Strong answer: fixes what changes the reader experience most, flags the rest,
and says clearly what was not done rather than pretending it is finished.
6. How do you fact check, and what do you do with a claim you cannot verify?
Why ask: an unverified claim published under your name is your problem.
Strong answer: checks numbers and names against a primary source, and cuts or
softens anything that cannot be sourced.
7. What do you do when you disagree with the writer about a change?
Why ask: an editor who cannot hold a position is not adding judgment.
Strong answer: explains the reason, listens, and knows which calls are theirs
to make and which belong to the writer or to you.
8. Tell me about a mistake that reached publication. What happened next?
Why ask: everyone has one, and the answer shows accountability and process.
Strong answer: owns it plainly, describes the correction, and names the check
they added afterward.
WHAT TO LISTEN FOR
•Reasons behind changes, not preferences stated as rules
•A stated process, followed in a stated order
•Comfort saying "this is not ready" and explaining why
•Interest in our reader and our business, not only in the prose
NOTES
__
__
Set 2: Copyediting and Proofreading Accuracy
For roles where an error costs money or trust: recurring mistakes, house style over personal taste, a named proofreading technique, throughput, and what they check outside the body text.
Copyediting and Proofreading Accuracy Questions
COPYEDITING AND PROOFREADING ACCURACY QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Use this set when accuracy is the main reason you are hiring: product copy,
customer-facing documentation, legal or medical review, or anything where an
error costs you money or trust. These questions test mechanics, consistency, and
whether the candidate can explain a rule rather than just feel it.
QUESTIONS
1. What are the three errors you catch most often, and why do writers keep
making them?
Why ask: a real copyeditor has patterns memorized and can teach them.
Strong answer: names concrete recurring errors and how they coach the writer
out of them.
2. Where do you stand on the serial comma, and what happens if our house style
disagrees with you?
Why ask: tests whether they follow a guide or their own taste.
Strong answer: has a preference, then follows house style without argument.
A candidate who cannot let go of a personal rule will fight you weekly.
3. How do you proofread your own work?
Why ask: everyone misses errors in text they have read five times.
Strong answer: has a real technique, such as a separate pass on a different
day, reading backward, or a fresh format, not "I read it again carefully."
4. How many words an hour do you copyedit, and how does that change for a
technical piece?
Why ask: gives you a planning number and tests self-knowledge.
Strong answer: gives a range, explains what slows it down, and does not claim
a speed that would make careful work impossible.
5. Take this sentence: it is grammatically correct and still hard to read. What
would you do with it, and why?
(Bring one real sentence from your own site.)
Why ask: the difference between correcting and improving.
Strong answer: explains the fix in terms of the reader, not the rule.
6. Beyond the words, what do you check on a page?
Why ask: most published errors live in the parts nobody reads.
Strong answer: headings, subheads, links, captions, alt text, image credits,
numbers in charts, and anything repeated across pages.
7. What tools do you use, and where do you overrule them?
Why ask: automated checkers are useful and confidently wrong.
Strong answer: uses a checker as a first pass and can give examples of
suggestions they ignore.
WHAT TO LISTEN FOR
•Rules explained, not recited
•A named proofreading technique, not more effort
•Willingness to follow house style over personal preference
•Attention to the parts of a page outside the body text
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
For an editor who decides what ships: finding the point in a shapeless draft, cutting good material, headlines, and when to send a piece back rather than polish it into competent emptiness.
Substantive Editing and Editorial Judgment Questions
SUBSTANTIVE EDITING AND EDITORIAL JUDGMENT QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Use this set when the editor will shape what gets published, not only clean it
up: a content editor, a managing editor, or the one person who owns your blog,
newsletter, or documentation. These questions test judgment, which is the part of
the job that is hardest to replace and hardest to interview for.
QUESTIONS
1. A draft arrives and it has not decided what it is about. How do you find the
piece inside it?
Why ask: this is the most common failure in business writing.
Strong answer: finds the one claim worth making, checks it against the reader,
and reorganizes around it rather than smoothing every paragraph.
2. Tell me about a time you cut something good because it did not serve the piece.
Why ask: editors who cannot cut produce long, unfocused work.
Strong answer: a specific example, with the reason, and no resentment about it.
3. How do you judge whether a headline is doing its job?
Why ask: the headline decides whether the rest is read at all.
Strong answer: tests it against the promise the piece keeps, not against how
clever it sounds.
4. A draft is well written and says nothing new. What do you do with it?
Why ask: competent, empty content is the most expensive kind.
Strong answer: sends it back with a specific ask, usually for evidence,
an example, or a real position, rather than editing it into polish.
5. How do you edit for a reader who is not you?
Why ask: your audience is probably not made of editors.
Strong answer: asks about the reader, the level of knowledge assumed, and what
the reader is supposed to do next.
6. When would you kill a piece rather than fix it?
Why ask: tests whether they can spend your money well.
Strong answer: has a threshold and raises it early, before hours are sunk.
7. How do you handle a subject you know nothing about?
Why ask: at a small company, they will.
Strong answer: reads the primary sources, finds the internal expert, and asks
the questions a reader would ask.
WHAT TO LISTEN FOR
•Decisions framed around the reader and the goal
•Comfort sending work back rather than absorbing it
•Curiosity about your business and your customer
•A clear line between what is wrong and what is merely different
NOTES
__
Set 4: Working With Writers
Delivering a heavy edit without losing the writer, handling a freelancer who files late twice, and knowing which edits to hold and which to concede. An editor who burns writers costs you writers.
Working With Writers Questions
WORKING WITH WRITERS QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
An editor who cannot work with writers costs you writers. Use this set whenever
the editor will handle staff writers, freelancers, or subject-matter experts
inside the company who write reluctantly. At a small business the editor is often
the only person in that relationship, with no manager above them to smooth it.
QUESTIONS
1. How do you deliver a heavy edit without losing the writer?
Why ask: the same edit lands very differently depending on delivery.
Strong answer: explains the reasoning, separates the must-fix from the
preference, and leads with what worked.
2. Tell me about a writer you made better. What did you do differently with them?
Why ask: developing writers is compounding value.
Strong answer: a specific person, a specific weakness, and a specific method,
not "I gave a lot of feedback."
3. A freelancer files late twice in a row. What do you do?
Why ask: you need someone who handles this without escalating it to you.
Strong answer: has a direct conversation, resets the deadline in writing, and
knows when to stop assigning work.
4. A writer rejects your edit and you still think you are right. What happens?
Why ask: tests both spine and proportion.
Strong answer: distinguishes accuracy and clarity, where the editor holds, from
voice and taste, where the writer often should.
5. How much do you explain your changes, and when do you just make them?
Why ask: over-explaining is slow, silent rewriting breeds resentment.
Strong answer: silent on mechanics, explained on anything that changes meaning.
6. Have you assigned and scheduled work for other writers? How did you decide who
got what?
Why ask: relevant if the role includes any commissioning.
Strong answer: matches the writer to the subject, considers load, and tracks
who is carrying what.
7. What do you want from an editor when you are the one being edited?
Why ask: the answer usually describes how they edit.
Strong answer: self-aware, and consistent with the answers above.
WHAT TO LISTEN FOR
•Directness paired with respect
•A rule for which fights are worth having
•Evidence of writers who got better under them
•Willingness to have the awkward conversation without escalating it to you
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Set 5: Workflow, Deadlines, and the Editorial Calendar
Building a calendar, making status visible without anyone asking, and a capacity number they will stand behind, plus scope and availability questions for freelance, part-time, and remote hires.
Workflow, Deadlines, and Calendar Questions
WORKFLOW, DEADLINES, AND EDITORIAL CALENDAR QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Publishing is a schedule, and an editor who cannot hold one is not much use no
matter how good the edits are. Use this set for any editor who owns a calendar,
and use the last two questions for freelance, part-time, or remote hires, where
scope and availability need to be settled before you make an offer.
QUESTIONS
1. How do you build and maintain an editorial calendar?
Why ask: tells you whether they plan or react.
Strong answer: works backward from publish dates, builds in a review buffer,
and keeps a small backlog so one late draft does not stop the week.
2. Where would you keep the queue, and how would I see status without asking you?
Why ask: visibility is the difference between delegating and worrying.
Strong answer: one shared place, updated as work moves, with statuses anyone
can read.
3. How many pieces a week can you edit at our length and depth?
(Show a real published example first.)
Why ask: gives you a capacity number you can plan against.
Strong answer: a range tied to the example, with the assumptions stated.
4. What is your turnaround commitment, and what do you do when you are going to
miss it?
Why ask: everyone misses one, and the warning matters more than the miss.
Strong answer: commits to a specific window and warns early, before the
deadline, not after.
5. Two people both tell you their piece is urgent. How do you decide?
Why ask: at a small company the editor arbitrates this alone.
Strong answer: has a tiebreak, usually the business date behind the piece, and
confirms the call in writing.
6. FREELANCE OR PART-TIME: How many clients do you carry, and how do you protect
our slot?
Why ask: an editor stretched across six clients will drop yours first.
Strong answer: honest client count, a named recurring window, and a plan for
coverage when they are away.
7. REMOTE: How do you handle handoffs, versions, and approvals when nobody is in
the same room?
Why ask: version confusion is the main way remote editing goes wrong.
Strong answer: one source of truth for the current version, tracked changes,
and a clear sign-off step with a named approver.
WHAT TO LISTEN FOR
•Planning backward from a publish date
•A capacity number they will stand behind
•Early warning as a habit, not an apology
•A single, visible source of truth for status and versions
NOTES
__
Set 6: Test Edit Brief and Editor Scorecard
A paid test edit brief every finalist receives identically, a 1-to-5 rubric across five areas, and a red-flag checklist, so the decision rests on evidence instead of on whichever conversation felt best.
Test Edit Brief and Editor Scorecard
PAID TEST EDIT BRIEF AND EDITOR SCORECARD
Candidate: __
Business: __
Interviewer: __
Date: _
PART 1: THE TEST EDIT BRIEF
Give every finalist the identical brief, on the same material, with the same
deadline, and pay for the time. A test edit tells you more than any answer,
because editing is the only part of the job you cannot describe your way through.
Material: one real draft of 800 to 1,200 words that you have NOT published, with
a known set of problems (a buried point, two factual claims to check, several
mechanical errors, a weak headline).
Ask for, in this order:
1. Tracked changes on the draft itself
2. A short note, 150 words or fewer, on the three biggest problems and what
they did about each
3. Three alternative headlines
4. Any claim they could not verify, listed
Time: cap it at 90 minutes and say so. Pay the candidate's stated hourly rate for
that time.
Rules that keep it fair:
[ ] Same draft, same brief, same deadline for every finalist
[ ] Nothing you intend to publish as-is from the test
[ ] Scored on the rubric below the same day, by the same person
[ ] The brief is job-related and applied consistently to all candidates
PART 2: SCORING RUBRIC
Score each area 1 to 5 immediately after the interview and the test edit, while
both are fresh. Anchor every score to something the candidate did or said. If two
people are involved, score independently first, then compare.
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
Accuracy and mechanics: catches errors, follows a style guide, checks the whole
page rather than only the body text
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Editorial judgment: finds the real point, cuts well, improves the headline,
knows what to send back
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Working with writers: explains changes, holds the important line, lets the small
ones go
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Speed and reliability: realistic capacity, met the test deadline, warns early
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Fit with our subject and voice: understands our reader, curious about the
business, adapts to house style
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
PART 3: RED FLAGS
[ ] Cannot say why a change was made, only that it reads better
[ ] Personal taste presented as a rule, and unwilling to follow house style
[ ] No process: edits structure, grammar, and headline all in one pass
[ ] Blames writers for every problem in every example
[ ] Will not commit to a turnaround window
[ ] Rewrote the test draft entirely, with no tracked changes and no note
[ ] Portfolio work they cannot describe in terms of what they changed
[ ] Missed the test edit deadline without warning you first
Every candidate gets Set 1. Add Set 2 when accuracy is the point of the hire, Set 3 when the editor decides what gets published, Set 4 whenever they will handle writers, and Set 5 when they own a calendar or the arrangement is freelance, part-time, or remote. Set 6 runs alongside all of them. Five or six questions asked properly, with follow-ups, beat twenty asked quickly.
Judging Editing Skill Without Being an Editor
Stop asking whether the writing sounds good and start asking why each change was made. That single shift is what makes an editor interview legible to a non-editor. Reasoning is gradeable; prose is not, at least not by someone who does not do this for a living.
Walk me through your process from receiving a draft to signing it off.
Strong answer: Describes an ordered sequence: read once for structure and argument, fix the shape, then work at the line level, then a separate proofreading pass, then a final check of headings, links, captions, and any numbers. A strong answer also says what they do when the draft fails the first read.
Weak answer: A weak answer starts with commas. Editing grammar before the structure is settled means polishing sentences that may not survive, and it is the clearest sign of a proofreader being sold to you as an editor.
A draft is well written and says nothing new. What do you do with it?
Strong answer: Sends it back with a specific ask: an example, a number, a real position, an interview with someone who knows. A strong answer treats emptiness as a content problem the writer has to solve, not a wording problem the editor can smooth over.
Weak answer: A weak answer edits it into polish and publishes it. Competent, empty content is the most expensive thing a small content operation produces, because it costs the same as good work and returns nothing.
How do you proofread your own work?
Strong answer: Names a real technique: a pass on a different day, reading the text in a different format or font, reading backward sentence by sentence, or reading aloud. The point is a mechanism that defeats familiarity, because attention alone does not.
Weak answer: A weak answer is a promise to be careful. Anyone who has read the same paragraph six times knows that care is exactly what stops working, which is why the technique matters more than the intent.
The pattern holds across the whole interview. Strong answers are ordered, specific, and tied to the reader. Weak answers are about effort, care, and how something feels. When you are unsure, ask the follow-up that never fails here: why did that help? An editor with judgment answers it immediately, and an editor without one changes the subject to how much they love language.
What to Ask About the Portfolio
A published article in an editor portfolio proves that a writer wrote well and that somebody did not ruin it. It tells you almost nothing about the candidate in front of you, which is why the portfolio conversation needs different questions from the ones you would ask a writer.
Ask for a before and after
A finished piece proves the writer. A tracked-changes pair proves the editor. Ask for one, redacted if needed, from work they are proud of.
Ask what they changed and why
Take one paragraph from their sample and ask for the reasoning behind three specific edits. Judgment shows up in the explanation, not the result.
Ask what they did not touch
Restraint is half of editing. An editor who can name a line they left alone, and say why, is thinking about the writer and the voice.
Ask for a before-and-after pair with tracked changes, redacted if the client requires it. Most working editors have one, and a candidate who cannot produce a single example of their own marks is worth a second look. Handle this in the screening call, before you spend a full hour on someone whose samples cannot be discussed.
The Paid Test Edit
One short paid test edit separates candidates faster than another round of questions, because editing is the part of the job nobody can talk their way through. Keep it small, keep it identical, and pay for the time.
Element
What to specify
Material
One unpublished draft, 800 to 1,200 words, with known problems
Time cap
About 90 minutes, stated up front, paid at their rate
Deliverable 1
Tracked changes on the draft itself
Deliverable 2
A note of 150 words or fewer on the three biggest problems
Deliverable 3
Three alternative headlines
Deliverable 4
A list of any claim they could not verify
Fairness
Same draft, same brief, same deadline, scored the same day
Two rules keep it clean. Do not send a live piece you intend to publish as-is, and do not ask for a volume of finished work that carries commercial value to you. The note matters as much as the edit: it shows you what the candidate believes the biggest problems are, which is the judgment you are buying. Score it the same day and feed the result into your interview feedback step.
Scoring and Red Flags
Score every candidate on the same rubric immediately after the interview, while the answers are still exact rather than remembered. Rate the same five areas for everyone, anchored to something the person actually said or did, so you compare evidence instead of impressions.
Scoring area
What a 5 looks like
Accuracy and mechanics
Catches errors consistently, follows house style, checks the whole page
Editorial judgment
Finds the real point, cuts well, knows what to send back
Working with writers
Explains changes, holds accuracy, concedes on taste
Speed and reliability
Realistic capacity, met the test deadline, warns early
Fit with subject and voice
Understands your reader, curious about the business
The red-flag list in Set 6 is deliberately behavioral. The heaviest signals are an editor who cannot explain a change, one who presents personal taste as a rule, and one who missed the test deadline without warning you first. Late is survivable and silent is not, because early warning is the habit that keeps a publishing schedule alive. Treat every flag as evidence on the scorecard, alongside the rest of the warning signs worth watching.
Editor Pay and Exempt Status
Editor pay has one of the widest spreads in the media occupations, because the title stretches from a part-time proofreader to a managing editor running a whole content operation. Use federal data as your floor and ceiling, then adjust for your market and the actual scope.
Median $77,920 a Year (BLS, May 2025)
Editors had a median annual wage of $77,920, about $37.46 an hour, with the lowest 10 percent under $41,250, the 25th percentile at $57,300, the 75th at $106,100, and the top 10 percent above $153,700, according to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025). Federal projections put employment at about 115,800 in 2024, growing slower than average through 2034 (U.S. Bureau of Labor Statistics).
Exempt status is a separate question, decided by duties and salary rather than by the job title. The creative professional exemption under the Fair Labor Standards Act requires a salary or fee basis of at least $684 a week plus a primary duty involving invention, imagination, originality, or talent. Work that mainly collects and records routine or already public information, without original interpretation, does not qualify.
In practice a copy editor doing mechanical correction is a much weaker fit for the exemption than a managing editor who shapes and commissions work. If the arrangement is freelance rather than employed, classification is its own analysis: review the employee versus contractor test against the real working relationship, not the label on the invoice. Check any stricter state test as well. This is general information, not legal advice.
Fair, Legal, and Structured Interviewing
Structure is both the fairer process and the better predictor, and editorial interviews drift away from it more easily than most. A portfolio conversation opens naturally onto where someone grew up, what they studied and when, and who is at home, which is precisely the terrain where questions you cannot ask appear without anyone intending them.
Same Questions, Same Test, Same Rubric
Asking every candidate the same prepared questions and scoring them against a consistent rubric predicts on-the-job performance more reliably than an unstructured conversation, and it keeps you within the EEOC rules against basing decisions on protected characteristics. The agency also expects tests and selection procedures to be job-related and applied consistently, which is why every finalist gets the identical test edit brief.
Keep every question tied to the work: the edit, the process, the deadline, the reader. Ask whether the candidate can perform the essential functions of the job and whether they are legally authorized to work. Then let the same rubric decide, which also reduces bias as a side effect of good process. This is general information, not legal advice.
Hiring an Editor Without an HR Department
At a publisher, an editor is interviewed by other editors and slots into a chain of review. At a small business the owner interviews alone, usually cannot grade an edit on sight, and the person hired becomes the entire chain. Here is how to make that single interview as rigorous as a full editorial team would.
You are hiring an editor and you are not an editor yourself
Most owners hiring their first editor cannot grade an edit on sight, which makes the interview feel like a taste test. The fix is to stop asking whether the writing sounds good and start asking why each change was made. An editor who can explain the reason behind a cut, a reorder, or a headline rewrite is doing the job; one who says it just reads better is guessing, and you will not be able to tell the guesses from the judgment six months in. Every question in these sets carries a note on what a strong answer sounds like, so you can score the reasoning rather than the prose.
The title covers four different jobs
Editor means copy editor at one company, managing editor at another, and video or photo editor somewhere else. Before you interview anyone, decide whether you are buying accuracy, judgment, or throughput, because the candidate pools barely overlap and a great copy editor is often a poor content owner. Write the split into the posting, then use the question sets that match. If you hire for accuracy and expect someone to own the calendar, you will conclude within a quarter that the hire failed, when the brief did.
One editor, no editorial department behind them
At a large publisher an editor sits inside a chain of review, with a copy desk under them and a chief above them. At a small business the editor is the entire chain, and their own last read is the only one the work gets before it faces customers. That raises the weight on process questions: a named proofreading technique, a visible queue, an early warning habit, and a real capacity number. Once you choose someone, FirstHR handles the hiring paperwork around them, with e-signature for the offer and an agreement covering copyright and confidentiality, document management for the signed files, and task workflows for system access. Applicant tracking is coming soon to FirstHR.
The practical version is short. Decide which editor you need, ask the same questions of everyone, insist on reasoning rather than adjectives, run one small paid test, and score it the same day. That process fits inside a normal week and beats a long unstructured search. The broader hiring process guide covers the steps around it, from the posting to the offer.
From Interview to Onboarding
The interview is step one. For an editor, the gap between the offer and the first published piece is where an otherwise good hire quietly goes wrong: nobody wrote down the house style, the ownership of edited drafts was never settled, and the calendar still lives in one person's head. Handle it with the offer letter and an agreement covering copyright and confidentiality, signed before the first file moves.
Offer, copyright, and confidentiality
Confirm pay and scope in writing, and settle who owns the edited work and any drafts before the first file changes hands.
Hand over the style sheet
Give the new editor your house style, or ask them to write a one-page version in week one and approve it. Consistency starts here.
Set up access and the queue
Publishing tools, the shared drive, and the content calendar, with the editor able to move work through status themselves.
Store the paperwork
Keep the signed offer, the agreement, the I-9 and W-4, and the interview scorecards organized and easy to find later.
Then run the standard sequence: new hire paperwork, system access, and an onboarding plan with a real publishing target for the first 30 days.
Two reference checks are worth the twenty minutes on a role where deadlines are the product. Ask specifically about turnaround and about how the candidate handled a writer who pushed back, since those are the two failures you will feel first.
FirstHR connects the offer, the agreement, e-signatures, the paperwork, and the onboarding checklist in one place, and keeps the signed documents and the interview scorecards on the employee profile, so a small business can run this without a coordinator. FirstHR is an onboarding and HR platform, not a content management system or an editorial workflow tool, so pair it with those. Applicant tracking is coming soon to FirstHR.
If the role also covers writing rather than only editing, run the content writer questions in the same session. The rest of the hiring templates handle the paperwork around the hire, from the posting through the first week. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Decide first which editor you are hiring: copy, line, managing, or specialist, because the candidate pools barely overlap.
Assess four areas: accuracy and mechanics, editorial judgment, working with writers, and reliability against a deadline.
Ask why each change was made rather than whether the writing sounds good, since reasoning is gradeable by a non-editor.
Request a before-and-after pair with tracked changes; a finished article proves the writer, not the editor.
Run one short paid test edit, identical for every finalist, capped at about 90 minutes and scored the same day.
Use BLS data as a baseline: editors reported a median of $77,920 a year in the May 2025 survey.
Frequently Asked Questions
What questions should I ask when interviewing an editor?
Ask questions that test four things: accuracy, editorial judgment, how they work with writers, and reliability against a deadline. The strongest openers are: walk me through your process from receiving a draft to signing it off; tell me about the last thing you edited and what you changed and why; which style guide do you work from and what would you do if we do not have one; a draft is well written and says nothing new, what do you do with it; and how do you proofread your own work. Add capacity and turnaround questions for any editor who will own a calendar, and scope questions for a freelance or part-time hire. This page gives you six ready-to-use sets, and every question carries a note on why it is worth asking and what a strong answer sounds like, so you can score the reasoning rather than the writing.
What is the difference between a copy editor, a line editor, and a managing editor?
They sit at different depths in the same process. A copy editor works on correctness and consistency: grammar, spelling, punctuation, house style, and factual details, usually late in the process. A line editor works one level up, on how sentences and paragraphs carry meaning, rewriting for clarity, rhythm, and flow without changing what the piece argues. A managing or content editor works above both, deciding what gets commissioned, shaping structure and argument, running the calendar, and managing the writers. At a small business one person often covers all three, but the skills genuinely differ and candidate pools barely overlap, so decide which one you are actually buying before you write the posting. Hiring for accuracy and then expecting someone to own the content calendar is the most common way this hire goes wrong.
How do I evaluate an editor if I am not an editor myself?
Stop judging whether the writing sounds good and start asking why each change was made. An editor who can explain a cut, a reorder, or a headline rewrite in terms of the reader is doing the job; one who says it just reads better is guessing. Three practical moves work well. Ask for a before-and-after pair with tracked changes rather than a finished sample, since a polished article proves the writer more than the editor. Take one paragraph from that sample and ask for the reasoning behind three specific edits. Then run a short paid test edit on a real draft of your own with a stated brief and deadline, identical for every finalist, and score it the same day on a rubric. The explanation and the test edit together tell you far more than any interview answer.
Should I give an editor candidate a test edit, and should I pay for it?
Yes to both. Editing is the one part of the job that cannot be described convincingly in an interview, and a short test on a real draft separates candidates faster than another round of questions. Keep it small and fair: one unpublished draft of 800 to 1,200 words, a cap of about 90 minutes stated up front, tracked changes plus a short note on the three biggest problems, three alternative headlines, and a list of anything they could not verify. Pay the candidate for the time at their stated rate. Give every finalist the identical draft, brief, and deadline, and score them the same day on the same rubric, because a selection procedure used in a hiring decision should be job-related and applied consistently. Do not use a live piece you intend to publish as-is.
What are the red flags in an editor interview?
The clearest red flag is an editor who cannot say why a change was made, only that it reads better. Others worth weighing: personal taste presented as a rule, and unwillingness to follow house style; no process at all, editing structure, grammar, and headline in a single pass; blaming writers for every problem in every example; refusing to commit to a turnaround window; rewriting a test draft entirely with no tracked changes and no explanation; portfolio pieces they cannot describe in terms of what they changed; and missing the test edit deadline without warning you first. Late without warning matters more than late, because early warning is the habit that keeps a publishing schedule alive. Note red flags on the scorecard as evidence rather than as an impression, and weigh them against the rest of the interview.
How much does it cost to hire an editor?
Editor pay varies widely with experience, subject matter, location, and whether the role is staff or freelance. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), editors had a median annual wage of about 77,920 dollars, roughly 37.46 dollars an hour, with the lowest 10 percent under 41,250 dollars and the highest 10 percent above 153,700 dollars. The spread is one of the widest in the media occupations, because the title covers everything from a part-time proofreader to a managing editor running a whole content operation. A staff editor costs that salary plus benefits and overhead; a freelance editor is billed per hour, per word, or per project and only when working, which suits businesses with uneven publishing volume. Benchmark to your local market and publish a good-faith range wherever pay transparency law requires one.
Are editors exempt from overtime?
It depends on the actual duties and the salary, and it is decided case by case rather than by job title. Under the Fair Labor Standards Act, the creative professional exemption requires payment on a salary or fee basis of at least 684 dollars a week and a primary duty involving invention, imagination, originality, or talent in a recognized creative field. The Department of Labor has been explicit that people who mainly collect, organize, and record routine or already public information, without contributing original interpretation or analysis, are not exempt creative professionals. A copy editor doing mechanical correction is a much weaker fit for the exemption than a managing editor shaping and commissioning work, and a part-time or freelance arrangement raises separate classification questions. Check the duties against the current federal rules and any stricter state test before you classify the role. This is general information, not legal advice.
What interview questions cannot I ask an editor candidate?
Avoid anything that probes a characteristic protected under federal law: age, race, color, religion, national origin, sex, pregnancy or family plans, disability, or genetic information. Creative interviews drift into this territory more easily than most, because a portfolio conversation naturally opens onto where someone grew up, what they studied and when, their family, and their health. Keep every question tied to the work: the edit, the process, the deadline, the reader. You may ask whether a candidate can perform the essential functions of the job and whether they are legally authorized to work. The simplest safeguard is structure: prepare the same job-related questions for every candidate, run the same test edit brief, and score on the same rubric, which is both fairer and a better predictor of performance. This is general information, not legal advice.