Lead Software Engineer

Mastercard Mastercard · Fintech · New York, NY +1 · Engineering

Lead Software Engineer at Mastercard, a global payments and technology company focused on building a sustainable digital economy. The role involves owning complex problems, writing and enhancing code, defining procedures, driving prioritization, automating software delivery, and ensuring seamless integration across services. Responsibilities include introducing new technologies, providing guidance, conducting interviews, and leading by example. Requires strong coding skills in multiple languages, understanding of secure coding standards, operating systems, design patterns, and system architecture, with a focus on high availability and efficient delivery.

What you'd actually do

  1. Own complex problems having dependency across services and facilitate cross-functional team interactions to drive resolution
  2. Write code to build and enhance applications/services and promote code-reviews, code scanning, and other standard development practices to deliver high-quality artifacts to production.
  3. Define, design, and develop procedures and solutions at a service level to meet the business requirements/enhancements
  4. Drive prioritization decisions and trade-offs in working with product partners
  5. Identify opportunities and build roadmaps to enhance primary service/function

Skills

Required

  • C
  • C+
  • C#
  • Java
  • JavaScript
  • OWASP
  • CWE
  • SEI CERT
  • Spring Boot
  • Steeltoe
  • Angular
  • DXP
  • Windows
  • Linux
  • service-to-worker
  • MVC
  • API gateway
  • intercepting filter
  • dependency injection
  • lazy loading
  • gang of four
  • 99.95% availability

Nice to have

  • secure coding standards
  • open frameworks
  • operating systems internals
  • debugging and troubleshooting
  • core dumps
  • heap dumps
  • thread dumps
  • documentation
  • coaching
  • development practices
  • coding guidelines
  • branching
  • peer reviews
  • library use
  • logging
  • scanning rules
  • test-driven development
  • error handling
  • advanced design patterns
  • technical review of code
  • anti-patterns
  • continuous refactoring
  • technical debt
  • operational issues
  • stakeholder discussions
  • run experience
  • system architecture
  • platform and infrastructure capacity planning
  • database capacity
  • compute capacity
  • network capacity
  • storage capacity
  • dependency prioritization
  • delivery lead time
  • customer journeys
  • Mastercard good experience
  • Mean time to mitigate (MTTM)
  • deployment simplification
  • software and infrastructure snowflakes elimination
  • standardized platforms
  • ephemeral instances
  • automation
  • release workflows and pipelines orchestration
  • standardized pipelines

What the JD emphasized

  • write secure code in three or more languages
  • familiar with secure coding standards
  • high availability (99.95% as a starting point)