Lead Java Engineer

We are looking for a Senior Backend Engineer who specializes in building high-performance, low-latency Microservices using Core Java and deploying them directly onto On-Premises Kubernetes clusters for one of our Banking clients. We operate a strict, high-security, non-Cloud environment and do not use the Spring Boot ecosystem. Instead, we lean into modern, lightweight, or native Jakarta EE architectures. If you thrive on optimising the JVM, managing your own container orchestration, and writing clean, high-throughput code, this role is for you.

What You Will Do :

1. Architect & Build :

- Design and develop scalable microservices using Core Java (Multithreading, OOPs, Collections) and lightweight frameworks.

- Infrastructure Management : Deploy, scale, and maintain containerised applications natively on on-premises Kubernetes clusters.

- Performance Optimisation : Optimise memory footprints, garbage collection, and application startup times without relying on heavy enterprise frameworks.

- Frontend Integration (Good to Have) : Collaborate with or occasionally touch the frontend using ReactJS to ensure seamless end-to-end API integration.

What We Are Looking For (Technical Stack) :

1. Must-Have (Core Stack) :

- Language : Deep expertise in Core Java (Concurrency, Concurrency Utilities, Memory Management, I/O streams). Java 25 is a plus, Java 21, 17 works.

- Hands-On Coding.

- Microservices (No Spring Boot) : Proven experience building microservices using lightweight runtimes/frameworks such as Quarkus, Micronaut, Vert.x, Helidon, or native Jakarta EE / MicroProfile.

- Orchestration (No Public Cloud) : Strong hands-on experience with Kubernetes (on bare-metal or private data centres), Docker, and private container registries.

- Core Standards : Experience with JAX-RS, native JDBC/JPA, and build tools (Maven/Gradle).

2. Good-to-Have :

- UI Experience : Basic understanding or hands-on exposure to ReactJS, JavaScript (ES6+), and state management.

- Advanced Networking : Familiarity with Service Meshes (Istio, Linkerd) or on-premises API Gateways.

What This Role Is NOT :

- This is NOT a Spring Boot/Spring Cloud role.

- This is NOT an AWS, Azure, or GCP cloud-native development role.

(ref:hirist.tech)