Technical Specialist - Java, Microservices, React.js
Chennai, Tamil Nadu
Job Summary
Software Engineer (Back End)
Build secure, testable and observable services that power Treasury capabilities.
Programme
Treasury Transformation
Role family
Software Engineering
Primary location
India-based delivery, integrated with LBG teams
Role purpose
Design, build and operate cloud-native APIs, microservices and business services that integrate user journeys, specialist engines and governed data products.
Role accountabilities
- Develop back-end services using Java/Quarkus, Node.js or another agreed strategic technology based on the use case.
- Implement secure API layers and service contracts supporting presentation, orchestration, domain and system integration.
- Build for Cloud Run or agreed GCP runtimes with appropriate configuration, scaling and failure handling.
- Integrate with BigQuery, Cloud SQL, data products, events and specialist calculation services.
- Create automated unit, component, contract and integration tests and support end-to-end quality engineering.
- Instrument services with logging, metrics, tracing and actionable alerts.
- Apply secure coding, IAM, secrets, encryption, audit and least-privilege controls.
- Contribute to design, estimation, code review, CI/CD, production support and continuous improvement.
Core skills and experience
- Strong Java and modern service-framework experience; Quarkus experience preferred.
- REST/API design, versioning, error handling, idempotency and contract testing.
- Cloud-native engineering on GCP, containers and managed runtimes.
- SQL and data-access patterns for analytical and operational stores.
- Event-driven design and integration technologies such as Kafka and API management such as Apigee X.
- Automated testing, code quality, dependency management and observability.
- Performance, resilience, security and operability engineering.
Leadership expectations
- Take ownership beyond assigned tickets, from clarification through safe operation.
- Lead technical slices, mentor peers and raise concerns early.
- Use reviews and pairing to improve collective code ownership.
- Work constructively with architects, UI, data, QE and DevOps colleagues.
- Make maintainability and operational impact visible in delivery decisions.
Productivity and delivery expectations
- Deliver small, demonstrable increments with clear acceptance criteria and automated evidence.
- Minimise hand-offs by building, testing, documenting and supporting services as team.
- Use automation and reusable components to improve flow without trading away quality.
- Track lead time, escaped defects, failed changes, reliability and rework as learning signals, not individual scorecards.
Expected behaviours
- Proactive ownership and bias to action.
- Engineering discipline and respect for controls.
- Open collaboration, constructive challenge and timely communication.
- Customer and outcome focus.
- Continuous learning and willingness to simplify.
Evidence of effectiveness
- Working services meeting functional and non-functional acceptance criteria.
- High automated test coverage appropriate to risk and stable pipelines.
- Clear API contracts, operational runbooks and observable production behaviour.
- Low avoidable rework and active contribution to team improvements.
Desirable domain experience
- Regulated or financial-services engineering.
- Treasury calculations, workflows or specialist engine integration.
- mTLS, Apigee X, Kafka and GCP production operations.
Key Responsibilities
Software Engineer (Back End)
Build secure, testable and observable services that power Treasury capabilities.
Programme
Treasury Transformation
Role family
Software Engineering
Primary location
India-based delivery, integrated with LBG teams
Role purpose
Design, build and operate cloud-native APIs, microservices and business services that integrate user journeys, specialist engines and governed data products.
Role accountabilities
- Develop back-end services using Java/Quarkus, Node.js or another agreed strategic technology based on the use case.
- Implement secure API layers and service contracts supporting presentation, orchestration, domain and system integration.
- Build for Cloud Run or agreed GCP runtimes with appropriate configuration, scaling and failure handling.
- Integrate with BigQuery, Cloud SQL, data products, events and specialist calculation services.
- Create automated unit, component, contract and integration tests and support end-to-end quality engineering.
- Instrument services with logging, metrics, tracing and actionable alerts.
- Apply secure coding, IAM, secrets, encryption, audit and least-privilege controls.
- Contribute to design, estimation, code review, CI/CD, production support and continuous improvement.
Core skills and experience
- Strong Java and modern service-framework experience; Quarkus experience preferred.
- REST/API design, versioning, error handling, idempotency and contract testing.
- Cloud-native engineering on GCP, containers and managed runtimes.
- SQL and data-access patterns for analytical and operational stores.
- Event-driven design and integration technologies such as Kafka and API management such as Apigee X.
- Automated testing, code quality, dependency management and observability.
- Performance, resilience, security and operability engineering.
Leadership expectations
- Take ownership beyond assigned tickets, from clarification through safe operation.
- Lead technical slices, mentor peers and raise concerns early.
- Use reviews and pairing to improve collective code ownership.
- Work constructively with architects, UI, data, QE and DevOps colleagues.
- Make maintainability and operational impact visible in delivery decisions.
Productivity and delivery expectations
- Deliver small, demonstrable increments with clear acceptance criteria and automated evidence.
- Minimise hand-offs by building, testing, documenting and supporting services as team.
- Use automation and reusable components to improve flow without trading away quality.
- Track lead time, escaped defects, failed changes, reliability and rework as learning signals, not individual scorecards.
Expected behaviours
- Proactive ownership and bias to action.
- Engineering discipline and respect for controls.
- Open collaboration, constructive challenge and timely communication.
- Customer and outcome focus.
- Continuous learning and willingness to simplify.
Evidence of effectiveness
- Working services meeting functional and non-functional acceptance criteria.
- High automated test coverage appropriate to risk and stable pipelines.
- Clear API contracts, operational runbooks and observable production behaviour.
- Low avoidable rework and active contribution to team improvements.
Desirable domain experience
- Regulated or financial-services engineering.
- Treasury calculations, workflows or specialist engine integration.
- mTLS, Apigee X, Kafka and GCP production operations.
Skill Requirements
Other Requirements
