Remote
#138512 - Backend Software Engineer - Payments
About this role
We are seeking a backend software engineer for a remote contract engagement building and operating scalable, revenue-critical payment infrastructure. You will deliver payment features, reduce technical debt, and modernize services while collaborating with engineers, product managers, and partner teams. Enterprise experience strongly preferred. Key Responsibilities - Implement production backend features for payment flows.
- Refactor legacy services, improve test coverage, and modernize APIs, including migrations from deprecated APIs. - Deliver clean, well-tested, production-ready code with passing CI/CD pipelines and peer-review approval. - Deliver initiatives within agreed sprint cycles and participate in code reviews, design discussions, and sprint ceremonies. - Clarify requirements with product managers and partner teams and deliver end-to-end solutions.
- Produce designs, API specifications, knowledge-transfer documentation, and runbooks for owned workstreams. - Support maintainability and a smooth handoff to the engineering team at the conclusion of the engagement. Must-Have Skills - 3+ years of backend software engineering experience. - Experience building and operating production backend services at scale. - Strong proficiency in Java as the primary programming language, with Kotlin and Python as complementary skills.
- Hands-on experience with RESTful and GraphQL APIs, microservices, and event-driven systems. - Payments, fintech, or billing domain experience, including gateways, processors, or payment service providers. - Experience writing unit, integration, and contract tests. - Agile/Scrum experience with sprint-based delivery. - Ability to ramp quickly on an existing codebase with minimal guidance. - Git-based version control and code review using GitLab.
- Hands-on experience with GitLab CI/CD pipelines. - Relational database experience with MySQL and SQL. - Distributed systems experience with message queues, asynchronous processing, and eventual consistency. - Jira experience for task and sprint tracking. - Experience building end-to-end backend payment flows in production, including charges, refunds, disputes, and webhooks. - Legacy service refactoring or migration experience with regression testing.