Java Developer, full-time, remote, $115,000 a year. Open anywhere. Backend team, enterprise Java applications.
Two years of hands-on Java is the bar here, plus a bachelor's degree. Not two years of a bootcamp certificate and a few personal repos. Two years where your code ran in something people actually used.
What the work looks like
- Design, build, and maintain backend applications and services in Java
- Write unit tests as part of the build, not bolted on after
- Work with other teams — QA, frontend, product — to actually get software out
A batch job is a fair example of what breaks and needs fixing here. One that ran fine nightly for months started silently dropping a small percentage of records after a schema change three teams away added a nullable column nobody flagged to the batch team. Nothing crashed. Nothing threw an error. It just quietly processed less than it should have, and it took a week of comparing row counts against expected totals to even notice. That's the kind of bug Java shops deal with more than people expect when they walk in.
What you need
Java itself, obviously, deep enough to read and fix code you didn't write. Spring Framework experience. Solid SQL. REST APIs. Object-oriented design that goes beyond textbook definitions. Git. A real habit of writing unit tests, not just knowing the theory behind them.
Beyond that, some Kafka or messaging queue exposure helps, as does familiarity with Docker or prior work in a microservices setup rather than a single monolith. None of it is required if the core Java and Spring experience is solid.
Pay
Health insurance, paid time off, 401(k) matching, remote flexibility. Naukri Mitra has a couple of other backend openings up from this employer right now, and this one also includes paid holidays, with occasional team-building events depending on how the broader group is organized that quarter.
The actual rhythm of the job
Enterprise Java codebases tend to be older than what you'd find at a startup, and that's not a knock on the code, just a fact about how long-running systems accumulate history. Reading through a service that's had six different people touch it over four years takes patience most junior developers haven't built yet. It gets easier fast once you've done it a handful of times.
Code review here runs a little slower than some places, mostly because a bug shipped into a system this size doesn't stay contained to one team. That extra scrutiny frustrates some people early on. Most come to see the point of it within the first couple of months.
Applying
Point us to a Java project you've built or maintained, ideally one with real usage rather than a tutorial clone. If you've dealt with a gnarly production bug and fixed it, tell us what happened — that's more useful than a list of frameworks. Since this is fully remote, expect regular collaboration hours with a distributed team, along with the usual mix of async work and live meetings that come with it.
