Backend Engineer — Node.js / MongoDB

## The role

We're looking for a backend engineer to own the systems Funngro runs on.

You'll join a team that has built and shipped a mature production platform, learn it quickly, and take full responsibility for it. Within three months we want you owning the backend end to end — the APIs, the database, the scheduled jobs, the integrations and the infrastructure they run on.

This is a broad, high-trust role. Our backend handles user accounts, project workflows, wallets and payouts, and integrations with a wide range of partners. Some of it moves real money to real teenagers, which means correctness matters more here than almost anywhere else you'll have worked.

---

## What you'll own

• **Our APIs** — the services powering the mobile app and our internal tools
• **The database** — schema design, query performance, indexing, growth and retention
• **Scheduled jobs** — a substantial suite handling notifications, payouts, reconciliation and reporting
• **Integrations** — payments and payouts, rewards partners, messaging providers and analytics
• **Money movement** — wallets, payouts and reward ledgers, where accuracy is non-negotiable
• **Infrastructure** — the cloud environment, deployments, monitoring and cost
• **Technical direction for the backend** — architecture, data model and the quality bar

### Essential

• **3–5 years building production Node.js backends** serving real traffic
• **Strong MongoDB experience** — you've designed schemas, written indexes, and diagnosed a slow query in production
• **Experience becoming productive in a large codebase you didn't write.** This matters more to us than almost anything else. Tell us about the biggest one you've worked in and how you got up to speed.
• You've worked on something involving **payments or money movement**, and you understand why that code needs to be treated differently
• Comfortable operating in production — deployments, logs, and handling an incident
• **You ask questions when something doesn't make sense** rather than guessing

### Nice to have

• Sails.js (or another opinionated framework — NestJS, Rails, Laravel all transfer well)
• Redis or another caching layer
• Cloud platform experience — Azure, AWS or GCP
• Payment gateway integrations (Razorpay, PayU or similar)
• SMS, WhatsApp or email delivery at volume
• Performance tuning and cost optimisation

---

## Our stack

Node.js · Sails.js · MongoDB · Redis · Azure · REST APIs · Firebase · payment and payout gateways · SMS, WhatsApp and email providers

---