Software Engineer Interview Experience - United States
Process
2 recruiter calls followed by 1 behavioral and 1 coding challenge.
Was told the coding challenge was language agnostic at the start of the coding challenge.
Solved the problem and 2 follow-ups in 2 minutes. The 3rd follow-up required you to rewrite in JavaScript. Solved in 3 more minutes but was rejected anyways.
Questions
Remove Duplicates from an array
Was this helpful?
Interview Statistics
The following metrics were computed from 48 interview experiences for the The New York Times Software Engineer role in United States.
Success Rate
The New York Times's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for The New York Times's Software Engineer interview process in United States.
The New York Times Work Experiences
- 4.0Good culture, weak paySoftware Engineer • Current EmployeeMay 16, 2025Pros: Good culture, interesting problems to solve as a team and as a company.Cons: Weak pay, still struggling to move fast like a tech company, but this could be a good thing.
- 2.0Experience depends on the teamSoftware Engineer • Former EmployeeNew York Mills, New York, United StatesJanuary 11, 2025Pros: Great place to learn new tech.Cons: Landscape does not support growth.
- 4.0NYT Base SalarySoftware Engineer • Current EmployeeNew York, New York, United StatesDecember 12, 2024Pros: The culture and diversity. A good reputation.Cons: Nothing to share. Need to work for a longer time.
