Associate | Full Stack Developer | Bengaluru | Engineering as a Service/ Operate

Role Purpose

Customize, extend, and integrate Deloitte products inside diverse client codebases. The role is deliberately polyglot — engineers will move between Java microservices on one engagement and a React front-end on the next. Strength is rapidly ramp-up on new stacks, not depth in any single one.

Key Responsibilities

• Implement client-specific customizations on top of the product's extension points and configuration layers.
• Build integrations with client systems — identity providers, data warehouses, third-party APIs, internal services.
• Write deployment scripts, configuration manifests, and migration utilities for each engagement.
• Diagnose and resolve production issues during go-live and hyper-care windows.
• Pair with engagement-team developers to onboard them on the product and hand over operational knowledge.
• Document every non-trivial customization pattern so the next POD member can repeat it faster.

Must-Have Skills & Experience

• 2+ years building and shipping production software across at least two distinct tech stacks.
• Front-end competence in at least one modern framework (React, Angular, or Vue).
• Strong with relational and at least one NoSQL data store; comfortable writing performant queries.
• REST/GraphQL API design and consumption, including auth, pagination, error semantics, and versioning.
• Git-based workflows, code review discipline, and an instinct for writing tests.

Nice-to-Have

• Experience with containerization (Docker), orchestration (Kubernetes), and at least one major cloud platform.
• Exposure to event-driven architectures (Kafka, RabbitMQ, cloud-native equivalents).
• Mobile development experience (iOS/Android or React Native).
• Prior client-facing engineering work in a consulting or systems integration setting.

Success in This Role Looks Like

• Ramps up on a new client tech stack within two weeks of engagement kickoff.
• Customizations land cleanly with minimal post-go-live defects.
• Documentation produced is detailed enough so that another engineer can repeat the customization without help.
• Engagement teams request this engineer back by name on future POD pulls.