Hey, if you like the part of building software that nobody sees, this one's for you. It's a full-time, fully remote Backend Developer role paying $118,000 a year, open to anyone anywhere.
You won't be pixel-pushing here. The team needs someone who's genuinely comfortable owning the machinery behind an application, the databases, the APIs, the parts that keep everything running when ten thousand people hit the site at once instead of ten. If that sounds like the fun part of the job rather than the boring part, keep reading.
What you'd own
- Design and write the logic that powers the app from behind the scenes
- Keep the databases and APIs healthy, not just functional but genuinely well-run
- Watch for performance bottlenecks and fix them before users notice anything's wrong
That third one is where the job gets interesting. Anyone can write code that works fine with a hundred test records. Making it hold up under real traffic, real concurrency, real edge cases- that's a different skill, and it's the one this role is really testing for. A good chunk of the week goes into reading query plans, watching latency graphs, and figuring out why something that ran fine last month is suddenly slower now that the dataset's grown.
What you'd bring
A computer science degree covers the baseline education requirement here. Two years of hands-on experience actually shipping and maintaining backend systems is what the team's looking for, not just coursework or a bootcamp. Database and system design need to already be strong, since much of the day-to-day involves decisions that are hard to walk back later, like schema choices that ripple through everything built on top of them for years.
One story worth mentioning: a previous hire once picked a document database for a project that turned out to need heavy relational joins six months later, and untangling that migration ate three sprints the team could've spent building new features instead. Getting the data model right early matters more than it might seem.
None of this means the team wants someone rigid or overly cautious. Plenty of decisions here are genuinely reversible, and moving fast on those is fine. Knowing which is which, that's the actual judgment call the role is testing for.
Skills
- A server-side language, Python, Java, or Node.js all work here
- Databases, both relational and non-relational
- REST APIs
- Cloud services, AWS or GCP experience is common on the team
- System design chops
- Git
Most of these show up together in practice rather than as separate boxes to check. Someone who's genuinely strong in system design has usually also developed real instincts around databases and APIs along the way, since the three tend to be exercised together on any real project.
Beyond the core list, experience with message queues like Kafka or RabbitMQ helps, and so does any exposure to Kubernetes if the role grows toward infrastructure work later. Nice to have, not gatekeeping. A candidate strong on the fundamentals and light on these extras will still get a fair look; someone can pick up a specific queueing tool in a couple of weeks, but they can't pick up solid database instincts nearly as fast.
Pay and what comes with it
Base pay is $118,000 a year. On top of that comes a standard package: medical coverage, a real PTO policy rather than an unlimited-in-name-only one, and a 401(k) with company matching. Remote here actually means remote, not a euphemism for being expected to be online at all hours, regardless of time zone. There's also a bonus paid out each quarter, sized to how you and the team performed over that stretch rather than a flat annual number handed out once a year. For anyone weighing this against other remote backend developer jobs, the salary is in the middle of the market for someone two years into backend work, and the quarterly structure helps close the gap for people who perform well.
- Health insurance
- Paid time off
- 401(k) matching
- Remote-work flexibility
- Quarterly performance bonuses
What the work actually feels like
Most days are heads-down, which is exactly what draws many backend engineers to this kind of role in the first place. There's a standup, sure, but it's short, and the rest of the day is yours to actually build. On-call rotates through the team roughly once a month, and yes, there will be a night here and there when something breaks, and you're the one fixing it. That part's real. The team keeps the rotation fair, and the incident count genuinely low, but nobody's going to pretend a distributed system never falls over. Most on-call weeks pass without a single page; the rare ones that don't tend to get a proper post-mortem afterward rather than getting quietly forgotten.
Naukri Mitra posts a fair number of backend roles across different teams, and this one tends to draw people who came from frontend or full-stack work and realized they liked the backend half more. That's a completely normal path in here, and it's often a stronger signal than a resume that's been backend-only from day one, since it usually means the person actually chose this specialty rather than defaulting into it.
Growing into it
Someone figuring out how to become a remote backend developer without years of prior specialization usually gets there through exactly that kind of pivot, spending time on smaller side projects that force real database and API decisions, then bringing that judgment into a full role like this one. The technical bar is real, but it's built through practice more than credentials. Two or three well-built personal projects, each with a genuine data modeling problem baked into it, usually do more for a resume than a stack of certifications.
Apply
Send a resume along with a link to something you've built where the backend was the interesting part, a project with real data modeling decisions behind it, not just a CRUD app following a tutorial. If you've got a war story about a system you had to scale or fix under pressure, include it; that kind of detail shows how you actually handle pressure, which a skills list can't capture. No fixed deadline on this one; applications come in and get reviewed continuously.
