The scenario: a call you have to make live
A tip comes in twenty minutes before a competing outlet is expected to post the same story, with one source willing to talk but not on the record, and no time to reach a second one before the window closes.
A technical interview built for this role hands over that exact pressure and asks the candidate to reason through it out loud in real time: what gets published now, what gets held, what language covers the uncertainty honestly without either burying the story or overstating what's actually confirmed.
There's no draft to write, just the reasoning a reporter would walk an editor through on a five-minute phone call before deadline.
What gets tested here, and what stays out of scope
Expect scenario-based questions built around verification under time pressure, weighing an anonymous source's credibility, and deciding what's safe to run versus what needs to wait, each one asking for the reasoning process rather than a single memorized rule. The AI interviewer follows up the way a real editor would, pressing on a thin justification or asking what would change the call.
What this session does not cover is any actual writing or editing of a passage. For a posting that tests a written rewrite or an edit exercise directly, that lives in technical challenges, a separate feature supporting a written format alongside coding, debugging, and SQL for outlets that also need those, and it's worth treating as this session's companion rather than a substitute for it.
Scoring
How the five dimensions apply here
Technical is the dimension doing the most work in this session, and its written reasoning explains whether the verification and sourcing logic held together, not whether it matched one predetermined call. Communication matters almost as much, since a reporter who reasons well internally but can't explain the call clearly to an editor under deadline loses the part of the job that actually gets tested in real newsrooms.
Calibration floors and caps apply the same way here as elsewhere, so a fast, confident-sounding answer that skips the actual verification steps won't outscore a slower one that gets the sourcing reasoning right.
Frequently asked questions
Will I be asked to write or edit anything in this session?
No. The technical interview type is a spoken conversation about news judgment and sourcing reasoning. Writing or editing an actual passage happens in the separate technical challenges feature's written format.
How is this different from a job-description session for the same role?
The job-description type reads a specific posting and questions you on its named beat and coverage area. The technical type tests general news-judgment and sourcing reasoning without needing a posting to draw from.
What if the outlet I'm targeting also runs a written edit test?
That's a real, separate part of many journalism hiring processes. Pair this session with technical challenges, which supports a written format for exactly that kind of exercise.
Does speaking fast and confidently score well here even with a shaky verification call?
No. Calibration floors and caps apply to this session the same as every other Intervieux interview, so a fluent answer that skips real verification reasoning won't outscore a slower, more careful one.
Related pages
Practice the news-judgment call out loud
Run a technical AI interview to rehearse sourcing and verification reasoning under deadline, then pair it with technical challenges if the outlet also tests a written rewrite.