The New York Times
Software Engineer, Content Data Products
About this role
The New York Times seeks a Software Engineer to join the Content Data Products team, building systems that transform the organization's publishing archive into accessible data products and APIs. You'll collaborate across engineering, product, newsroom, and data teams to develop backend services that power both internal and external offerings within their publishing platform.
What you'll do
- Build content data products and APIs in collaboration with product, design, engineers, and newsroom teams
- Own features end-to-end from requirements through design, implementation, testing, deployment, and monitoring
- Use AI to structure unstructured content archive data into actionable datasets
- Establish architectural best practices for high-concurrency, data-intensive systems
- Drive code quality, security, and system observability standards
- Design automated testing frameworks to ensure service reliability at scale
What they're looking for
- Backend development (Go, Python, Java, or similar)
- SQL databases and data modeling
- API and data backend service design
- Data feeds development
- CI/CD tooling and practices
- Cloud infrastructure (GCP or AWS)
- Application and data security
- Cross-functional collaboration
Benefits
- Hybrid work arrangement (2 days/week in NYC office)
- Work on mission-driven journalism technology
- Collaborate with world-renowned newsroom
- Impact millions of readers globally
Opens the official application on the employer’s site. No login required.
The New York Times
The New York Times builds digital platforms and products that deliver journalism through web, mobile, and multimedia experiences, supported by modern backend systems and AI-enhanced tools. The company is hiring software engineers, QA engineers, and full-stack developers to work across content management, audio/video features, AI-driven reader experiences, and internal developer tooling.
- Website
- nytimes.com
Likely interview questions
- Describe your experience building data backend services and APIs that other teams depend on—what challenges did you face?
- Tell us about a time you owned a feature from design through deployment. How did you ensure quality and security?