The most unprofessional interview I’ve ever been to. I applied through a referral and got an email from the recruiter about a week later to discuss the role. She sounded like she was just reading back the job description to me. She mentioned she’d pass my application on to the manager and that I should hear back in a day or two. I didn’t hear back, so I followed up about a week later and received no response. I thought they had moved on.
Three weeks later, the recruiter sent a message thanking me for the call and stating that I should submit my availability to speak with the manager, just like that—no apology.
I gave my availability and was scheduled to speak with the manager two days after. The manager turned out to be worse. She literally came unprepared.
To start, she pulled up my resume and was reading it, thinking of questions to ask. She asked about points on my resume, and when I explained the tasks I’d done and the tech stack I used, she literally argued that a particular tool was used for what I mentioned in my resume. She couldn’t even talk about the tools they use in their team.
An interview that was supposed to be 45 minutes lasted less than 30 because she came very unprepared and couldn’t think of any more questions to ask.
I got a rejection email from the recruiter two days after. I thought, “I’m not even interested in working for a team led by such a manager.”
Points on my resume.
Orchestration tools, CI/CD
The following metrics were computed from 17 interview experiences for the The New York Times Software Engineer role in New York, New York.
The New York Times's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for The New York Times's Software Engineer interview process in New York, New York.