I help developers across Mastercard to automate their workflows on a day-to-day basis. Automated workflows come in many shapes and sizes, but the main workflow my team and I focus on is automating application deployments. This is done through a combination of technologies, which include Salt, Jenkins, and custom-built Salt modules.

Ensuring that best practices are enforced and our code is constantly improved are passions of mine. Regular maintenance of the Salt modules and supporting code are critical to maintaining and improving operational health. We use Splunk to gather metrics and display dashboards about operational health and how customers are using Salt to deploy their applications.

Maintaining supporting infrastructure, like Jenkins, is also critical to our day-to-day operations. If Jenkins is not up and running, our users can't deploy. It is crucial that I work with various teams across Mastercard to ensure that our tools are being used appropriately, and that they are running efficiently.

Lastly, seeing through Mastercard's vision of "a world beyond cash" pertaining to my role is crucial. Although I am not directly involved in innovating product solutions to our external customers, I support all of the other verticals in Mastercard that enable its vision in a more direct manner. Making sure these teams have platform uptime, easy-to-follow processes, and robust deployment solutions is just as important to Mastercard's vision.

Worked on a suite of web applications that were directly used by customers in production.

- Used Angular (2.x - 6.x).
- Collaborated on feature development, including design.
- Collaborated on developing the backend API, written in Java.

Spun up a Jenkins server for team's immediate use before Jenkins was widespread across the corporation (in prod).

- Dedicated an RHEL VM internally exposed to the company, more than one team demanded it's usage.
- Managed LDAP roles and permissions.
- Performed usual Jenkins administrative tasks since I was the service owner.

Created a Git branching strategy that the team still uses today.

- Based on the Mainline Stable architecture.
- Included much research and documentation.

Ported an internal Java CLI tool to an AngularJS web app with a REST API that monitored server loads, and users could see server metrics for production servers. Although it never made it to production, it was a good learning experience.

- Designed the GUI from wireframes to implementation.
- Collaborated on the architecture.
- Used many AngularJS (1.x) modules to manage common tasks like routing, web services, and animations.