Java Technical Delivery Manager (NCS/Job/ 3243)

Job Description

Technical Delivery Manager (TDM)

Role Overview

The Technical Delivery Manager (TDM) is a techno‑functional leadership role with strong emphasis on technical ownership. The TDM is accountable for end‑to‑end technical delivery of applications, while also managing stakeholder communication, risk, and delivery governance.

This role is critical in a banking modernization program, where applications are being migrated from monolithic architectures to microservices across Java and .NET technology stacks.

As discussed, the role is ~70% technical and ~30% functional/management.

Key Responsibilities

1. Technical Ownership (Primary Responsibility)

• Act as the technical owner of one or more applications
• Take complete ownership of:
  • Application architecture
  • Technical design decisions
  • Development challenges
  • Deployment and production issues
• Provide guidance and resolution for:
  • Development team issues
  • Support and operations team issues
• Ensure technical decisions align with modernization and microservices strategy

2. Application Modernization & Architecture

• Drive modernization initiatives, including:
  • Migration from monolithic to microservices architecture
• Guide teams on:
  • Architecture breakdown
  • Service design
  • Scalability and performance considerations
• Prioritize candidates with prior modernization experience
  • This was explicitly called out as a strong differentiator

3. Technology Leadership (Mandatory Background)

The TDM must come from a strong development background.

• Background must be technical (Java / .NET)
• Should not be purely functional or finance background
• Expected to be aware of:
  • Java versions (8, 17, 20+ as applicable)
  • .NET versions and ecosystem
• Able to:
  • Understand technical issues raised by teams
  • Provide direction or solutioning
• Code review responsibility:
  • Required when teams are small or when no separate tech lead exists
  • Otherwise guided through senior developers / leads

4. Delivery & Environment Management

• Own delivery across environments:
  • Development
  • UAT
  • Production
• Understand and guide:
  • Manual deployments (majority)
  • Partial DevOps‑based deployments
• Participate in:
  • UAT deployment discussions
  • Production deployment bridges
• Ensure developers support deployments and not treat it as “someone else’s job”

5. Stakeholder & Client Communication

• Act as primary technical interface with client stakeholders
• Represent the delivery team with:
  • Application Owners
  • SDG / ICC stakeholders
• Communicate clearly on:
  • Scope
  • Timelines
  • Risks
  • Dependencies
• Proactively raise risks and mitigation plans instead of waiting for escalation

6. Team & Delivery Management

• Manage teams typically ranging from:
  • 10 to 30+ members
• Handle:
  • Multiple applications (minimum 2 or more)
• Coordinate across:
  • Development teams
  • Support teams
  • Infra, network, and storage teams
• Ensure smooth coordination across multiple technical towers

7. Functional / Management Responsibilities (Secondary – ~30%)

• Delivery planning and tracking
• Dependency and risk management
• Schedule and milestone ownership
• Coordination with multiple teams for delivery readiness

Budgeting and pure PM activities are minimal compared to technical responsibilities.

Mandatory Skills & Experience

Technical Skills

• Strong hands‑on background in Java or .NET
• Good understanding of:
  • Microservices architecture
  • Enterprise application delivery
• Ability to support both Java and .NET teams is a strong advantage

Delivery & Leadership Skills

• Proven experience owning technical delivery
• Strong communication and negotiation skills
• Ability to manage multiple applications and stakeholders
• Proactive mindset with ownership attitude

Role Fitment Notes (As Discussed)

• This role is not:
  • A pure Scrum Master
  • A purely functional Project Manager
• This role combines:
  • Technical leadership
  • Delivery ownership
  • Stakeholder management
• Best suited for:
  • Senior technical professionals who have moved into delivery roles
  • Candidates comfortable handling both engineering and delivery pressure

Position Details

• Role Type: Technical Delivery Manager (Techno‑Functional)
• Expected Demand: ~7 positions (as discussed; subject to confirmation)
• Primary Technology Preference: Java (with .NET as additional advantage)
• Program Context: Large‑scale banking modernization (140+ applications)

✅ Client‑Ready & Panel‑Aligned

This JD:

• Matches customer expectations
• Aligns with panel evaluation
• Clarifies why this role is different from PM / Scrum / Architect
• Can be shared with client, TA, and internal sourcing teams