OpenNash Jobs
Mastercard · Mexico City, Mexico

Senior Software Engineer

Mexico City, MexicoSenior individual contributorSoftware Engineering

Listed on Mastercard’s official careers site. Listed as of October 18, 2026. Check that it is still open and apply there.

Apply on Mastercard’s careers site →

Job description

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 Senior Software Engineer Overview

The Mastercard Developer Workbench, part of the MSBX (Mastercard Software Builder Experience) division, is evolving from a cost-allocation construct into a unified, developer-centric platform. With over 11,500 software engineers across the organization, Mastercard is investing in a dedicated product team to deliver an integrated, end-to-end developer experience. The Developer Workbench brings together five core MSBX products — BuildersHub, DevFlow, TestFlow, DevInsights, and Cloud DevEx — alongside cross-cutting tools including GitHub Copilot, Claude Code, and Docker Desktop.

This is a rare opportunity to shape the future of how engineers at one of the world's leading technology companies build, test, and ship software.

About the Role

  • Design, build, and maintain core components of the Developer Workbench platform across the full development lifecycle.
  • Contribute to the technical direction and roadmap of the Developer Workbench, helping evolve it from a chargeback mechanism into a cohesive, productized developer experience.
  • Drive the integration and enablement of software engineering tools across the development lifecycle, with a focus on usability and reliability.
  • Contribute to the governance of the "birthright and optional tooling" catalogue — supporting version lifecycle management, tool evaluations, and deprecation of redundant solutions.
  • Collaborate with product owners, platform teams, and engineering stakeholders to deliver workbench capabilities that align with organization-wide engineering priorities.
  • Build and improve developer enablement features — onboarding flows, self-service tooling, feedback integrations — to maximize the value of deployed tools across 11,500+ engineers.
  • Design and implement pre-provisioned onboarding environments that enable new hires to be productive within 30 minutes of day one.
  • Implement and advance AI-augmented development capabilities including agentic coding tools, code assistants, and automated quality pipelines.
  • Instrument the platform with meaningful metrics that surface developer productivity, satisfaction, and platform health.
  • Engage across engineering, security, and compliance teams to ensure tooling implementations meet Mastercard's security and regulatory requirements.
  • Actively participate in the Software Engineering Guild, sharing technical expertise and promoting standard engineering patterns across the organization.

All About You

  • Strong background in software engineering, ideally including work on platform engineering, developer tooling, or developer experience (DevEx) products.
  • Hands-on experience building and operating developer platforms or internal tooling at enterprise scale.
  • Deep familiarity with the modern developer tooling ecosystem, including: - AI coding assistants: GitHub Copilot, Claude Code, or similar

Containerization and desktop dev environments

  • Docker Desktop, Kubernetes, DevContainers - CI/CD and pipeline tooling: GitHub Actions, Jenkins, ArgoCD, or similar

Developer portals and inner-source platforms

  • Backstage, or similar
  • Experience working with AI-powered developer tools in a regulated enterprise environment, including an understanding of policy compliance, access controls, and responsible AI usage.
  • Strong understanding of developer experience (DevEx) principles and the ability to translate developer pain points into platform improvements.
  • Experience designing and delivering pre-provisioned, standardized development environments at scale.
  • Solid understanding of cloud platforms (AWS, Azure, GCP), including infrastructure automation and cloud-native development patterns.
  • Ability to contribute to tool adoption through instrumentation, metrics, and feedback mechanisms.
  • Strong written and verbal communication skills with the ability to collaborate effectively across engineering and cross-functional teams.
  • Familiarity with software development productivity metrics (e.g., DORA metrics, onboarding time, tool adoption rates) and using data to inform technical decisions.
  • Self-driven and comfortable operating in ambiguous, fast-evolving technology environments.
  • Strong understanding of Agile/Scrum methodologies and SDLC best practices from design through deployment.

Corporate Security Responsibility All activities involving access to Mastercard assets, information, and networks comes with an inherent risk to the organization and, therefore, it is expected that every person working for, or on behalf of, Mastercard is responsible for information security and must: Abide by Mastercard’s security policies and practices; Ensure the confidentiality and integrity of the information being accessed; Report any suspected information security violation or breach, and Complete all periodic mandatory security trainings in accordance with Mastercard’s guidelines.

More jobs at Mastercard

Lead Software Engineering

Mexico City, Mexico

Lead, DevOps Engineer

Mexico City, Mexico

Similar jobs at other companies

Staff Software Test Engineer/Software Test Lead

Thermo Fisher Scientific · Singapore

OpenNash lists jobs from employers’ own careers sites and does not handle applications. Dates come from the employer where stated; “first seen” and “last checked” are our own observations.