Technical Delivery Manager

Why PayNet / Why Now

• PayNet is modernizing critical applications and architecture to create technology platforms that are scalable, resilient, and ready for evolving payment needs.
• This transformation includes expanding in-house engineering capability and building stronger ownership of software delivery beyond vendor-led execution.
• As technical complexity grows, PayNet needs leaders who can connect strategic ambition with disciplined engineering decisions and predictable delivery.
• This is an opportunity to shape how modern applications are built, delivered, and continuously improved within Malaysia’s payments ecosystem.

TL;DR

• Own the technical delivery of application modernization initiatives from direction-setting through production outcomes.
• Lead multidisciplinary teams through ambiguity, balancing delivery pace, engineering quality, cost, and risk.
• Shape decisions across software architecture, cloud adoption, delivery planning, and quality standards.
• Build trusted alignment among engineers, product owners, business stakeholders, and external partners.
• Grow PayNet’s internal delivery capability while reducing dependency on outsourced development.

Why This Role Matters

• The quality of technical delivery directly influences the reliability, resilience, and long-term maintainability of PayNet’s modernized applications.
• Strong decisions in this role will turn strategic priorities into working software without compromising quality or creating unmanaged technical risk.
• The role creates clarity when business expectations, engineering realities, resources, and delivery timelines compete.
• It strengthens accountability across teams by making risks, trade-offs, and delivery progress visible to decision makers.
• This role requires judgment over process, with the confidence to challenge plans that do not lead to sustainable outcomes.

What You Will Actually Do

• Own technical delivery outcomes, setting clear priorities and making informed trade-offs across scope, quality, time, cost, and risk.
• Lead engineers and cross-functional contributors through delivery milestones, technical impediments, changing requirements, and continuous improvement.
• Shape technical direction alongside architecture and engineering stakeholders, particularly for cloud-based, scalable, and resilient applications.
• Drive quality by embedding effective testing, automation, continuous integration and delivery, and practical engineering standards throughout development.
• Influence stakeholders through clear, evidence-based communication that translates technical complexity into business choices and consequences.
• Build internal engineering capability through coaching, constructive challenge, knowledge-sharing, and purposeful collaboration with external partners.

Examples of This Role in Practice

• A delivery milestone is at risk, so you bring the right stakeholders together, expose the underlying constraints, and decide which trade-offs protect the most important outcome.
• A proposed technical shortcut could create future instability, so you challenge the approach and guide the team towards a more sustainable solution.
• A modernized application is moving to AWS, so you align architecture, delivery sequencing, testing, security considerations, and operational readiness.
• Delivery depends heavily on a third-party vendor, so you clarify accountabilities, raise quality expectations, and transfer meaningful knowledge to PayNet’s internal team.
• Team performance data reveals recurring bottlenecks, so you turn retrospective insights into focused changes that improve flow, predictability, and product quality.

What Will Help You Succeed

REQUIRED

• Strong judgment across software delivery, with the ability to make balanced decisions when technical, business, cost, and timeline priorities conflict.
• Practical knowledge of software development, Agile ways of working, quality engineering, delivery risk, and modern engineering practices.
• The credibility to engage engineers in technical discussions while communicating clearly with non-technical stakeholders and decision makers.
• A leadership style built on ownership, transparency, constructive challenge, coaching, and accountability for outcomes.

Helpful

• Familiarity with AWS or comparable cloud platforms, containerization, continuous integration and delivery, automated testing, and engineering collaboration tools.
• Exposure to banking, payments, regulated technology environments, application modernisation, or transitions from outsourced to in-house development.