Phone screening, then a technical interview. I talked about my previous experiences on developer teams, then did a coding assessment, which I passed. The assessment was an easy-level LeetCode question. The two interviewers seemed satisfied with my performance. Two weeks passed and I heard nothing. I emailed them again and received an automated rejection email. There was no feedback, even though I asked for it. Feedback is quite critical for interviewing developers, especially after interviews that seem to go so well that I'm waiting for the invitation to advance to the next step. Like most companies out there, they switch off the courtesy once they decide I can't do anything for them. Not that I'm too concerned; I was hesitant about working there anyway, since they're not exactly a paragon of unbiased and fact-based reporting.
Mostly my experience with collaborative coding, working with a team, communicating with non-developers, and testing.
The following metrics were computed from 2 interview experiences for the The New York Times Web Developer role in New York, New York.
The New York Times's interview process for their Web Developer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for The New York Times's Web Developer interview process in New York, New York.