Java Technical Lead

Hyderabad, Bangalore,Pune, Chennai,Gurgaon

Mode: Hybrid (2 – 3 Days Onsite per Week)

Experience: 10 + Years 

Immediate to 30 days

Role Summary

We are seeking a skilled Java backend engineer with proven hands-on experience in Spring Boot., preferably in BFSI-grade applications. 

Must‑Have Skills and Depth

Java 11/17

Must have independently developed REST APIs or services using Java 11 or higher, with solid OOP practices, memory management, and concurrency constructs.

Spring Boot

Should be capable of end-to-end microservice/API implementation with clear understanding of dependency injection, controller/repository separation, exception handling, and request lifecycle.

Oracle SQL

Must be proficient in writing complex queries with joins, subqueries, indexes, and query optimization strategies for large datasets (10M+ rows).

REST API Development

Should have implemented multiple REST endpoints with full understanding of HTTP methods, status codes, error schemas, and basic security headers (CORS, auth tokens).

JUnit 5, Mockito

Must have written unit and integration tests with 70%+ coverage, using Mockito for mocking dependencies and achieving isolated testability.

Jenkins, Gradle/Maven

Must have hands-on experience configuring CI jobs in Jenkins and managing project builds via either Gradle or Maven. Deep scripting not mandatory.

Logging (Log4j/SLF4J)

Candidate must have integrated structured logging within applications using standard Java logging frameworks. Should be able to trace logs and debug using correlation IDs.

Git, IntelliJ IDEA

Must be fluent with Git branching, merge conflict resolution, and IntelliJ debugging tools (breakpoints, stack trace analysis, thread dump navigation).

Nice to Have

Splunk / ELK (Monitoring Tools)

Familiarity with log analysis using Splunk or ELK stack for error traceability and performance tracking. Candidate should have used these tools at least in read mode during production support.

Kafka / IBM MQ / Solace

Understanding of messaging system concepts (producer/consumer, topic/queue, durable subscription). Practical experience with at least one such tool preferred.

Harness

Exposure to automated deployment pipelines in Harness is a plus. Not mandatory if Jenkins is known.