CONSULTANT

Atos; Mumbai; On-site; INR 900,000 - 1,800,000; Full time

Job summary

Atos is seeking a Java Spring Boot Developer with 3 to 10 years of experience to design, build, and deploy microservices in an OpenShift/AWS environment. You will develop REST/GraphQL APIs via Apigee, implement event-driven flows with Kafka, and ensure smooth integration with React frontend teams.

The role emphasizes robust testing, CI/CD participation, and governance around AI-assisted coding tools to maintain code provenance and privacy considerations.

Qualifications

• 3–10 years of Java/Spring experience.
• Experience with microservices in cloud environments.
• REST/GraphQL API development experience.

Responsibilities

• Develop and deploy Spring Boot microservices within OpenShift/AWS.
• API development for REST/GraphQL APIs managed via Apigee.
• Implement event-driven logic using Kafka producers and consumers.
• Collaborate with React frontend teams to ensure seamless API consumption.

Skills

Core Java

Spring Boot

Spring MVC

PostgreSQL

Hibernate/JPA

Kafka

Git

Docker

CI/CD

AI-assisted tools

Tools

OpenShift

AWS

Apigee

Job description

Java Springboot Developer with 3 to 10 years experience.

Key Responsibilities

• Microservices Develop and deploy Spring Boot services within an OpenShift/AWS environment.
• API Development Build and maintain REST/GraphQL APIs managed via Apigee.
• Messaging Implement event-driven logic using Kafka producers and consumers.
• Integration Collaborate with React frontend teams to ensure seamless API consumption and data flow.
• Quality Write robust unit/integration tests and participate in automated CI/CD pipelines.

Required Skills

• Core Java 17+, Spring Boot, and Spring MVC.
• Data SQL proficiency (PostgreSQL preferred) and Hibernate/JPA.
• Messaging Basic Kafka (topics, producer/consumer configuration).
• DevOps Git, Docker fundamentals, and CI/CD awareness.
• Demonstrated use of AI-assisted dev tools (e.g., GitHub Copilot, Claude Code assist) and governance (prompt patterns, privacy, code provenance) in daily workflows and clear understanding of limitations/guardrails.