Kerja Sepenuh Masa, Solutions Architect 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;DR

• Own end‑to‑end architecture for national‑scale, real‑time payment platforms
• Decide architecture trade‑offs across performance, security, resilience, and compliance
• Set and enforce architecture guardrails without relying on hierarchy
• Act as the final technical authority for consequential design decisions

Why This Role Matters

• Architecture decisions directly affect national payment availability and trust
• Weak architectural judgment creates regulatory, operational, and reputational risk
• Strong architecture enables safe transaction growth under peak load
• This role requires judgment over process and outcomes over activity

What You Will Actually Do

• Own architecture decisions across the full system lifecycle for payment platforms
• Define and enforce architecture standards, patterns, and guardrails
• Lead architectural due diligence for vendors and third‑party integrations
• Drive legacy modernisation and technical debt reduction through structured roadmaps
• Design for resilience, security, and observability as first‑class architecture concerns

Examples of This Role in Practice

• Blocking a design that meets functional needs but fails under national transaction peaks
• Leading architecture decisions for a live payment migration with zero customer impact
• Translating regulatory requirements into concrete, enforceable architecture patterns
• Challenging vendor proposals that compromise PayNet’s security or operability standards

What Will Help You Succeed

• Deep experience designing distributed, high‑availability transaction systems
• Ability to reason about failure modes, consistency trade‑offs, and operational risk
• Strong technical communication across engineers, executives, and regulators
• Comfort acting as the decisive technical voice without formal authority