Hopscotch - Software Development Engineer – I (Backend)
Nexthire
—
Jul 2, 2026
—
Jul 21, 2026
What this job asks for AI summary
A backend engineering role focused on building and maintaining scalable, distributed systems for a high-traffic e-commerce platform. Day-to-day work involves developing microservices and RESTful APIs in Java 17 with Spring Boot, managing data across MySQL, Redis, and Elasticsearch, and working with AWS serverless and messaging services. Suited to engineers with solid Java backend fundamentals and some exposure to cloud-native architectures.
Junior level · 2+ years · Bangalore, India · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (10)
This role is based in Indiranagar, Bangalore, India (5 days WFO) — US compensation benchmarks do not apply.
The title 'Software Development Engineer – I' explicitly signals a Level 1 / entry-level position, consistent with the 1.5+ years experience requirement; classified as Junior.
The JD states '1.5+ years' of experience; the overall years minimum is set to 2 as the nearest whole-year minimum.
A Bachelor's degree in CS/Engineering is listed under 'What we want' but the JD immediately qualifies it with 'or equivalent practical experience', so no hard degree gate is applied.
ActiveMQ is listed under required skills with the qualifier 'or similar message brokers'; well-known alternatives (RabbitMQ, Kafka) are captured in alternatives.
Docker and Kubernetes appear only under the 'What would be good to have' section and are treated as preferred.
Kibana, Datadog, and Consul also appear only under 'What would be good to have' and are treated as preferred.
AI tools (ChatGPT, Claude AI) mentioned under nice-to-have are omitted as they name no specific engineering technology that would gate a candidate.
AWS EC2, S3, and RDS are listed in the requirements section but are subsumed under the broader AWS skill entry; Lambda, API Gateway, SQS, and SNS are called out separately as they represent distinct service-level requirements explicitly named in the daily responsibilities.
This role's work location reads as outside the US — the candidate pool, comp, and contention benchmarks here are US-only (BLS employment, Adzuna/USAJOBS demand, and certified H-1B wages), so treat them as a rough US reference, not a local market.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.