Benefits Modeler
The U.S. Total Rewards team approached us and described their idea of a benefits modeler, where employees could view their current year's benefits and model changes for their upcoming open enrollment. We immediately knew this was feasible as we were already sending employee benefit data from Workday into the Total Rewards Dashboard sitting within our HR Portal. My team worked with the vendor to surface this personalized data into the DOM as an XML structure which we established could be picked up, parsed, and leveraged for the benefits modeler.
This application sat within the HR Portal's SharePoint 2010 environment, where were able to override the platform's CSS and introduce custom modules and styling. Current year's plans, coverage levels, and payroll contributions were pulled from employee data. Subsequent year's data were hard-coded as XML in the base code. We also had the employee's work location at our disposal so we could show location-specific rates.
As employees traversed the experience, their selections were captured in a browser cookie not only for persistence, but to display their selections in a Benefits Checklist. This could be saved or printed out for reference once Open Enrollment began and it was time for employees to make their elections in Workday.
An MVC design pattern was used as well as Git and a Bitbucket repository for version control and merging changes between myself and the front-end developer.
Skills Used
- HTML
- CSS
- JavaScript
- jQuery
- XML
- XPath
- JSON
- RegEx
- Git
- Bitbucket
- Workday
- SharePoint
HR Portal
Mastercard's HR Portal was hosted by a 3rd party vendor as a SaaS SharePoint 2010 instance. After user research, we worked with the vendor to configure the platform to align to user needs and Mastercard branding standards as closely as possible.
We used SharePoint groups to personalize the experience by country, career level, individual contributor vs. people manager, and acquisition. This allowed us to only surface content & search results that were relevant to the employee. In addition, we used SharePoint lists to both reuse content and surface it onto global pages enabling stakeholders to send out a single global communication instead of separate emails for country-specific pages.
My team compensated for SharePoint 2010's tendency to introduce hidden characters and superfluous CSS into the content by hardcoding all content as HTML. For site-wide changes and customizations, we created custom CSS stylesheets to avoid vendor-related change orders or limitations of the technology.
In 2022, the vendor migrated all of their clients to the Evoq (DotNetNuke) content management system—which was an upgrade—and eliminated the need for HTML or CSS customizations.
Skills Used
- SharePoint 2010
- DotNetNuke (DNN)
- Workday
- HTML
- CSS
- JavaScript
- SQL operators
- Adobe Analytics
- Qualtrics
- Data analysis
Career Navigator
As sole front- and back-end developer, I had 4 months to design, build, test, and deploy this application. Working with the business owner and two Workday integration specialists, we output position data from Workday, leveraging XSLT, into separate XML files for each Job Function. I then used HTML, CSS, JavaScript, and jQuery to visualize this data in a meaningful format where employees could interact with it to explore career development opportunities.
I built the application to be low maintenance, as changes in Workday would automatically flow through and update the tool, including the navigation.
Skills Used
- HTML
- CSS
- JavaScript
- jQuery
- XML
- XPath
- XSLT