The New York Times logo

The New York Times interview questions

From 1 candidate account, updated Oct 12, 2026

Candidate accounts
1
Rounds on average
2
Rounds in every loop
2
Open roles at The New York Times
130

How the loop works

This guide draws on 1 first-hand interview account from Hacker News. Candidates describe about 2 rounds on average, most often technical interviews and system design.

These 1 writeup cover software engineering roles. All of them were posted under a forum handle, so we could not verify the authors’ identities.

See open roles at The New York Times

Interview experiences at The New York Times

Software Engineer

Received an offer

unknown. 2 rounds. Shared by sigfubar on hn, 2019-02-24

  1. 1Technical interviewTechnicalInterview was conducted entirely in the company's homegrown language.Covered: In-house programming language
  2. 2Architecture discussionSystem designArchitecture answers framed in industry standards were steered back to the in-house stack. Offer declined.Covered: System architecture

What The New York Times is hiring for now

130 open roles in our index. Advertised pay floors run $113k to $150k (median $128k, from 120 postings that state pay).

Most-posted roles

  • Senior Customer Service Agent, NYT Wirecutter (Temporary)2
  • Delivery Driver (RSH)1
  • HR Generalist1
  • Designer, Marketing1
  • Operations Manager, Styles and Well1
  • Associate Creative Director, Earned Marketing (Temporary)1

Top locations

  • New York City110
  • London5
  • Washington3
  • Seoul2
  • Los Angeles1

The New York Times interviews: FAQ

What is the interview process like at The New York Times?
This guide draws on 1 first-hand interview account from Hacker News. Candidates describe about 2 rounds on average, most often technical interviews and system design.
What topics does The New York Times test in interviews?
Commonly reported topics include In-house programming language, System architecture.

These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.