The views expressed here are solely my own. They do not represent the opinions, positions, or policies of any current or former employer, client, or affiliated organization.
Once, in a selection process for a content author role, I was asked a series of questions that still stick with me: How long does it take you to compare a paragraph? How long does it take you to copy and paste a piece of text? How long does it take you to review a page?
My brain short-circuited. Not because the questions were hard, because they had no real answer, and I found myself rambling, trying to construct something that sounded logical for a question that wasn't measuring anything logical to begin with.
It took me a while afterward to realize what actually happened in that room: it wasn't that I failed to answer well. It's that the questions revealed a completely wrong model of what makes a content author good at their job.
The Symptom: Content Work as an Assembly Line
Questions like "how long does copying and pasting take you" only make sense if you believe content authoring is a mechanical, timeable task, something closer to data entry than to judgment work. Under that model, a good author is a fast author, and speed on isolated micro-tasks is a reasonable proxy for overall competence.
It's an understandable mistake to make from the outside. Content work looks like typing and formatting from a distance. But that's exactly the trap: measuring the visible motion of the job instead of the invisible judgment that actually makes it work or fail.
Why That Criterion Is Wrong
What actually distinguishes a good content author has almost nothing to do with how fast they can execute a single mechanical step. It's autonomy, the capacity to act with good judgment while creating content, to research independently, to make dozens of small decisions correctly without needing someone else to make them first.
Speed on a single paragraph tells you nothing about whether someone understands why a style guide says what it says, whether they can infer the right call when a situation isn't explicitly covered, or whether they know the difference between a genuine ambiguity worth escalating and a trivial one they should just resolve themselves.
The Real Cost, Seen From Inside a Content Operation
I've seen this play out repeatedly in real content operations, and the pattern is always the same: authors hired on the wrong criteria turn into a constant stream of interruptions. If a sentence is missing a period, they ask. If something deviates slightly from the expected format, they ask. The work stops, over and over, for decisions that a competent author should be able to make on their own in seconds.
This isn't a minor inconvenience, it's the single biggest hidden cost in a content operation. It doesn't show up in any dashboard that measures "time per paragraph," but it shows up everywhere else: in stalled review queues, in editors who become de facto babysitters instead of quality gatekeepers, in throughput that never scales no matter how many authors you add, because each one still needs someone else's judgment to function.
What You Should Actually Be Spotting Instead
Here's the irony I have to be honest about: if I just swapped those timing questions for a different set of interview questions, I'd be falling into the same trap I criticized in the previous article, testing a skill through an artificial, isolated prompt instead of looking for evidence of it in how someone actually operates.
So instead of a better question, what you actually need is a better thing to spot:
Autonomy under ambiguity. Not "can they follow the format," but whether, faced with something underspecified, they make a reasonable call on their own instead of freezing and escalating. This shows up far more reliably in a work sample or a trial task than in any interview answer.
Understanding the "why," not just the "what." Someone who can explain the reasoning behind a convention (not just recite it) is far more likely to apply it correctly to situations the guide never explicitly covered.
Judgment about what's worth escalating. The real skill isn't "never asks questions." It's knowing which ambiguities are trivial enough to resolve alone and which ones genuinely need another set of eyes. That's a pattern you see across someone's actual work history, not something a single interview answer can reliably surface.
Evidence over self-report. The most honest way to spot all of the above is to look at real samples of past work, or a short paid trial task with real ambiguity built in, and watch what they do with the gaps, rather than asking them to describe what they would do.
None of this produces a tidy number you can put in a spreadsheet, but that's exactly the trade-off worth making.
The Pattern Behind the Pattern
This connects to something I keep running into across every hiring process I've analyzed: companies default to measuring what's easy to measure, not what actually predicts performance. A stopwatch on a paragraph is easy. Judgment, autonomy, and the ability to infer intent from incomplete information are hard to quantify, so they get skipped, even though they're the entire job.
If there's one thing worth taking from this, it's a question worth asking before designing any evaluation, for any role: are we testing the visible motion of the job, or the invisible judgment that actually makes someone good at it?
Juan Carlos Vásquez has spent ten years inside enterprise content operations, repairing content supply chains before scaling them. Fix to Flow is the discipline that work produced. The views here are his own.