VIGNESH JAYANTHI MOORTHY

Driven and versatile developer with 4.11 years in the industry A Challenging Career in a reputed organization which will help to develop my abilities and skills in the field of Full stack. Aspiration to make my ideal choice from the sea of opportunities. The core of my objective is to emerge as a leading professional as well as accomplishing the organizational purpose. Seeking a position to utilize my skills and abilities that offers me professional growth. Seeking an environment that encourages continuous learning and creativity, providing exposure to new ideas that stimulate professional and personal growth

• AWS Solution Architect - Associate, AWS Certified Solutions Architect - Associate, Credly
• Java Lead and Developer

• Developed Spark-Scala scripts and services that leverages AWS Glue to process records that can be consumed by down-stream applications.
• Developed/Enhanced the utility services for Glue scripts as per business requirements.
• Developed the python Person resolution Libraries which is used to normalize, index the value from the cluster and update resolved based on the business rule.
• Developed Script to calculate the person stats with respective resolved count.
• Developed to script populate the Item Hash calculation in resolved value.
• Developed library called task support to fetching the secret for the cluster and smarty street license from AWS secret.
• Placing the different kinds of transactions using the Securities Front End.
• Checking the behavior of the Transaction in Secore as per the BAU.
• Validation of transaction in Securities Market Interface.
• Developed API in Service-1 to read a claim file from the S3 Bucket, fetch all the values from Sheet and mapping them to Stage using Java 11.
• Built the Rule Processor Service (Service-2), which processes the claim data with respect to rules applied by the user and updates the result into the Process claim data table happens using Java 11 and data are stored to Mysql DB using JPA.
• Built the Input Generation Service (Microservice-3), which fetched the data from the Rule Processor Service and generated the Kyriba input files and uploaded them to the file server.