Summary
✨ AI‑Generated
A senior backend engineer is sought to build and scale systems supporting high-volume, real-time financial transactions. The role owns APIs, data models, and services while addressing reliability, performance, security, and resilience challenges in mission-critical infrastructure.
Highlights
High-impact engineering work on critical national-scale payment infrastructure, with strong emphasis on reliability, security, performance, and operational judgment.
Description
Why PayNet / Why Now
Protect the reliability of Malaysia’s national payments data platformOperate data systems under increasing scale, scrutiny, and dependencyStrengthen data resiliency as analytics and reporting become mission‑criticalPlace operational judgment at the centre of trusted payment data
TL;DR
Build and scale the backend systems powering Malaysia’s core payment infrastructureOwn APIs, data models, and services that process high‑volume, real‑time transactionsMake decisions that directly impact system reliability, performance, and securityIdeal for engineers who thrive on solving complex problems at scale with real‑world impact
Why This Role Matters
Payment systems must be fast, secure, and always available—failure is visible at a national levelStrong backend engineering directly impacts financial stability, customer trust, and ecosystem growthPoor design decisions create cascading risks across banks, businesses, and consumersThis role demands judgment under scale—balancing performance, resilience, and security
What You Will Actually Do
Own the design and evolution of backend services powering critical payment flowsBuild and scale APIs that handle high‑volume, low‑latency transactionsShape database architecture, optimizing for performance, consistency, and resilienceDiagnose and resolve complex system issues, driving root‑cause fixes—not quick patchesEmbed security and data protection into system design from day oneInfluence engineering standards, code quality, and architectural decisions across systems
Examples of This Role in Practice
A spike in transaction volume exposes latency—redesign query patterns and caching strategy to stabilise performanceA third‑party integration introduces inconsistent responses—design safeguards and fallback mechanisms to protect system integrityA production issue occurs under load—identify root cause across distributed services and implement permanent fixesA new payment feature requires scale—define API contracts and data models that support future growth, not just current needsA potential vulnerability is identified—drive architectural changes that eliminate the risk, not just mitigate symptoms
What Will Help You Succeed
Required:
Strong command of at least one backend language (Java, Golang, Python, Node.js) with the ability to apply it at scaleProven ability to break down complex system problems and drive effective, lasting solutionsHelpful:
Strong instinct for clean, maintainable code and thoughtful system designAbility to adapt quickly in evolving environments with shifting requirementsEmpathy for end users—building systems that solve real problems, not just technical ones