Why pre-screen digital publishing specialists before the interview
This role sits between the writing and everything that can go wrong with it: markup that breaks on one device, an image nobody licensed, a heading structure that makes the piece unusable with a screen reader, and a stakeholder who wants a change an hour before publication. Specialists worth hiring have shipped through all four. A short screen asks what broke on publication day.
What actually matters when screening Digital Publishing Specialist candidates
- 01
Execution and reliability
Check throughput on real titles: InDesign to EPUB3 conversions, ONIX feeds to Ingram or KDP, epubcheck validation passes, and how many titles they shipped per release window.
- 02
Improving the process
Probe changes they made to the production pipeline: templated InDesign styles, automated XML or Pandoc conversion scripts, metadata QA checklists, or reduced rework on retailer rejections.
- 03
Judgement and autonomy
Assess how they handle ambiguity alone: broken reflow on Kindle versus Apple Books, missing alt text, rights or territory restrictions, last-minute price or embargo changes.
- 04
Communication
Look for how they brief editorial, design, and sales: change logs on corrected files, retailer takedown requests, explaining WCAG or fixed-layout limits to non-technical colleagues.
Pre-screening questions to ask Digital Publishing Specialist candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Publications shipped
3 questions01Can you give examples of digital publishing projects you have managed?
Listen forPublished work with volume and cadence described, and their own responsibility across the process.
Projects described without publication detail, or involvement limited to one stage.
02Can you describe your experience with content management systems?
Listen forSystems used daily with templates and workflows configured, not only content entered.
Experience limited to typing into an editor, or template problems always escalated.
03Describe your experience with multimedia content such as video or audio.
Listen forFormats, hosting and captions handled properly, with file sizes considered for the reader.
Media embedded without captions, or large files published without any optimisation.
Technical craft real
3 questions04Describe your experience with markup and web technologies.
Listen forEnough to read and correct markup, with semantic structure understood rather than visual styling.
Markup avoided entirely, or formatting achieved by inline styling and repeated line breaks.
05Can you explain your process for ensuring cross-device compatibility?
Listen forTesting on real devices including small screens, with layouts checked before publication.
Testing done only in a desktop preview, or mobile problems reported by readers.
06How do you ensure content is optimised for search?
Listen forStructure, metadata and internal linking handled without distorting the content for search engines.
Keyword stuffing described as optimisation, or search treated as unrelated to publishing well.
Accessible and cleared
3 questions07How do you ensure published content is accessible to all readers?
Listen forHeading structure, alternative text and link wording handled as part of the publishing process.
Accessibility limited to contrast, or alternative text generated automatically without review.
08How do you ensure compliance with copyright and publishing standards?
Listen forImage and quotation rights verified before publication, with licences recorded for each asset.
Images taken from search results, or licence terms not recorded anywhere.
09What steps do you take to improve readability and reader experience?
Listen forStructure, length and typography considered for how people actually read on screen.
Readability treated as a score, or long unbroken text published without structure.
Handles revisions
3 questions10Describe a time when you had to troubleshoot a technical publishing problem.
Listen forA real failure diagnosed under time pressure, with what they changed to prevent a repeat.
Problems always escalated to developers, or no publication issue they resolved themselves.
11How do you manage feedback and revisions from stakeholders?
Listen forRevisions consolidated with a version everyone works from, and a cut-off before publication.
Changes accepted right up to publishing, or conflicting edits applied without resolution.
12How do you use analytics to guide content decisions?
Listen forReading behaviour reviewed with a change made because of it, rather than reporting for its own sake.
Analytics reported monthly with no decisions attached, or page views treated as the only measure.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Execution and reliability
35%5Names title counts, deadlines held against print pub dates, and clean epubcheck plus ONIX ingestion on first submission.
Improving the process
25%5Describes a specific automation or template overhaul with before and after figures on turnaround time or rejected files.
Judgement and autonomy
25%5Decides confidently on accessibility fixes and retailer quirks, escalating rights and embargo questions with a recommendation attached.
Communication
15%5Writes plain, traceable updates; translates EPUB and metadata constraints into choices editors and sales teams can act on.
Markup breaks, images are unlicensed and someone wants a change an hour before. A one-way video screen asks about that.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Ten to fifteen minutes across eight to ten questions, answered async. Enough to establish what they shipped, test their technical craft, and check accessibility and rights handling.
How technical should this role be?
Enough to read and fix markup rather than only using an editor. Someone without that will be blocked by a broken layout every time the content management system behaves unexpectedly.
Evaluating answers
What is the strongest signal when screening this role?
What broke on publication day and how they fixed it. Specialists who ship have several stories. Anyone whose publications went out cleanly every time has not published much.
How do I judge their accessibility practice?
Ask about heading structure and alternative text. Real answers treat both as part of publishing rather than an addition. Anyone who mentions only contrast has learned it from a checker.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
