Senior Engineer (Backend)

PayNet (Payments Network Malaysia); Kuala Lumpur; On-site; MYR 150,000 - 230,000; Full time

Job summary

PayNet (Payments Network Malaysia) is seeking an experienced backend engineer to own the design and evolution of backend services powering Malaysia’s critical payment flows. You will build and scale APIs handling high-volume, low-latency transactions, and shape database architecture for performance, consistency, and resilience.

You’ll diagnose complex system issues, drive root-cause fixes, and embed security and data protection into system design from day one.

Qualifications

• Strong command of at least one backend language (Java, Golang, Python, Node.js).
• Proven ability to break down complex system problems and drive lasting solutions.
• Experience with high-volume, low-latency transactional systems.
• Understanding of security and data protection in system design.

Responsibilities

• Own the design and evolution of backend services powering critical payment flows.
• Build and scale APIs that handle high-volume, low-latency transactions.
• Shape database architecture, optimizing for performance, consistency, and resilience.
• Diagnose and resolve complex system issues, driving root‑cause fixes—not quick patches.
• Embed security and data protection into system design from day one.
• Influence engineering standards, code quality, and architectural decisions across systems.

Skills

Backend development

Java

Golang

Python

Node.js

Job description

• 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;DR

• Build and scale the backend systems powering Malaysia’s core payment infrastructure
• Own APIs, data models, and services that process high‑volume, real‑time transactions
• Make decisions that directly impact system reliability, performance, and security
• Ideal 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 level
• Strong backend engineering directly impacts financial stability, customer trust, and ecosystem growth
• Poor design decisions create cascading risks across banks, businesses, and consumers
• This 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 flows
• Build and scale APIs that handle high-volume, low-latency transactions
• Shape database architecture, optimizing for performance, consistency, and resilience
• Diagnose and resolve complex system issues, driving root‑cause fixes—not quick patches
• Embed security and data protection into system design from day one
• Influence 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 performance
• A third‑party integration introduces inconsistent responses—design safeguards and fallback mechanisms to protect system integrity
• A production issue occurs under load—identify root cause across distributed services and implement permanent fixes
• A new payment feature requires scale—define API contracts and data models that support future growth, not just current needs
• A 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 scale
• Proven ability to break down complex system problems and drive effective, lasting solutions

Helpful:

• Strong instinct for clean, maintainable code and thoughtful system design
• Ability to adapt quickly in evolving environments with shifting requirements
• Empathy for end users—building systems that solve real problems, not just technical ones