About Medtronic LABS

At Medtronic LABS, we believe in the power of technology to transform lives, especially where healthcare systems are most fragile. As a mission-driven, non-profit health systems innovator, we design and scale tech-enabled care delivery models that bring essential health services closer to underserved communities. Our work strengthens primary healthcare and creates pathways to better health and equity for people with limited access to care.

This is a unique chance to apply your technology expertise for real-world impact. Not just building software, but enabling better care, greater opportunity, and lasting change for those who need it most.

Medtronic LABS operates in Kenya, Ghana, Sierra Leone, Rwanda, Bangladesh, Tanzania, India, Bhutan, and the United States. Our team values openness, shared purpose, and entrepreneurial drive. We offer meaningful growth for high-performing individuals who are aligned with our mission.

About the role

Ensure OpenPHC's roadmap is executed with technical integrity across every dev team — including teams run by different vendors — so that a change in one module doesn't create downstream breakage elsewhere, and so that code quality stays consistently high. Operates within the guardrails and review processes set up. This role's core performance measure is quality — making the right technical decisions, not just fast ones.

What you’ll do

- Technical fidelity to plan — works directly with the engineering team(s) to ensure technical design choices and actual development track against OpenPHC’s roadmap
- Cross-team alignment — keeps every dev team, working to the requirements they were given; owns cross-module and cross-developer consistency




- Design translation — works with the Product & Engagement Head / Business Analyst to turn product feature requirements into technical design, and surfaces the implications of different technical approaches and stack choices
- Privacy Architecture & Guardrails: Enforces DPDP-by-Design, purpose-bound architecture, and the core invariant: "No clinical data stored in CCE."
- Unblocking — works directly with teams to resolve technical issues and keep delivery on track
- Code quality — owns code quality standards across all dev teams
- QA oversight — makes sure the test strategy the QA Automation Engineer designs is actually executed by both PODs, as an extension of code-quality standards and within the overall QA strategy OpenPHC sets. Does not author the test strategy itself.
- Post-release triage — assesses the technical severity and design impact of post-release bugs and enhancement requests; feeds directly into OpenPHC's sign-off on the overall post-release priority list
- Tech debt & backlog — surfaces technical debt and backlog considerations into the release-strategy trade-off OpenPHC owns

Decision authority
- Makes single-module, day-to-day design decisions independently, within the guardrails. Big-ticket or strategic decisions — performance, security, APIs,



anything cross-module — always go to leadership for sign-off. This is OpenPHC's permanent bottom-line authority, exercised through lighter-touch review as judgement is established, not a restriction that lifts with tenure.
- Escalation duty: Must proactively flag any quality, downstream-impact, or technical-debt risk that conflicts with the Engineering Project Manager's timeline pressure. OpenPHC leadership makes the final call — raising it clearly is this role's responsibility.

What we’re looking for Must-have
- 15 + years building and shipping production systems, comfortable owning technical execution within a defined review process rather than full end-to-end autonomy
- Working literacy in healthcare interoperability standards sufficient to specify an integration and review AI-generated integration code against it
- Track record keeping multiple engineers, including ones not directly managed, consistent with a shared technical standard
- Has used AI coding assistants (Copilot, Cursor, Claude Code or similar) in a real production codebase
- AI-first, 10x mindset — treats AI-assisted review and code-quality tooling as the default way of keeping multiple teams and individual contributors consistent fast, not a manual, one-by-one process

Nice-to-have
- Prior work on an Indian govt/health digital infrastructure project
- Open-source project contribution
- Familiarity with India’s DPDP Act 2023 obligations, or with taking a system through a CERT-In empanelled security audit

Preferred education Tier 1 engineering institute (IIT/NIT/BITS) preferred, not required.

Engagement type: Fixed-term consultancy

Duration: 12 months, fixed term

📌 Architect (Bengaluru)
🏢 Medtronic Labs PBC
📍 Bengaluru