🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Joining Razer will place you on a global mission to revolutionize the way the world games. Razer is a place to do great work , offering you the opportunity to make an impact globally while working across a global team located across 5 continents. Razer is also a great place to work, providing you the unique, gamer-centric #LifeAtRazer experience that will put you in an accelerated growth, both personally and professionally. Job Responsibilities : The Senior Software Engineer, Payweb is responsible for designing, building, and operating full‑stack web‑based payment systems using a .NET backend and modern frontend technologies. This role focuses on correctness, reliability, and operational ownership of money‑moving workflows, including integration with external payment service providers and handling asynchronous and failure scenarios. This position supports revenue‑critical systems and requires strong engineering judgment, end‑to‑end ownership, and accountability. The role also leverages AI‑assisted development tools to improve productivity while maintaining strict standards for financial correctness and system safety. Key Responsibilities Design, implement, and maintain end‑to‑end payment flows using a .NET backend and web frontends, including checkout, top‑ups, subscriptions, refunds, and reversals Build and operate APIs and services using C# / .NET (e.g. ASP.NET Core) Develop and maintain frontend components using modern web frameworks (e.g. React or equivalent) Integrate and operate third‑party payment service provider (PSP) APIs Collaborate with backend, frontend, and platform engineers on payment state management, idempotency, and reconciliation Handle asynchronous workflows including webhooks, retries, and partial failures Ensure systems are observable through logging, metrics, and alerting Participate in on‑call rotations and lead investigation and resolution of payment‑related production incidents Review designs and implementations with a focus on failure handling, data integrity, security, and operational readiness Apply AI‑assisted development tools (e.g. code generation, testing, debugging, analysis) to improve productivity, while ensuring all money‑related logic is reviewed, validated, and production‑safe Contribute to continuous improvement of engineering standards, reliability practices, and development tooling Minimum Qualifications Bachelor’s degree in Computer Science, Engineering, or equivalent practical experience 5+ years of professional software engineering experience Strong experience building full‑stack web applications with .NET (C#) on the backend Experience developing modern web frontends (e.g. React, Angular, or similar frameworks) Hands‑on experience integrating payment systems or financial APIs Solid understanding of distributed systems concepts, including idempotency, retries, and eventual consistency Experience diagnosing and resolving production issues in revenue‑critical systems Experience using modern developer productivity tools, including AI‑assisted coding or analysis tools , in a professional environment Preferred Qualifications Experience working with payment service providers (e.g. Stripe, Adyen, Braintree, or local PSPs) Familiarity with wallets, balances, or ledger‑adjacent systems Exposure to chargebacks, refunds, disputes, or fraud workflows Experience operating high‑availability, revenue‑generating systems Knowledge of compliance or regulatory requirements related to payments (e.g. PCI) Experience with Southeast Asia payment methods (e.g. PayNow, GrabPay) Working Relationships Work closely with backend, frontend, platform engineering, product management, and customer support teams Interface with external payment providers during integrations and incident resolution Additional Information This role is responsible for systems where accuracy and reliability are critical Participation in after‑hours incident response may be required AI tools are used to augment development, but all production changes require human review and ownership Pre-Requisites : Razer is proud to be an Equal Opportunity Employer. We believe that diverse teams drive better ideas, better products, and a stronger culture. We are committed to providing an inclusive, respectful, and fair workplace for every employee across all the countries we operate in. We do not discriminate on the basis of race, ethnicity, colour, nationality, ancestry, religion, age, sex, sexual orientation, gender identity or expression, disability, marital status, or any other characteristic protected under local laws. Where needed, we provide reasonable accommodations - including for disability or religious practices - to ensure every team member can perform and contribute at their best. Are you game?
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.