Sr. Principal Software Engineer

Our Purpose

We work to connect and power an inclusive, digital economy that benefits everyone, everywhere by making transactions safe, simple, smart and accessible. Using secure data and networks, partnerships and passion, our innovations and solutions help individuals, financial institutions, governments and businesses realize their greatest potential. Our decency quotient, or DQ, drives our culture and everything we do inside and outside of our company. We cultivate a culture of inclusion for all employees that respects their individual strengths, views, and experiences. We believe that our differences enable us to be a better team – one that makes better decisions, drives innovation and delivers better business results.

Title and Summary

Sr. Principal Software Engineer

Who is Mastercard?

Mastercard is a global technology company in the payments industry. We work to connect and power an inclusive, digital economy that benefits everyone, everywhere by making transactions safe, simple, smart and accessible. Using secure data and networks, partnerships and passion, our innovations and solutions help individuals, financial institutions, governments, and businesses realize their greatest potential.

Our decency quotient, or DQ, drives our culture and everything we do inside and outside of our company. With connections across more than 210 countries and territories, we are building a sustainable world that unlocks priceless possibilities for all.

Overview:

The Transfer Solutions team was created to establish Mastercard as the frontrunner in the fast-evolving real-time payments space, and to position Mastercard to be able to incubate the development of new payment flows. The team is responsible for designing, building, and operating the technology that powers Mastercard’s next generation payment applications – Domestic, Cross Border and Bill Payments.

Mastercard seeks to define a world beyond cash. To accelerate this mission, we are committed to building & scaling products & applications that transform payments of any type. Real time payment technology is central to this strategy.

The Role:

What’s it all about and what we expect you to do day to day?

· At least 50% individual contributor with technical team leadership who is recognized as a departmental authority and technical expert within a discipline, and drives innovation and organizational growth through their contributions.

· Spend their time in IDEs writing non-feature code; are hands all the time and collaborate by writing interfaces, tests (unit or acceptance) and architecture fitness functions, outside of meeting rooms. Tools like JDepend, ArchUnit, ADRs and NetArchTest make them feel at home.

· Implement, monitor, and maintain compliance and security concerns in CI/CD pipelines to bring life to the principle of “Code is Design and Design is Code”.

· Domain driven design in their game. They code to enforce the contextual mappings and aggregates for each bounded context. They drive implementation of consumer driven contracts to allow for evolution and learning of the domain model with hyper speed while meeting our promises to other teams internally and customers alike.

· Polyglot engineering gurus. They bring cutting edge engineering practices to life in multiple evolving frameworks – Feature flags, fitness functions and whatever is required to reduce the cost and increase the lifecycle value of next feature delivered by engineering teams.

· Love for declarative paradigm and functional programming. No one can stop them in paying off technical debt and refactoring the code for better SDLC, performance and availability.

· Work on complex enterprise-wide initiatives spanning multiple services/programs and drives resolution

· Work with business/product owners to architect and deliver on new services to introduce new products and bundles

· Participate and contribute to team’s agile process and decisions. Understand and contribute to Prioritization. Drive prioritization decisions and trade-offs in working with product partners

· Drive the architectural design, including dependent services, service interactions, and policies

· Take ownership to improve the customer experience of an entire set of services/applications sold as products or bundled services

· Simplify and improve the cost/benefit of a function/service/architecture strategy

· Apply judgment and experience to balance trade-offs between competing interests

· Venture beyond comfort zone to take on assignments across different areas of Software Engineering

· Take on organization-wide and public speaking engag