Android Engineer Interview Experience - United States
Process
The interview process at the New York Times was quite thorough. The recruiter did a great job of keeping me updated on the next steps throughout the process and helping me prepare effectively.
It took about 8-9 weeks between my applying for the role and receiving an offer.
The interview process consisted of:
- A recruiter screen
- A hiring manager screen
- An Android system design interview
- A culture/values interview
- An Android live coding interview
- A cross-team collaboration interview
After passing all the interviews, a reference check with former coworkers was required.
The interview process was fair and felt thoughtful/relevant to the role. All of the people on the hiring panel seemed like great people to work with. A strong cultural fit felt like something they valued quite a bit.
Ultimately, though, the compensation was less than other competing offers and industry standards for the role.
Questions
How do you deem a feature to be production ready?
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the The New York Times Android Engineer role in United States.
Success Rate
The New York Times's interview process for their Android Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for The New York Times's Android Engineer interview process in United States.
The New York Times Work Experiences
- 4.0It was goodSoftware Developer • Current EmployeeNovember 13, 2025Pros: Supportive staff, good manager, good pay, no pressure.Cons: Timings are a bit too long.
- 5.0Freedom to Learn, Build, and ContributeIOS Engineer Intern • Former EmployeeNew York, New York, United StatesNovember 13, 2025Pros: The people are genuinely kind and supportive. The internship program is well-structured but gives you the freedom to explore and grow—it’s really what you make of it. You get to work on real, impactful projects that ship to production, not just intern tasks.Cons: You’re typically the only intern on your team, so you may not collaborate directly with other interns on your project. However, there is still a strong intern cohort and plenty of planned events to connect outside of your day-to-day work.
- 4.0Good, but getting worseStaff Software Engineer • Current EmployeeNew York, New York, United StatesOctober 24, 2025Pros: Generally a friendly place to work. People like what they do and are great to work with.Cons: They are less and less interested in building great software and more and more interested in short-sighted, quick wins.
