Abhishek Kumar

Hi, I am a software engineer with a working experience of 9 years. I am accustomed to working in dynamic, goal-oriented team environments.My strengths are excellent communication and interpersonal skills with proven abilities in resolving complex software issues. I am recognized for reliability, teamwork, persistence, and strong work ethics. I believe in sharing what I learn and learning from others. Results-driven Software Engineer with a strong background in developing and maintaining complex software solutions. Delivered effective communication and collaboration within diverse teams, enhancing project outcomes. Cultivated a culture of knowledge sharing, fostering continuous improvement and innovation.

Workforce MDM

Workforce MDM is a central repository for employee information which can be accessible by all the consumers within organization. This includes various maintaining various endpoints. We support a lot of consumers through our APIs. workforce outbound data is another app that we support. Presently, We are calling multiple vendors for different purposes for adding licensed data and carrier appointments or for populating different employee attribute fields. We are maintaining this app just for making third party vendor calls or internal calls.

QUERY API

Workforce Team needed to come up with an API allowing their consumers to retrieve data as response based on their allowed set of attributes referred as consumer projections. Addition of this api would attract more consumers who can retrieve data based on multiple fields inclusive of existing consumers who relied on just two attributes before this api was created. I worked on the implementation part of this APi and came up with multiple design solutions

Success Factors to Workday Migration

For maintaining employee data we were receiving event updates from source system named Success Factors, now Success Factors has been replaced by Workday as our data Source. We had to update our code base and calls accordingly.

REST API Migration

In order to migrate away from existing MAUI view(mainframe data source) to modernized REST API. We worked on the migration of MAUI views to JAVA direct services which led to save a lot of MIPs for Fidelity. As a part of this process we were consuming the available REST services and replacing the existing SOAP service with the new REST one. It included request response mapping from all the stubs generated through yaml which were later filtered based on the number of attributes which were going in as a part of request in the MAUI call and the same was with the response.

• Cricket(playing/watching/Reading)
• Video Games(FIFA)
• Reading(Novels)
• webseries