Full-time, remote, $118,000 a year. Virtual Python Developer, no location tie. Backend team, production Python services.
Coming in, you need two years of actual Python development behind you and a bachelor's degree. Not two years of tinkering on side projects. Two years where something you built was actually running for real users.
What lands on your desk
- Design and build backend applications and services in Python
- Write automated tests while you build, not after something breaks
- Work across design, frontend, and product to actually ship
Here's a real one: a data migration that looked simple on paper turned into three days of digging once it turned out a chunk of old records had date formatting from a system nobody had documented properly. The tests that eventually caught it weren't fun to write. They were also the only reason a bad migration didn't quietly corrupt live data.
Skills
Python, obviously, and deep enough to debug someone else's mess, not just write clean code from a blank file. Django or Flask. Solid SQL. REST APIs. Git. A testing framework you actually use. Enough cloud deployment know-how to get something running somewhere other than your own machine.
Nice to have on top: async work in Python specifically, some Celery experience, Docker familiarity. None of that is required if the core stuff is there.
Pay
Health insurance, PTO, 401(k) matching, remote flexibility. Naukri Mitra has a few other backend roles open from the same employer right now, and this one also includes tuition reimbursement or a learning stipend for people who want to keep going deeper into the language.
How the days actually go
Cross-team stuff eats more time than people expect. A backend piece that looks quick from the Python side can sit for days waiting on the frontend to lock down what shape they even want the data in. Getting used to that, instead of treating every wait as someone else's failure, matters more than it sounds like it should.
There's older code here too. Not everything gets built fresh with the latest tooling — some weeks go into a codebase that's been around a while and wasn't written with today's conventions in mind. Patience with that beats frustration every time.
Applying
Send a link to something you've built, and tell us what made it hard, not just what it does. If you've written tests for something running in production, say so — it's a real signal here. Fully remote means standard collaboration hours with a distributed team, plus the usual video calls that come with working across functions.
