Editor Interview Questions
For desktop publishers who use software to lay out text and graphics. Interviews focus on preparing pages for publication and correcting layout problems in proofs.
30 questions, ranked by what the job needs most
Also for Editor: Camera Operators, Television, Video, and Motion Picture · Technical Writers · Editors · all 9 sets →
Print the top 10:Scoring sheetPractice sheet
Question 1: Walk me through a recent project you laid out and took all the way to print-ready files, including the software you used at each step.
Example answerThe interviewer wants to see that you can run a job from brief to finished files without gaps. Build your answer in order: the brief and specs, setting up the document, placing text and images, proof rounds, and exporting and checking the final files. Name the software you used at each stage, and keep to tools you really know. Sample answer: "Last spring I laid out a 12-page event program. I started by confirming the trim size, bleed and deadline with the printer, then set up a template with master pages and paragraph styles in our layout software. I placed the copy from the editor, edited the photos in an image editor, and sent a PDF proof to the editor. After two rounds of corrections, I ran a preflight check for fonts, image resolution and color mode, exported a print PDF to the printer's settings, and reviewed it page by page before sending it." Pitfalls to avoid: listing software without showing how you used it, skipping how proofs and corrections were handled, and leaving out the final file check.
Interviewer tipA strong answer moves clearly from brief to layout to proofs to exported files and shows comfort with the software; skipping proofing or file prep is a red flag.
Candidate tipChoose a project you know well. Cover the brief, how you built the layout, how proofs were handled, and how you exported and checked the final files.
Question 2: Give an example of how you corrected a publication proof before the pages were released.
Interviewer tipA strong example follows a marked correction through to the revised proof. Clearing a page without checking that the correction made it into the new proof is a red flag.
Candidate tipPick a proof, a preview checked before release, that needed a correction. Describe what you fixed in the layout file and what you checked on the revised proof.
Question 3: Walk me through how you used type and layout to make a web page easy to scan.
Interviewer tipListen for a type or layout choice that helped readers find the main point. Making every heading equally prominent can bury the main point.
Candidate tipPick a web page you laid out for work, a course project, or an internship. Explain one choice about headings, text size, or placement and say what readers could find more easily.
Question 4: How do you choose type size and style, column width, and spacing for a printed document?
Interviewer tipListen for how they balance readable type, line length, and spacing at the final print size. Shrinking the text until it fits without checking readability is a red flag.
Candidate tipStart with the finished page size and the amount of copy. Explain how those affect your type and column choices, then describe what you check on a printout at actual size.
Question 5: Share an example of how you revised a page layout after reading an editor's comments on a screen proof.
Interviewer tipListen for the editor's comment, the candidate's layout change and the result of checking the revised screen proof. Making a change without understanding the comment is a red flag.
Candidate tipChoose one screen proof with an editor's layout comment. Explain how you interpreted it, changed the page and checked the revision. End with the result and what you learned.
Question 6: Tell me about a time you caught a small production detail, such as a missing font or a low-resolution image, before a file went to the printer.
Example answerThe interviewer wants to see that you catch the small technical problems that can ruin a print job. Use Situation, Task, Action, Result, and name the detail exactly. Sample answer: "I was finishing a trifold brochure for a local nonprofit. When I ran my preflight check before export, it flagged a photo on the back panel that was only good enough for screen use. On screen it looked fine, but printed it would have come out blurry. I asked the client for the original file, placed it, and checked that it was at print resolution and in the right color mode. I also found that one heading used a font that wasn't embedded, so I fixed that before exporting. The brochure printed sharp and on time, and I now run the preflight check on every file before it leaves my desk." Pitfalls to avoid: a vague answer about being detail-oriented, a catch that came from luck rather than a routine, and leaving out what the mistake would have cost.
Interviewer tipListen for a habit of checking, such as a preflight check or a final review on screen and on paper, and what the mistake would have cost; luck instead of a routine is a red flag.
Candidate tipName the detail, how you spotted it, and what would have happened if it had gone through. Mention the check you now use on every job.
Question 7: Describe a time you prepared a sample page layout for feedback before laying out the rest of a publication.
Interviewer tipA strong example shows how the sample let the editor judge a choice before the full layout. Treating a short placeholder story as proof that the full copy will fit is a red flag.
Candidate tipSay what you wanted the editor to judge, such as whether a story and its photo would fit together. Describe what you put on the sample page to test that choice and what the feedback told you.
Question 8: Tell me about a time you imported text and artwork from separate files into a publication layout.
Interviewer tipListen for how they brought the files into the layout and checked that the complete copy and correct artwork came through. Assuming an import worked because the first page looks right misses that check.
Candidate tipA course project or internship example works. Name the layout software and explain how you brought in the copy and artwork and checked that the full text and the right images came through.
Question 9: Share an example of using software to convert a publication file to the format required for delivery.
Interviewer tipA good example names the required file format, how they made the conversion, and a check on the converted file. A file that opens can still display the wrong fonts or drop images.
Candidate tipName the starting format, the format the printer or publisher needed, and the software you used. Describe one thing you checked in the converted file, such as whether the fonts still displayed correctly.
Question 10: How do you plan the work for a new publication layout before you start building pages?
Interviewer tipListen for a sequence that accounts for the page requirements and which copy and artwork are ready. Planning to lock the page breaks before checking whether the copy is final can create avoidable rework.
Candidate tipStart with what you check in the assignment, such as the required page size and page count. Explain how you decide which layout work can start with the files you have and which parts need to wait.
Question 11: What factors do you consider when selecting number of colors and determining color separations?
Question 12: When you have several publications due the same week, how do you plan and prioritize the layout, proofing and file delivery?
Example answerThe interviewer wants to know how you keep several jobs on schedule when deadlines overlap. Describe your system: how you list the jobs, work back from each print or publish date, leave time for proofs and corrections, and check priorities with editors or clients. A recent example makes it believable. Sample answer: "I start the week by listing every job with its delivery date and the date the printer needs files. I work backward to set when each proof must go out, and I leave a buffer for a second round of corrections. The job with the earliest hard deadline gets layout time first, and I fit smaller edits around it. If two jobs clash, I ask the editor which one matters more rather than guessing. When a late change puts a date at risk, I tell the person right away and offer options, like moving a page to the next issue." Pitfalls to avoid: saying you just work harder, ignoring time for proof rounds, and not mentioning how you handle late changes.
Interviewer tipA strong answer covers printer deadlines, time for proof rounds and checking priorities with editors; an answer with no plan for late changes is a red flag.
Candidate tipWalk through a real busy week. Explain how you work back from print dates, leave time for corrections, and tell people early when a date is at risk.
Question 13: Describe your experience using pixel editing, bitmap editing, airbrushing, masking, and/or image retouching.
Question 14: Describe your experience retouching and making color corrections.
Question 15: Provide an experience in which you effectively collaborated with graphic artists, editors, and/or writers to produce a master copy.
Question 16: How do you confirm you have permission to use supplied images and fonts before sending a publication file out?
Interviewer tipExpect checks of image permissions and font licenses against the publication's intended use, plus resolution of missing rights before release. Assuming a supplied file is free to use is a red flag.
Candidate tipDescribe where you check image permissions and font license terms for the publication. Explain how you handle unclear rights before sending the file out.
Question 17: Tell me about a time you found a creative layout solution when the content didn't fit the space or the usual template didn't work.
Example answerThe interviewer wants to see how you solve layout problems with good design judgment, not just by shrinking the type. Use Situation, Task, Action, Result: the constraint, the options you considered, what you chose and why, and how it turned out. Sample answer: "I was laying out a flyer for a community event, and the organizers sent nearly twice as much copy as the usual template could hold. Cutting the type size would have made it hard to read. Instead I suggested moving the schedule into a simple table and putting the sponsor list on the back in smaller text. I mocked up both versions so they could compare. They chose the new layout, the front stayed clean and easy to scan, and they used the same format for their next event." Pitfalls to avoid: describing creativity that ignored the brief or brand rules, skipping how you checked the idea with the client, and giving no result.
Interviewer tipA strong answer names the constraint, such as too much copy or an odd page size, and explains the design choice that solved it; a fix that ignored the brand or the brief is a red flag.
Candidate tipDescribe the constraint, the options you tried, and why the layout you chose worked for readers. Say what the client or editor thought of it.
Question 18: Tell me about a time you had to tell a client or editor that their files or images weren't good enough to print as planned.
Example answerThe interviewer wants to see that you raise production problems early and explain them clearly to people who aren't designers. Use Situation, Task, Action, Result. Explain the problem in plain words and the options you offered. Sample answer: "A client sent photos for a catalog that had been saved from their website. They looked fine on screen, but they were too small to print sharply at the planned size. I printed a test page so they could see the blur for themselves, and I explained that web images usually don't have enough detail for print. I offered three options: send the original camera files, run the photos smaller on the page, or reshoot the key products. They found the originals for most items and we ran the rest smaller. The catalog printed cleanly, and they now send original files first." Pitfalls to avoid: using jargon the person can't follow, fixing the problem quietly without telling them, and bringing a problem with no options.
Interviewer tipLook for an answer that explains the problem in plain terms, such as low image resolution, and offers options; vague warnings or fixing it silently without telling anyone are red flags.
Candidate tipSay what the problem was, how you explained it without jargon, and what options you offered. Share how they responded and what was printed in the end.
Question 19: Tell me about a time you learned a new publishing tool or software feature and used it to improve your work.
Example answerThe interviewer wants to know that you keep your skills current and use new tools to get real results. Use Situation, Task, Action, Result: what you needed, how you learned the tool, how you tested it, and what improved. Sample answer: "Our team produced a monthly newsletter, and updating the same layout by hand each issue took me most of a day. I learned to use data merge and saved paragraph and object styles in our layout software through the built-in tutorials and a few test files. Once I was confident, I rebuilt the template so the recurring sections pulled from a spreadsheet and the styles applied in one step. The next issue took far less time to lay out, and the formatting was more consistent from page to page. I showed a coworker how to use it too." Pitfalls to avoid: naming a tool without explaining what changed, claiming results you can't explain, and suggesting you used it on a live job before testing it.
Interviewer tipListen for how they learned it, such as tutorials or test files, and a concrete gain in speed or quality; learning a tool only because it was new, with no result, is a weak answer.
Candidate tipName the tool or feature, how you learned it, and how you tested it before using it on a live job. Explain what got faster, easier or more accurate.
Question 20: Describe how you handled a client or editor who kept changing a layout late in the job.
Example answerThe interviewer wants to learn how you keep a working relationship productive when late layout changes make a job difficult.
Build your answer with Situation, Task, Action, Result. Name the publication, the late changes and your responsibility. Explain your own conversations and decisions, including how you clarified the changes and their effect on the schedule. Close with the result for the job and relationship, plus what you learned.
For example: "A client kept sending separate layout changes as I was finishing a newsletter. I was losing track of which requests were final, so I called to go through them together. I sent back a written list and explained which changes would affect the print deadline. We agreed on the final revisions, and I checked the updated proof with the client. The newsletter went out on the agreed schedule, and our later jobs used a single change list. I learned to clarify requests before frustration builds."
Avoid blaming the client or editor, describing a hypothetical instead of a real case or claiming you agreed to changes while hiding their effect on the deadline.
Interviewer tipListen for calm discussion of the layout changes, clear expectations and a workable relationship afterward. Blaming the client or editor without explaining their own actions is a red flag.
Candidate tipUse a real layout job. Focus on how you clarified the client's or editor's changes and managed the conversation, then give the outcome and a lesson you took into later jobs.
Question 21: Provide your experience entering digitized data into electronic prepress system computer memory.
Question 22: Share your experience creating special effects and adding elements, e.g. sound and animation, to electronic publications.
Question 23: Provide an experience that demonstrates your ability to manage time effectively. What were the challenges and results?
Example answerThe interviewer wants to know how you plan your time and handle competing demands, and whether you meet deadlines.
Use Situation, Task, Action, Result. Name the specific challenges, such as overlapping deadlines or interruptions. Describe the steps you took to plan and protect your time, and what you did when something came up. End with the results the question asks for.
Sample answer: "During one busy week, I had a report due Thursday, two new team members to train, and my usual daily tasks. I mapped out the week on Monday, scheduled training for the mornings when things were quieter, and blocked two afternoons for the report. When an urgent request came in Wednesday, I asked a colleague to cover one training session. The report went in a day early, and both new team members finished their training on schedule."
Pitfalls: Don't just list time-management tools. Avoid a story where you met the deadline only by working through the night. Don't skip the challenges.
Question 24: Provide an example of a time when you were able to demonstrate excellent listening skills. What was the situation and outcome?
Example answerThe interviewer wants evidence that you listen to understand, not just to reply, and that it makes a difference to your work.
Use Situation, Task, Action, Result. Show what careful listening looked like: letting the person finish, asking follow-up questions, and repeating back what you heard. The outcome should show that listening caught something you would otherwise have missed.
Sample answer: "A manager from another department asked for a monthly report and said they wanted it faster. Instead of starting right away, I asked what they used the report for. They mentioned twice that they only looked at two of the columns. I confirmed that with them, built a one-page summary of just those figures, and it took a third of the time to produce. They used the summary format from then on."
Pitfalls: Don't just describe yourself as a good listener without an example. Avoid an answer where you talk mostly about what you said. Don't leave out the outcome the question asks for.
Question 25: How do you balance cooperation with others and independent thinking? Share an example.
Example answerThe interviewer wants to see that you can work well with a team while still bringing your own judgment, and that you know when to speak up and when to go along.
Start with a short answer about how you balance the two, then give one example. A good example shows you sharing your own view, listening to others, and then supporting the team's decision even if it wasn't yours.
Sample answer: "I try to form my own view first, share it clearly, and then commit to whatever the group decides. On one project, the team wanted to launch a new form right away. I thought we should test it with a few users first and explained why. We agreed on a one-week trial. Testing found a confusing field, we fixed it, and the full launch went smoothly."
Pitfalls: Don't present yourself as someone who always goes along or always insists on your own way. Avoid a story where you ignored the team's decision. Don't skip the example.
Interviewer tipTry to determine if the candidate has a cooperative attitude or is otherwise good-natured.
Candidate tipThe employer wants to know that you have a cooperative attitude or are otherwise good-natured.
Question 26: Share an example of when you went above and beyond the "call of duty".
Interviewer tipLook for answers that show the candidate is dependable.
Candidate tipThe employer wants to know that you are dependable.
Question 27: Tell me about the last time you monitored or reviewed information and detected a problem. How did you respond?
Example answerThe interviewer wants to see that you keep an eye on your work area or data, notice problems early, and act on them.
Use Situation, Task, Action, Result. Describe what you were checking and how often, what signaled the problem, and the steps you took right away. Include who you told and what you did to stop it happening again.
Sample answer: "I review our inventory report every Monday. One week I saw that one item's stock had dropped far faster than usual. I checked the order records and found a duplicate order that had shipped twice to the same customer. I told my supervisor, contacted the customer to arrange a return, and asked our systems team to block duplicate orders. The return came back the following week, and we haven't seen the problem since."
Pitfalls: Don't pick a problem someone else found and you only fixed. Avoid stopping at the fix without saying how you prevented a repeat. Don't stay vague; name what you were monitoring.
Question 28: Name a time when your creativity or alternative thinking solved a problem in your workplace.
Example answerThe interviewer wants to see that you can find a new approach when the usual one isn't working.
Use Situation, Task, Action, Result. Describe the problem and why the normal fix didn't work. Then explain your idea, where it came from, and how you tested it. End with the result and whether the idea was kept.
Sample answer: "Our training sessions for new staff had poor attendance because people couldn't step away from their work for an hour. Instead of rescheduling again, I suggested splitting the material into ten-minute videos people could watch between tasks. I recorded the first three as a test. New staff finished them within their first week, and my manager asked me to turn the rest of the training into the same format."
Pitfalls: Don't describe an idea that was never tried. Avoid claiming sole credit if others helped build it. Don't confuse creativity with ignoring rules or safety steps.
Question 29: Provide a time when you worked in a rapidly evolving workplace. How did you deal with the change?
Example answerThe interviewer wants to know how you respond when processes, tools, or priorities change quickly, and whether you help or slow things down.
Use Situation, Task, Action, Result. Describe what was changing and how it affected your work. Then explain what you did to adjust: learning the new way, asking questions, or helping others through it. End with how things turned out and what you took from it.
Sample answer: "In one year my team changed its scheduling software, its reporting process, and its manager. When the new software came in, I signed up for the first training session, wrote a one-page guide for the steps we used most, and shared it with the team. Questions to our manager dropped within a couple of weeks, and I was asked to help test the next update."
Pitfalls: Don't complain about the changes or past leadership. Avoid saying you just went along with it; show what you actively did. Don't pick a change so small it doesn't show adaptability.
Interviewer tipMake sure the candidate is flexible.
Candidate tipShow that you can adapt.
Question 30: Share an experience in which you successfully coordinated with others. How about a coordination effort that was not as successful?
Example answerThe interviewer wants to see how you work with others to line up schedules, tasks, and handoffs, and whether you learn from times it didn't work.
The question asks for two stories, so keep each one short. For the success, explain who was involved, how you kept everyone in step, and the result. For the less successful one, say what went wrong, your part in it, and what you now do differently.
Sample answer: "For an office move, I set up a shared timeline with the facilities, technology, and department leads, and held a 15-minute check-in each week. Everyone was set up and working by Monday morning. Earlier, on a smaller project, I assumed a vendor knew our deadline and didn't confirm it. Their delivery came two days late. Since then I confirm key dates in writing with everyone involved."
Pitfalls: Don't spend all your time on the success. Avoid blaming others for the one that went wrong. Don't skip what you learned.