Back to Jobs

Java Backend Developer

Not Disclosed

Job Description & Details

The role is a senior‑level Java backend gig focused on building and maintaining high‑throughput microservices. You’ll be on an engineering team that cares about clean architecture, performance, and reliability – not just shipping code.

What You'll Actually Be Doing

You’ll spend most of your day designing Spring Boot services, wiring them into a Kafka‑driven event pipeline, and making sure they play nicely with Oracle and Cassandra backends. Expect frequent design reviews where you argue over trade‑offs like synchronous vs async APIs, and you’ll be on‑call for performance tuning using ELK and Prometheus dashboards. Collaboration isn’t optional; you’ll pair with front‑end, QA, and ops folks to ship features end‑to‑end.

The Core Tech Stack

The non‑negotiable skills are Java 8+ (especially concurrency primitives), Spring Boot with Spring Data JPA/Hibernate, and a solid grasp of microservices patterns (service discovery, circuit breaking, eventual consistency). The team leans heavily on Apache Kafka for messaging and ELK for observability, so you need to be comfortable instrumenting logs and metrics. Knowing Oracle and Cassandra schema design is a must because you’ll be juggling relational and wide‑column stores in the same transaction flow.

Interview Expectations

  1. Design a resilient order‑processing pipeline using Spring Boot and Kafka. The interviewer will look for how you handle message ordering, duplicate suppression, and back‑pressure – expect follow‑up on idempotency and transactional guarantees.
  2. Explain the differences between JPA’s first‑level cache and Redis caching, and when you’d combine them. They want to see if you understand cache‑aside patterns, cache invalidation, and the performance impact on read‑heavy services.

Application Advice

Tailor your resume to echo the exact terminology from the JD: “Spring Boot microservices”, “Kafka”, “ELK Stack”, “Oracle & Cassandra”, “JUnit/Mockito testing”, and “Git/SonarQube CI”. Highlight any Azure or Kubernetes exposure, even if it’s on‑prem, because “Cloud experience (Azure) – Nice to Have” shows you’re a plus. Quantify impact (e.g., reduced API latency by 30% through async processing) to satisfy the hiring manager’s focus on performance and reliability.