Senior Backend Engineer

Senior Backend Engineer

We are looking for a Senior Backend Engineer to build backend features for payment flows and reduce technical debt across Java services. The mandatory requirements are 4+ years of backend engineering experience, production backend services at scale, Java with Kotlin and Python, and payments, fintech, or billing domain experience.

Job Information:

Date Opened 10/12/2026

City Indore

State/Province Madhya Pradesh

Country India

Zip/Postal Code 452001

Industry IT Services

Job Type Full time

Job Description:

We are looking for a Senior Backend Engineer to build backend features for payment flows and reduce technical debt across Java services. The mandatory requirements are 4+ years of backend engineering experience, production backend services at scale, Java with Kotlin and Python, and payments, fintech, or billing domain experience. RECRUITMENT PROCESS 1. Application — Share a few details about your experience and background. 2. Coding Challenge — If applicable, complete it in the coding language you are most comfortable with. 3. Video Interview — Record a short video introduction in English. 4. Technical Interview or Hiring Manager Interview — Discuss your experience and fit for the role. 5. Offer — If it's a match, you'll receive an offer. WHAT YOU'LL GAIN • Remote work — Work from where you feel most productive. • Local presence in India — Work in a structured and compliant environment aligned with Indian regulations. • Competitive compensation in INR — Receive compensation in INR, plus support for learning, education, and wellness. • Exciting projects — Work with modern technologies for global clients and fast-growing companies.

MUST HAVES • 4+ 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 PSPs. • Experience writing unit, integration, and contract tests. • Experience with Agile/Scrum and sprint-based delivery. • Ability to ramp up quickly on an existing codebase with minimal guidance. • Experience with Git-based version control and code reviews using GitLab. • Experience with GitLab CI/CD pipelines. • Experience with relational databases, particularly MySQL, and SQL. • Understanding of distributed systems, including message queues, asynchronous processing, and eventual consistency. • Experience using Jira for task and sprint tracking. • Production experience building end-to-end backend payment flows, including charges, refunds, disputes, and webhooks. • Experience refactoring or migrating legacy services with regression testing. • Experience resolving production incidents in payment or billing systems. • Experience designing internal APIs consumed by multiple downstream services. • Upper-intermediate English level.

NICE TO HAVES • Experience in a large enterprise engineering organization. • Experience with Spring Boot, Gradle, or service mesh. • Knowledge of PCI-DSS compliance, payment security, or financial data handling. • Experience with observability tooling such as Datadog. • Open-source contributions or a portfolio of shipped payment features.

WHAT YOU WILL DO • Implement new backend features for payment flows. • Reduce technical debt by refactoring legacy services, improving test coverage, and modernizing APIs, including deprecated API migrations. • Write clean, well-tested, production-ready code that meets engineering standards and passes CI/CD checks and peer review before merging to main. • Deliver multiple initiatives within agreed sprint cycles and participate in code reviews, design discussions, and sprint ceremonies with the Payments engineering team. • Collaborate with product managers, partner teams, and engineers to clarify requirements and deliver end-to-end solutions. • Document owned workstreams, including designs, API specifications, knowledge-transfer documents, and runbooks, to support long-term maintainability. • Ensure a smooth hand-off to the full-time engineering team at the end of the engagement.