Kerja Sepenuh Masa, Engineer (Backend) di PayNet (Payments Network Malaysia) Federal Territory - Maukerja

Why PayNet / Why Now

• Protect the reliability of Malaysia’s national payments data platform
• Operate data systems under increasing scale, scrutiny, and dependency
• Strengthen data resiliency as analytics and reporting become mission‑critical
• Place operational judgment at the centre of trusted payment data

TL;D

• RBuild and scale the backend systems powering Malaysia’s core payment infrastructur
• eOwn APIs, data models, and services that process high‑volume, real‑time transaction
• sMake decisions that directly impact system reliability, performance, and securit
• yIdeal for engineers who thrive on solving complex problems at scale with real‑world impac

t
Why This Role Matte

• rsPayment systems must be fast, secure, and always available—failure is visible at a national lev
• elStrong backend engineering directly impacts financial stability, customer trust, and ecosystem grow
• thPoor design decisions create cascading risks across banks, businesses, and consume
• rsThis role demands judgment under scale—balancing performance, resilience, and securi

ty
What You Will Actually

• DoOwn the design and evolution of backend services powering critical payment fl
• owsBuild and scale APIs that handle high‑volume, low‑latency transacti
• onsShape database architecture, optimizing for performance, consistency, and resilie
• nceDiagnose and resolve complex system issues, driving root‑cause fixes—not quick patc
• hesEmbed security and data protection into system design from day
• oneInfluence engineering standards, code quality, and architectural decisions across syst

ems
Examples of This Role in Prac

• ticeA spike in transaction volume exposes latency—redesign query patterns and caching strategy to stabilise perform
• anceA third‑party integration introduces inconsistent responses—design safeguards and fallback mechanisms to protect system integ
• rityA production issue occurs under load—identify root cause across distributed services and implement permanent f
• ixesA new payment feature requires scale—define API contracts and data models that support future growth, not just current n
• eedsA potential vulnerability is identified—drive architectural changes that eliminate the risk, not just mitigate symp

toms
What Will Help You Su

cceedRequ

• ired: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 solu

tionsHel

• pful:Strong instinct for clean, maintainable code and thoughtful system d
• esignAbility to adapt quickly in evolving environments with shifting require
• mentsEmpathy for end users—building systems that solve real problems, not just technical