Principal Backend Engineer

Why PayNet / Why Now Strengthen backend platforms critical to onboarding participants into Malaysia’s payment ecosystemScale and stabilize systems as onboarding volumes, complexity, and integration demands increaseReduce long‑term operational and performance risk through better backend architecture and designOwn backend decisions that directly affect platform reliability, security, and partner experience TL;DR Own and shape the back-end architecture powering high-scale payment systems on AWSLead the shift from outsourced development to strong internal engineering capabilityDrive engineering standards, system performance, and secure, scalable designInfluence how PayNet builds, deploys, and evolves mission-critical services Why This Role Matters PayNet’s ability to scale securely and reliably depends on strong architectural decisions made at this levelPoor system design or weak engineering standards create long-term risk across performance, security, and costThis role defines how fast PayNet can modernise and how effectively it controls its own technology stackRequires judgment over process—balancing speed, quality, risk, and long-term maintainability What You Will Actually Do Own the design and evolution of scalable, secure back-end systems built on AWSDrive engineering standards across code quality, architecture, and system design decisionsBuild, influence, and grow internal engineering capability while reducing reliance on vendorsLead complex technical problem-solving across performance, scalability, and reliability challengesShape API design, data architecture, and integration strategies across platformsDrive adoption of DevSecOps, CI/CD, and automated quality practices across engineering teams Examples of This Role in Practice Decide whether to refactor a core payment service or redesign it for cloud-native scalability—and lead the implementation pathIdentify performance bottlenecks in high-volume transaction systems and drive architectural fixes that reduce latency at scaleTransition a vendor-owned system into an internally built and maintained platform without disrupting live operationsSet organisation-wide standards for API design, testing, and deployment that multiple teams adoptEvaluate trade-offs between speed of delivery and system resilience when launching new payment capabilities What Will Help You Succeed Required strengths Deep backend engineering expertise across languages such as Java, Go, Python, Ruby, or Node.jsStrong architectural judgment in designing distributed, scalable, and secure systemsProven ability to lead technical direction and influence engineering practices at scaleExperience building and operating systems on cloud platforms such as AWS Helpful advantages Exposure to high-availability or transaction-heavy systems (e.g., financial services, large-scale platforms)Familiarity with modern DevSecOps practices, CI/CD pipelines, and observability toolsExperience designing APIs and integrating complex distributed systemsStrength in mentoring engineers and raising the overall engineering bar