Java Engineer (Day 2 Operations & Reliability)

Role Overview

We are looking for a Java Specialist dedicated to Day 2 Operations. You will be the guardian of our Java ecosystem, ensuring our applications are performant, observable, and resilient. You won't just be "fixing bugs"; you will be re-engineering existing systems to scale and modernizing our stack for the future.

Key Responsibilities

• Performance Engineering: Conduct deep-dive JVM tuning, heap dump analysis, and garbage collection optimization to ensure high throughput and low latency.

• Modernization & Refactoring: Lead the transition of legacy Java services to modern versions (Java 17/21) and upgrade core frameworks (Spring Boot, Hibernate, etc.).

• Observability: Design and implement advanced monitoring, custom metrics, and distributed tracing to provide 360-degree visibility into application health.

• Stability & Resilience: Identify and resolve systemic issues (memory leaks, thread contention, or database bottlenecks) before they impact the customer.

• Infrastructure Collaboration: Work closely with SRE teams to optimize Java application footprints in Kubernetes (resource limits, startup times, and scaling policies).

• Incident Post-Mortems: Lead technical root-cause analysis (RCA) for production issues and implement permanent code-based fixes to prevent recurrence.

Required Technical Skills

• Java Mastery: Deep understanding of the JVM internals, Concurrency/Multithreading, and Memory Management.

• Spring Ecosystem: Expert knowledge of Spring Boot, Spring Cloud, and Data.

• Monitoring Tools: Experience with Prometheus, Grafana, ELK Stack, and APM tools like New Relic, Datadog, or Dynatrace.

• Cloud/DevOps: Proficiency with Docker, Kubernetes, and CI/CD pipelines (Jenkins, GitLab CI).

• Database Ops: Experience optimizing SQL queries and managing connection pools (HikariCP).

Preferred Qualities

• A "detective" mindset: You enjoy the challenge of finding a needle in a haystack within logs.

• A passion for automation: You prefer writing a script or a tool over performing a manual fix twice.

• Strong communication: You can explain complex production issues to non-technical stakeholders.