{"id":1274973,"url":"https://alion.io/job/paynet-backend-engineer-platform-engineering","title":"Backend Engineer - Platform Engineering","company":{"id":2112342,"name":"PayNet","domain":"paynet.my","url":"https://alion.io/company/paynet-my","size_band":null,"is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"BrioHR","truth_index":null},"role":"Backend","role_family":"Backend","seniority":"senior","employment_type":null,"work_mode":"on_site","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["Malaysia"],"countries":["MY"],"hiring_countries":[],"hiring_countries_total":0,"salary":null,"salary_estimate":{"min_usd":17500,"max_usd":47000,"period":"year","method":"global_role_cell_scaled_by_country","sample_n":4445},"experience_years_min":5,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"Agile","optional":false},{"name":"CI/CD","optional":false},{"name":"Git","optional":false},{"name":"Go","optional":false},{"name":"Java","optional":false},{"name":"Node JS","optional":false},{"name":"Python","optional":false},{"name":"Spring Boot","optional":false},{"name":"SQL","optional":false},{"name":"JavaScript","optional":true}],"status":"live","first_seen_at":"2026-09-26T01:11:32Z","employer_posted_date":"2026-09-26","last_verified_at":"2026-09-26T13:51:25Z","board_verified":true,"closed_at":null,"days_open":1,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":1},"description":"Why PayNet / Why Now\nStrengthen backend platforms critical to onboarding participants into Malaysia's payment ecosystem\nScale and stabilize systems as onboarding volumes, complexity, and integration demands increase\nReduce long-term operational and performance risk through better backend architecture and design\nOwn backend decisions that directly affect platform reliability, security, and partner experience\nTL;DR\nDesign and own backend services that underpin critical participant onboarding platforms\nBuild scalable, secure, and high-performance systems used at national scale\nOperate as a self-directed technical owner - identify problems, propose solutions, and drive them to production with minimal handholding\nSet the code review bar and technical delivery standards for the team\nActively coach junior engineers through their day-to-day work, not just in passing\nWhy This Role Matters\nBackend systems directly impact the reliability and scalability of national payment onboarding\nPoor architectural decisions create long-term operational risk and rework\nSenior engineers set the technical bar for quality, performance, and security\nStrong backend ownership enables faster delivery without compromising stability\nA senior who can operate independently frees leads/architects to focus on cross-team and strategic problems\nWhat You Will Actually Do\nOwnership & Solutioning\nTake a problem statement (not a spec) and independently research, propose, and defend a technical solution - including trade-off analysis, not just implementation\nDesign and lead architecture for scalable, high-performance backend systems, from first principles where needed\nOwn end-to-end delivery: design → build → test → deploy → post-release stability, with minimal supervision once direction is aligned\nProactively flag architectural or scalability risks before they become production incidents, rather than waiting to be asked\nEngineering\nDevelop and maintain backend services and RESTful APIs using Java, Golang, or Python\nDesign and optimize database schemas and queries to ensure performance and data integrity\nWrite unit and integration tests as a default part of delivery, not an afterthought\nTroubleshoot complex production issues and drive root-cause analysis through to permanent fixes\nCode Review & Engineering Practices\nSet and enforce code review standards (PR size, test coverage expectations, security checks, documentation)\nReview peers' and juniors' code with a bias toward teaching - explain the \"why,\" not just flag the \"what\"\nChampion CI/CD, branching, and release discipline appropriate to a national payment system (audit trail, rollback safety, change management)\nAdapt quickly to the team's existing tooling, workflows, and review culture - able to plug into an established process within the first few weeks rather than needing it re-explained repeatedly\nExamples of This Role in Practice\nGiven only \"onboarding is timing out under load,\" independently profiles the system, identifies the bottleneck, and ships a fix - without needing the root cause pre-diagnosed for them\nRefactoring database queries to remove performance bottlenecks before they're flagged by monitoringLeading code reviews that catch security or reliability issues before merge, and using the review as a teaching moment for the author\nOwning a critical production incident end-to-end: triage, root cause analysis, fix, and postmortem write-up\nSpending 3-5 hours a week (not just \"when there's time\") on pairing or reviewing with junior engineers\nAdapting within the first sprint or two to the team's existing Git workflow, review cadence, and definition-of-done - asking sharp clarifying questions rather than needing repeated onboarding\n\nWhat Will Help You Succeed\nRequired\n5+ years of backend engineering experience, with strong proficiency in Java/Spring Boot (Golang or Python a plus)\nProven track record of end-to-end ownership: design, troubleshooting, structured problem analysis, and unit testing\nProven experience building RESTful APIs and scalable backend systems\nSolid understanding of relational databases, SQL, and performance optimization\nStrong, structured problem-solving ability - can walk through how they diagnose an issue, not just state the fix\nExperience mentoring engineers in a hands-on, ongoing capacity, and working in Agile environments\nHelpful\nExperience across multiple backend languages or frameworks (e.g., Golang, Node.js)\nExposure to microservices and distributed systems architecture (event-driven design, sagas, service boundaries)\nExperience integrating third-party APIs and external services\nFamiliarity with CI/CD pipelines and deployment automation\nKnowledge of backend security best practices (authentication, authorization, data protection) especially relevant in a payments context\nExperience with monitoring, logging, and performance tuning tools\nPrior experience in fintech, payments, or other regulated/high-availability environments","description_format":"text","description_chars":4956,"description_truncated":false,"requirements":{"experience_years_min":5,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[],"hiring_excludes":[],"relocation_offered":false,"industries":[],"lifecycle":[{"event":"open","at":"2026-09-26T01:11:32Z"}],"liveness":{"score":86,"band":"hot","label":"Hiring now","p_open":1,"p_active":0.86,"p_room":1,"age_days":0,"expected_fill_days":24,"reasons":["conf:4","win:early"],"computed_at":"2026-09-26T05:45:00Z"},"pay":null,"html_url":"https://alion.io/job/paynet-backend-engineer-platform-engineering","json_url":"https://alion.io/job/paynet-backend-engineer-platform-engineering.json","meta":{"generated_at":"2026-09-27T03:12:06Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","usage":{"tier":"assistant","counted_by":"address","units_charged":1,"used_today":143,"day_limit":2000,"remaining_today":1857,"minute_limit":60,"resets_at":"2026-09-28T00:00:00Z"}}}