Skip to main content

The New York Times

Associate Newsroom Software Engineer, Interactive News

New York, NYFrom $110kentryAdded today

About this role

Join The New York Times' Interactive News Technology team as an Associate Software Engineer to build tools and platforms that empower journalists and engage millions of readers. You'll develop features for breaking news coverage, interactive storytelling, newsroom AI products, and data-driven journalism using modern web technologies.

What you'll do

  • Prototype and develop new software features to support journalists' reporting and storytelling capabilities
  • Contribute to full software development lifecycle from technical design through production operation
  • Participate in project research and technical architecture decisions as part of cross-functional teams
  • Build reliable, scalable, and secure systems for newsroom and reader-facing applications
  • Collaborate with newsroom desks and specialized teams (AI, Data Journalism, Graphics) on integrated workflows
  • Support breaking news and major events with rapid deployment and real-time systems

What they're looking for

  • JavaScript and TypeScript
  • Node.js backend development
  • React frontend framework
  • PostgreSQL databases
  • Google Cloud Platform services
  • Serverless architecture
  • Collaborative software design
  • Journalistic and editorial thinking
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

The New York Times

The New York Times builds digital platforms and products that deliver journalism through web, mobile, and multimedia experiences, supported by modern backend systems and AI-enhanced tools. The company is hiring software engineers, QA engineers, and full-stack developers to work across content management, audio/video features, AI-driven reader experiences, and internal developer tooling.

View all jobs at The New York Times

Likely interview questions

  • Can you describe a time you built a feature under tight deadlines? How did you prioritize and ensure quality?
  • How would you approach learning about journalism workflows to build better tools for reporters?