Senior Backend Engineer — CCE POD
Medtronic (company site, opens in a new tab)7–14 yrsBengaluruOn-siteDirect career pageEst. 30–45 LPA
Posted on 17 Sept
Reach people at Medtronic
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Medtronic you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Owns and develops the Care Coordination Engine (CCE) focused on referral tracking, coordination logic, event-driven rules, and integration with CARE HMIS and ABDM/NHCX.
- Leads application-layer security and data protection for OpenPHC, including authentication, consent management, encryption, and audit logging in compliance with security audits and DPDP Act.
- Builds new external government and health-system adapters and co-owns interfacing with the Next Steps-CCE integration, ensuring automated test coverage and configuration-driven India-specific customizations.
Minimum Requirements
- 7–14 years of backend engineering experience with end-to-end ownership of a production service.
- Strong expertise in Java/Spring Boot backend stack and API design/integration.
- Experience with event-driven or rules-engine architectures and strong automated testing discipline.
- Notice period: Not explicitly mentioned in the JD.
Ideal Candidate Profile
- Experienced in building and maintaining secure, integrated backend services in complex health or public infrastructure environments.
- Comfortable working with event-driven rule engines and implementing consent and data rights management aligning with Indian DPDP Act or similar data protection frameworks.
- Able to independently make implementation decisions within module scope and collaborate with architects on cross-cutting security, data governance, and integration concerns.