FINEXUS Group Hiring! Full Time Delivery Manager in Federal Territory - Ricebowl

Why This Role Matters

At Finexus, our ability to deliver reliably is critical to the trust our clients place in us. As we manage multiple bank implementations alongside production support and internal releases, delivery becomes increasingly interconnected — with the same engineering resources, technical dependencies and deadlines often spanning several priorities at once.

The Delivery Manager brings these moving parts together. By creating clear ownership, visibility and discipline across the delivery portfolio, this role helps Finexus anticipate risks earlier, make better resource decisions and deliver commitments with greater consistency — while creating the capacity for the department to take on more as the business grows.

About the Role

As Delivery Manager at Finexus, you will own the overall delivery view across multiple bank implementations, internal product releases and live services. You will be the single point of accountability for delivery across the portfolio, ensuring commitments, dependencies, risks, resources and key milestones are visible and actively managed.

This is not a traditional project management role. You are expected to understand the systems being delivered well enough to challenge technical assumptions, identify dependencies and independently drive solutions through testing, technical acceptance and production readiness.

You will work across Project Management, Engineering, Business Analysis, QA and other technical teams to keep delivery moving, resolve cross-project and technical dependencies, and intervene when commitments are at risk. You will not replace the Project Managers who manage individual projects day to day; instead, you will establish the delivery standards they operate within and ensure the department delivers successfully as a whole.

Over time, you will move the function from tracking what is happening today to anticipating what comes next — giving Finexus leadership a clear, forward-looking view of delivery capacity, technical risks, dependencies and commitments.

Mission / Expected Outcomes

• Create one clear view of delivery across the department, giving Finexus leadership confidence in what is on track, what is at risk and where decisions or intervention are required.
• Drive predictable and disciplined delivery across concurrent bank implementations, internal releases and live services, ensuring commitments, technical dependencies and critical milestones are actively managed.
• Strengthen delivery accountability across functions, bringing Project Management, Engineering, Business Analysis, QA and supporting technical teams together around shared priorities, timelines and outcomes.
• Identify and resolve delivery risks early, including resource constraints, technical and cross-project dependencies, scope changes, certification requirements and regulatory deadlines before they become delivery failures.
• Strengthen technical and production readiness, ensuring solutions progress through the appropriate testing, acceptance and go-live gates before commitments are made or systems are released into production.
• Build a strong run-and-support discipline, improving visibility and management of production support, SLA performance, incidents, releases and service commitments.
• Increase the department's capacity to deliver and scale, enabling Finexus to take on additional client and product commitments without compromising existing delivery.
• Shift delivery management from reactive to forward-looking, providing management with reliable forecasts of upcoming commitments, capacity requirements, dependencies, risks and priorities.

Key Responsibilities:

1. Portfolio Delivery & Client Implementations

• Own the overall delivery outcome across multiple concurrent bank implementations, ensuring commitments are realistic, clearly understood and delivered against agreed timelines.
• Oversee delivery across the full project lifecycle — from kick-off and requirements sign-off through technical design, build, SIT, UAT, non-functional testing, technical acceptance, go-live and hypercare.
• Review project plans and challenge timelines, dependencies, technical assumptions and sequencing before commitments are made to clients.
• Maintain a consolidated view of portfolio risks, issues and dependencies, including certification, regulatory, technical and other external milestones. Escalate material risks early with clear recommendations and recovery actions.
• Maintain delivery discipline around scope and change control, ensuring changes to agreed scope are properly assessed for delivery, technical and resource impact before work proceeds.
• Step into critical client or delivery escalations when issues cannot be resolved at project level, establish clear recovery plans and drive them through to resolution.

2. Cross-Functional & Technical Delivery

• Drive delivery across Project Management, Engineering, Business Analysis, QA and supporting technical teams, creating alignment around priorities, dependencies, timelines and expected outcomes.
• Translate technical designs and solution architecture into clear delivery dependencies across applications, APIs, databases, infrastructure, network, security and external systems, ensuring the right teams are engaged at the right stage.
• Understand technical designs sufficiently to challenge assumptions, identify gaps and recognise when a technical decision creates delivery, performance, security or production risk.
• Establish consistent delivery standards across projects while recognising that Project Managers remain responsible for managing their individual projects day to day.
• Identify and resolve cross-project dependencies and competing resource demands, working with functional leads to determine priorities where multiple commitments require the same resources.
• Forecast resource and capacity requirements across the portfolio, highlighting constraints early enough for management to make informed prioritisation or resourcing decisions.
• Exercise authority over the delivery process through clear facts, influence and accountability, while working effectively across teams outside the role's direct reporting line.

3. Release, Testing, Production & Service Delivery

• Coordinate internal product releases alongside client implementation commitments, working with Engineering and QA to agree release scope, timelines and readiness.
• Ensure appropriate testing is completed before production, including SIT, UAT, security, load and performance testing, with test scenarios aligned to expected business usage, transaction volumes and peak or spike conditions.
• Ensure releases meet agreed readiness criteria, including completion of testing, resolution or acceptance of critical defects, release documentation, rollback planning and technical sign-off before deployment.
• Strengthen governance of live services and production support, including SLA performance, incident and problem management, production changes, patch releases and major-incident root cause follow-up.
• Coordinate production changes with relevant client and internal stakeholders, and support disaster recovery exercises and other operational readiness activities.
• Lead structured support transitions where required, ensuring knowledge transfer, artefact handover, shadowing, acceptance criteria and ownership are completed before Finexus assumes full support responsibility.

4. Delivery Governance, Capacity & Forward Planning

• Establish and maintain a single source of truth for delivery, providing the Head of Department and management with a consistent view of project status, committed dates, risks, dependencies, resource load and decisions required.
• Track delivery performance against agreed commitments and ensure deviations are identified, communicated and acted upon early rather than reported after milestones are missed.
• Provide clear, fact-based reporting that enables management to understand where intervention, reprioritisation or additional capacity is required.
• Develop forward-looking delivery forecasts, providing visibility of upcoming commitments, resource requirements, technical dependencies, potential bottlenecks and delivery risks over the coming months.
• Use portfolio insights and delivery trends to continuously strengthen planning, governance and execution, increasing Finexus' capacity to take on new work while protecting existing client and operational commitments.

Qualifications:

Education & Experience

• Bachelor’s degree in Information Technology, Computer Science, Engineering or a related discipline, or equivalent practical experience.
• 5–7 years of experience in technical delivery, including at least 3 years delivering enterprise software solutions to banks, financial institutions or other large organisations.
• Proven experience delivering at least two complex, end-to-end technology implementations from requirements and technical design through testing, production readiness and go-live.
• Able to understand and navigate system architecture across applications, APIs, databases, infrastructure, network, security and external integrations. You are not expected to design the architecture, but you must be able to understand it sufficiently to challenge assumptions, identify dependencies and drive delivery.
• Able to translate a technical solution into an executable delivery plan: which teams need to be involved, what each party needs to provide, what must happen in sequence, where the risks sit and what is required before production can proceed.
• Experience coordinating delivery across Engineering, Business Analysis, QA, Infrastructure/Cloud, Database, Network, Information Security and client-side technical teams, without relying solely on formal authority to get things done.
• Strong understanding of technical testing and production readiness, including SIT, UAT, security testing, load and performance testing, defect closure, technical acceptance and go-live criteria. You are not expected to execute the tests yourself, but you must understand what needs to be tested and why.
• Experience delivering high-volume, transaction-based or business-critical systems. Exposure to banking, payments or platforms processing approximately 1 million or more transactions per month is highly relevant.
• Able to identify when a technical issue is a delivery risk, understand its impact on timeline, client commitments or production readiness, and drive the appropriate technical teams towards resolution.
• Strong written and spoken English, with the ability to communicate clearly with both technical teams and senior client stakeholders.

Preferred / Good-to-Have

• Direct experience with Malaysian payment rails: DuitNow RPP, RENTAS or SWIFT.
• Working knowledge of Bank Negara Malaysia requirements (RMiT), PCI DSS, or ISO 20022 messaging.
• Familiarity with Java / Spring Boot systems, Linux, and message queues.
• Professional certification: PMP, PRINCE2 or Certified Scrum Master.
• Vendor-side experience — has been on the supplier side of a service level agreement before.