I received a curt email from the NYT recruiter asking for availability for a phone interview. The technical interviewer was late to the call and preceded every question with some variation of "Sorry, I'm in a rush," and often interjected my answers with "that's enough". All questions were either about documentation semantics for Backbone/Angular (really?) or relatively easy but nuanced questions about web development in general (CORS, scope in Javascript) that require more than a sentence to answer. However, like I mentioned earlier—I kept getting cut off when going into detail—so I assume that the interviewer didn't understand many of the questions and was reading from a list that a more experienced JS developer wrote.
Q: What happens when typing a URL into a web browser?
The following metrics were computed from 1 interview experience for the The New York Times Javascript Engineer role in United States.
The New York Times's interview process for their Javascript Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for The New York Times's Javascript Engineer interview process in United States.