Apj Technology Leader, Heart Recovery

Johnson & Johnson Johnson & Johnson · Pharma · Singapore

Technology Leader for Heart Recovery in the APJ region, responsible for driving regional technology strategy, demand shaping, portfolio management, budget oversight, and delivery of solutions across Commercial, Supply Chain, and R&D. This role requires self-sufficiency, relationship building, and ensuring solutions align with global standards while meeting regional business outcomes.

What you'd actually do

  1. Build deep relationships with APJ leaders to understand priorities, proactively identify opportunities, and translate needs into a clear, sequenced technology roadmap and demand pipeline.
  2. Represent APJ needs to global product and platform owners; define requirements, size work, manage dependencies, and drive reuse of global capabilities over local build.
  3. Lead intake, prioritization, and governance; build and manage the in-scope budget from the ground up across technology investments and people; define OKRs and metrics; and track value realization and portfolio health.
  4. Orchestrate end-to-end delivery with global squads and APJ teams; drive release readiness, change management, training, and sustained adoption. Initial phase is to: - Stabilize and shape the APJ demand funnel - Establish portfolio and governance operating rhythm - Drive adoption of the first wave of APJ deployments
  5. Ensure solutions meet security, privacy, and quality/compliance expectations; surface and resolve risks early and escalate when needed.

Skills

Required

  • 8+ years in technology/digital/product leadership
  • sustained partnership with senior business leaders
  • Experience defining roadmaps
  • leading delivery in a matrixed, cross-geography environment
  • Bachelor’s degree

Nice to have

  • master’s degree

What the JD emphasized

  • strong understanding of the technical nuances of delivering technology across a highly diverse region (e.g., varying regulatory and data-residency requirements, infrastructure maturity, integration landscapes, localization needs, and deployment/adoption constraints)