Principal Software Engineer - Java Architect, Microservices, Cloud, Springboot
Mastercard
- Location
- Pune, India
- Work model
- On-Site
- Level
- Principal
- Posted
- 10h ago
Skills
About this role
Our Purpose Mastercard powers economies and empowers people in 200+ countries and territories worldwide. Together with our customers, we’re helping build a sustainable economy where everyone can prosper. We support a wide range of digital payments choices, making transactions secure, simple, smart and accessible. Our technology and innovation, partnerships and networks combine to deliver a unique set of products and services that help people, businesses and governments realize their greatest potential. Title and Summary Principal Software Engineer - Java Architect, Microservices, Cloud, Springboot Principal Software Engineer, Real time Payments (RTP) Overview The Real time Payments (RTP) program is driving the global shift toward instant, account to account payments, enabling secure, low latency, and highly resilient payment services across multiple live markets worldwide. RTP platforms operate as mission critical financial infrastructure, supporting high transaction volumes, strict regulatory expectations, and near zero downtime requirements. The program spans multiple products and shared services, deployed across diverse market and customer environments, while adhering to Mastercard’s enterprise architecture, security, and operational standards. Engineering within RTP is focused not only on feature delivery, but on building scalable, resilient platforms that can evolve safely over time—through strong architecture, disciplined engineering practices, and a relentless focus on non functional excellence.
Role
We are seeking a Principal Software Engineer to provide hands on technical execution and leadership for one or more RTP products and platform capabilities across multiple markets. This is a senior individual contributor role for a deeply experienced engineer who: • Owns the design and implementation of complex services or subsystems • Stays close to the code on complex and high risk areas • Is deeply hands‑on and leads by technical excellence • Contributes meaningfully to architecture and product design aspects • Owns key implementation decisions including all non-functional aspects across performance, scalability, reliability, security, and observability The role combines strong technical depth with engineering leadership with end‑to‑end ownership for delivery quality, correctness, and maintainability in their area of responsibility.
Key Responsibilities
The role spans five core dimensions, with ownership across end to end technical outcomes. 1. Design & Technical Execution • Own the architecture and detailed design for one or more RTP products or platform capabilities across markets. • Define and enforce reference architectures, design patterns, and engineering standards (e.g., microservices, event driven architecture, domain driven design). • Design, build, and maintain high‑quality software components and services for RTP products. • Lead and participate in technical design reviews, ensuring alignment with RTP and enterprise architecture principles. • Make clear, well reasoned technology and design trade offs, balancing delivery speed, risk, and long term maintainability. • Own end‑to‑end delivery of complex features or subsystems, from design through production. • Translate functional and non‑functional requirements into robust technical implementations. • Ensure solutions adhere to RTP architecture standards and engineering best practices. 2. Hands‑on Engineering & Code Quality • Remain hands on for critical components, complex problem areas, prototypes, and reference implementations. • Lead by example in code quality, testing discipline, and maintainable design. • Perform and participate in code reviews, raising the bar for engineering quality. • Drive high quality implementations for low latency, high throughput, distributed systems. • Support teams in solving deep technical problems across application, messaging, data, and platform layers. 3. Non