Getting an Interview
Getting an Interview
Interviews for Top Jobs at New York Times
- Senior Software Engineer (4)
- Intern (3)
- Marketing Manager (2)
- Project Manager (2)
- Web Developer (2)
- Senior Developer (1)
- Senior Java Developer (1)
- Designer (1)
- Digital (1)
- Executive Assistant (1)
- Sales Representative (1)
- Data Engineer (1)
- EA (1)
- Digital Media Planner (1)
- Systems Administrator (1)
- Senior Front End Engineer (1)
- Manager of Web Development (1)
- IOS Developer (1)
- Senior IOS Developer (1)
- User Experience Research Manager (1)
- Sales- Advertising (1)
- Ios Software Engineer (1)
- Director of Customer Research (1)
- Assistant Editor - Video Content (1)
- Ad Technology Manager (1)
- Freelance Graphic/Web Designer (1)
- Director Marketing Planning (1)
- Software Development Engineer In Test/Software Development In Test (1)
- Team Lead of Help Desk (1)
- Product Manager, Web Products (1)
- No OfferNeutral ExperienceAverage Interview
Everyone was very nice and welcoming; obviously smart. However, the process itself was a bit disorganized. I have no complaints with the environment or the people, and they handled a last minute scheduling issue well.
- Very standard questions about goals and transferable skills. Answer Question
Helpful (3)No OfferNegative ExperienceDifficult Interview
I applied online. The process took 2 days – interviewed at New York Times.
- Q: What happens when typing a URL into a web browser? 1 Answer
- No OfferNeutral ExperienceAverage Interview
I applied through college or university. The process took 2+ weeks – interviewed at New York Times.
HR set up the interview time with manager and director. Standard interview questions with manager then dive into more details of previous work experience with director. I thought we had a nice conversation but I didn't hear from them later on. Probably they hired other candidates.
- Why you feel interested in this position Answer Question
- No OfferNegative ExperienceAverage Interview
Received a call from HR followed by an in-person interview. Did not get a call back explaining why they decided not to proceed. When I followed up, received no response. Glad I didn't receive an offer as I wouldn't want to work for a company that treats potential applicants in such an unprofessional manner.
- What are your strengths and weaknesses Answer Question
Helpful (1)No OfferNegative ExperienceDifficult Interview
I applied online. The process took a week – interviewed at New York Times in March 2015.
I received a single sentence, grammatically incorrect email from a recruiter asking for my availability for a phone interview. Later that week I interviewed with the a manager by phone. While answering most questions, I would get cut off as "that’s enough" leaving me unsure if I was correctly answering the question, going down the wrong avenue of discussion, or answering the question incorrectly. The interview did not seem very concerned with me as a developer or how I would fit the position aside from lots of trivia about obscure parts of various frameworks and browser networking. Most of the questions were fairly easy or straightforward (CORS, scope, HTTP requests, DNS lookup, caching) while some were more implementation specific (Backbone initialization functions and differences between Backbone and Marionette). I received no follow up and had to reach out to find out my status.
- How can you know when an Angular Directive is done updating? 1 Answer
Helpful (1)No Offer
interview with general political and business news, as well as historical questions. Some opinions, and others are behavioral questions. Most of them are general knowledges learned in high school/college, but some are related to real market.
- What do you think of Cultural revolution? Answer Question
Helpful (3)No Offer
I applied through a recruiter – interviewed at New York Times (New York, NY).
Had an easy phone interview and then was sent a problem to solve as homework. The problem was not hard - just had to download a json response, parse the response and convert the text. Didn't receive any feedback as to what they were looking for. Simply a rejection. I've been an iOS Engineer for 5 years and was stumped as to what was wrong. Another colleague went through the same process about the same time frame and he has similar iOS development experience with an MS in computer science and he experienced the same thing with his problem. It makes you wonder whether or not they are actually hiring people. I spent about 8 hours on the problem and so did my friend.
- Nothing was too difficult or unexpected Answer Question
Helpful (5)No OfferNegative ExperienceEasy Interview
I applied through a recruiter. The process took 3 weeks – interviewed at New York Times (New York, NY) in July 2014.
The recruiter contacted me about a Data Scientist position and submitted my resume. First, I spoke with the hiring manager and then with one of the resident data scientists in two separate calls. I pass the telephone screens and get invited to an onsite interview. I get there, and the first two interviewers (same session) start asking me to type Unix commands. I'm thinking to myself, uh shouldn't I be explaining the details of a random forest to you? Then it hits me.... they are interviewing me for a Data Engineer position. Bait and switch. I then have a series of five interviews, all very easy questions about linked lists, depth-first searches, and some Python code to debug (Hint: it's a deep copy). Two of the interviewers were non-technical managers who couldn't hack it in Silicon Valley, so they returned to the NYT nest. For the duration of the afternoon, I was thinking to myself, man these people are jaded but certainly have no reason to be. The exception was a brilliant engineer from the Caribbean, and I was thinking okay, this is cool. His manager was present during this interview, and clearly he did not like the way we were bonding during a coding exercise on the whiteboard. As other interviewers pointed out, it's about liking you, and if one of them does not, then you're hit. As far as technical expertise, keep it in your head.
- No OfferEasy Interview
I applied online. The process took 1 day – interviewed at New York Times in June 2014.
I applied online for the role of Team lead at the Help Desk. The interview was very easy and nice. Met with three different managers. Sadly never heard a peep back even after a thank you email was sent.
- This was not a difficult interview. Answer Question
Helpful (1)No OfferNegative ExperienceEasy Interview
I applied through a recruiter. The process took a week – interviewed at New York Times (New York, NY) in May 2014.
The phone screen was a breeze and the code test wasn't that hard, but they never followed up with me. I never found out if my code was bad, or if they just moved on to another candidate. I still wish they offered the feedback, is it really that much to offer?
- The phone screen barely had any technical questions 1 Answer
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review