The New York Times
Software Engineer, Games
About this role
The New York Times is seeking a Software Engineer to build subscription conversion and monetization features for its Games platform. You'll develop user-facing interfaces using React and TypeScript, collaborate across teams to drive player value and revenue, and own features end-to-end from design through production in a hybrid NYC role.
What you'll do
- Develop frontend entry points in React and TypeScript to help players understand Games subscription benefits across web and mobile
- Collaborate with product and partner teams to optimize sales funnels, landing pages, and subscription conversion surfaces
- Participate in full development lifecycle including technical design, code review, testing, and production releases
- Instrument features for observability and experimentation, defining and tracking success metrics with analytics teams
- Debug and resolve issues across frontend code, Node.js services, and AWS infrastructure
- Participate in on-call rotation and help improve frontend architecture and shared components
What they're looking for
- React and TypeScript
- HTML, CSS, and JavaScript
- Node.js backend development
- Web performance and accessibility
- Git version control
- Production debugging and monitoring
- A/B testing and experimentation
- Collaboration with cross-functional teams
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
- Can you walk us through a time you optimized a user-facing feature for conversion or engagement? What metrics did you track?
- Describe your experience with A/B testing platforms—how have you used experimentation to validate product decisions?