Full Stack Senior Engineer (Backend)

Role Overview

Patrika runs a high-traffic, mobile-first news platform: breaking news means instant load spikes, WordPress-published content must appear on web and app immediately, and downtime is not acceptable. This role is fullstack, but the weight sits on the backend — NestJS APIs, MongoDB for a read-heavy feed, Redis invalidation driven by CMS webhooks, async queues, and observability actually used in incidents. You still understand the Next.js and React Native consumers you are serving.

What You'll Work On

• Modular REST APIs in NestJS/TypeScript for web and mobile at high concurrency
• BFF endpoints shaped for React Native payloads, not only generic CRUD
• MongoDB schema, aggregations, and indexing for a read-heavy, feed-style product
• Redis caching with invalidation when CMS/WordPress content changes
• Async job queues (BullMQ/RabbitMQ) for notifications, batch work, analytics — with retry/DLQ
• Transform headless WordPress webhooks into clean API responses
• APM, structured logging, health checks behind AWS load balancers
• Own features through design → build → deploy → monitor, including incident response

Who Is Right for This Role

• Production NestJS, TypeScript, MongoDB, and Redis
• Has built and owned REST APIs that serve web and mobile under real traffic
• Has designed a MongoDB schema and index strategy for a read-heavy feed product
• Has implemented Redis in production including invalidation when source data changes
• Has built an async queue where failure recovery actually mattered
• Has used logging/APM to diagnose a real production issue, not only to tick a box
• Understands the Node event loop well enough to know how it fails under load

Who Isn't a Fit

• CRUD-only Node experience with no production concurrency, caching, or queue ownership
• Has never designed Mongo (or equivalent) for a read-heavy feed, or treated indexes as an afterthought
• Has put Redis in front of an API without owning invalidation
• Cannot show a production incident they diagnosed from logs/APM rather than from a user screenshot
• No experience consuming or syncing a CMS/headless WordPress (or equivalent) content pipeline

How You'll Work

• This is a remote contract role.
• Works with frontend, mobile, DevOps, QA, and editorial on publish → cache → client correctness.