Work directly with product managers and business stakeholders — finance, tax, and accounts payable operations — to understand what they need and why, so that you build the right thing. You will hear the requirement first-hand rather than through a written hand-off, and you will be expected to push back when the ask and the outcome do not line up.
Ship incrementally. Large payment changes land safely through staged rollout and measurement, not through a single release.
Reduce operational load. Our best work turns a recurring manual intervention into a code fix or a self-healing mechanism, not another runbook step.
Leave the system better explained than you found it. What you build should be maintainable and extensible by an engineer who has never seen it, which means clear documentation and design choices that hold up without you in the room.
Raise the bar around you: code review as a teaching mechanism, mentoring engineers earlier in their careers, and getting new teammates productive on how our software is built, how it operates, and how it fits into the bigger picture.
Building with agentic AI
We are not experimenting with AI on the side — it is how we work. You will use AI agents across the development lifecycle: exploring unfamiliar systems, drafting and reviewing designs, generating and testing code, triaging production issues, and automating the operational work that used to consume a week of on-call. We expect engineers to be strong directors of these agents and rigorous verifiers of their output. The judgment stays with you: you are accountable for what ships, whether you typed it or an agent did. Agentic capabilities are increasingly part of the systems themselves — automating decisions and investigations that previously required a human in the loop — and you will have room to build them.
Why this team
Payments is one of the few places in software where the business logic is genuinely hard, the scale is enormous, and a mistake has an immediate real-world consequence — a vendor who does not get paid when they expected. If you want real ownership, global scope, and the freedom to build with the newest tools available rather than waiting for permission to try them, this is a good place to build a career.
3+ years of non-internship professional software development experience
2+ years of non-internship design or architecture (design patterns, reliability and scaling) of new and existing systems experience
1+ years of software development engineer or related occupational experience
1+ years of designing and developing large-scale, multi-tiered, multi-threaded, embedded or distributed software applications, tools, systems, and services using: C#, C++, Java, or Perl experience
1+ years of Object Oriented Design experience
Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, or a related field
Experience programming with at least one software programming language
3+ years of full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience
Bachelor's degree in computer science or equivalent
Experience contributing to the architecture and design (architecture, design patterns, reliability and scaling) of new and current systems
Experience debugging, profiling, and implementing best software engineering practices in large-scale systems
Experience with cloud computing or web services or related areas
Experience using AI-assisted development tools in academic or professional settings
Our inclusive culture empowers Amazonians to deliver the best results for our customers. If you have a disability and need a workplace accommodation or adjustment during the application and hiring process, including support for the interview or onboarding process, please visit https://amazon.jobs/content/en/how-we-hire/accommodations for more information. If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner.
null
