Raju Paul

As part of this I was involved in automating workflows for the accounting project using Azure and UAC and Spring components. Have worked on Access management and business user provisioning for the Applications. Other task includes setting up the Azure pipeline for new server environments, automations required such as promoting UAC tasks, setting up integrations with external systems such as Active directory and ADFS for single signing, SSL key update for applications, server upgrade and patching of Linux machines, creating reusable components using shell scripting, carrying out change request and resolving incidents. As part of the being tech lead, I was also responsible for providing design solutions for integrations required for different business use cases.

• Automating workflows for the accounting project using Azure and UAC and Spring components
• Worked on Access management and business user provisioning for the Applications using Spring boot.
• Setting up the Azure pipeline for new server environments, automations required such as promoting UAC tasks, setting up integrations with external systems such as Active directory and ADFS for single signing, SSL key update for applications, server upgrade and patching of Linux machines, creating reusable components using shell scripting, carrying out change request and resolving incidents
• Design solutions for integrations required for different business use cases.

As part of the content services was involved in designing and creating a Custom component that will act as a gateway to a range of services that will help the client applications to meet their archiving requirements from creating content with metadata to updating and retrieving the content. The component has been built with and integrated ECS S3 store and is also programmed to interact with some target repositories. The component also integrated with a custom IAM to enforce user authorization.

• Designing and creating a Custom component that acts as a gateway to a range of services for archiving requirements
• Built and integrated ECS S3 store and programmed to interact with target repositories
• Integrated with custom IAM for user authorization
• Design and develop Application based on ING custom API SDK built on Spring Boot
• Work complying with ING TPA and registering the services designed on API Market place for other clients to consume
• Responsible for creating Spring Controllers, Service Components, Web Services and UI Integration of the developed services while authorizing it using JWT
• Configuring the components for synchronization of data from various external systems using Apache Kafka
• Implement transaction tracing tool for tracing the request
• Integrate the custom Archiving solution with Security Event Monitoring
• Implement Apache Kafka integration
• Quality compliance using Sonar and Fortify
• Custom IAM Access Control design and implement integration
• Responsible for UI integration of the archiving component
• Setting access policies for AWS s3 using AWSSDK.

As part of this I was involved in automating workflows for the accounting project using Azure and UAC and Spring components. Have worked on Access management and business user provisioning for the Applications. Other task includes setting up the Azure pipeline for new server environments, automations required such as promoting UAC tasks, setting up integrations with external systems such as Active directory and ADFS for single signing, SSL key update for applications, server upgrade and patching of Linux machines, creating reusable components using shell scripting, carrying out change request and resolving incidents. As part of the being tech lead, I was also responsible for providing design solutions for integrations required for different business use cases. The project is for replacing the existing service layer CARS with a new system. The new system exposes web services that then interacts with data repositories for providing the data. The new system replacing the CARS is a COTS product that has been customized for Ally. Custom implementation is also built as an interface between the actual client application and the COTS system. The custom component includes a gateway layer and microservices layer. The project also included designing and implementing custom client provisioning system for the Gateway.

As an Architect I was leading a team of Tech Leads and Developers and was coming up with optimized innovative solutions for various technical use cases. I was responsible for coming up with the mechanism for the entire stack of applications that was being developed to have their properties loaded from the database rather than from the file system and enable dynamic Spring context loading once the properties are changed in the database. I was also responsible for creating event flow model to process various offline work flow required for some of the business use cases. I was also tasked with the creation of a comprehensive application with screens that show the server statuses, database statuses, application deployment statuses, application deployment version numbers and application sanity test responses after the deployment. The comprehensive app also had a custom client provisioning system for the Gateway.

• Replacing the existing service layer CARS with a new system
• Exposing web services that interact with data repositories for providing the data
• Custom implementation as an interface between the client application and the COTS system
• Design and develop Application based on Spring Framework, Spring security, Spring Boot, Spring MVC, Hibernate and Micro Services for Ally Commercial Customer Management project
• Developed Spring Controllers, Service Components, DAOs, Web Services and UI Integration for developing presentation layer of the application
• Experience with data persistency using Hibernate and Spring Framework
• Implement Restful Web Services using JAX-RS API
• Designing and implementing client provisioning system using custom API
• Completing the migration of the client application on the WebLogic servers to Jboss
• Designing and Implementing the solution for creating a custom component with capabilities for stopping the cross site scripting and other security problems
• Automated DML creation for persisting the application properties in the database and reading it from the database on application load providing the capability to add new property values and make it available in the application context without deployment
• Configuring the components for synchronization of data from various external systems.

The Ally Dealer Portal Services Platform is currently using the services and insurance products provided GMPP (General Motors Payment Plan) whose contract was set to be over by 2015. The aim of this project is to come up with online solution which features Ally branded insurance products along third party insurance products various related services which will successfully replace the existing vehicle servicing products.

As an Tech Lead/Architect I was responsible for holding regular interactions with relevant business stake holder and client architects. I was tasked with the understanding the requirements relating to business and preparing the requirement design document, conducting reviews and getting the required sign off on project artifacts such as design documents. The project had a unique requirement of provisioning users with roles and fine grained access where by means of which the users will be having access to various business capabilities on the application screen. I have led the design and development of this provisioning mechanism using spring security.

• Replacing the existing products for vehicle servicing products
• Understanding the requirements relating to business and preparing the requirement document
• Preparing the analysis document and estimation
• Preparing the System design document
• Leading the team in implementing the requirements as per the design document and the use case
• Running vulnerability tool SONAR and coming up with the analysis and fix for vulnerabilities that has been found
• Running Security vulnerability analysis tool VERACODE and coming up with the analysis and fix for vulnerabilities that has been found
• Verification of development teams Adherence to the coding standard and PMD
• Formulating the code promotion strategy
• Implementation of the client specific service authentication framework
• Conducting session to discuss with the team on the various problems faced by the development team and formulating the solutions
• Coming up with the estimate and Design for the change request and guiding the team on implementing the changes on top of the existing implementation without any conflict
• Providing the all the details for the project audit and participating in the quality audit sessions for the project to give valuable insights on the project
• Implemented Restful Web Services that extends the JAX-RS API
• Used Sessions extensively to track client sessions
• Worked on the JMS to publish-subscribe the messages to interact with Apache ActiveMQ service Queues
• Worked with Oracle SQL Developer as IDE and executed queries
• Involved in writing the PL/SQL procedures in Oracle DB.

Document Custody Division (DCD) is a unit within Ally that looks at the Mortgage division of Ally. They are Custodians of the Mortgage related documents for the bank. The documents are maintained in digital format. The unit also provides solutions for the online sales and other related transactions of the Mortgage. The project was about upgrading the existing EmBTrust version to the latest version.

As an Tech Lead I was responsible for interacting with relavent business application managers and client architects to find the required front end application changes essential for the system upgrade. During this system upgrade the application was also expected to deployed and running from a new data center. I was responsible to come up with documents that enable admins to successfully deploy and configure the application on the new datacentre. I have come up with other project specific artifacts such as Runbook, Playbook and DRP (Disaster recovery Program) for the application.

• Upgrading the existing MBMS framework to the latest EmBTRUST framework
• Creating user interfaces using JSP, Servlets, HTML and JavaScript
• Gathering all the required details for Run Book
• Formulating the Play Book
• Coming up with the ADRP (Application Disaster Recovery Plan) and SMOG (System Maintenance and Operations Guide)
• Conducting the KT session for Sustain Team for the application and the Handover of all the required documents for successful Sustain KT sign off
• Creating the documents related to the various environments (production and other model environments) for EmBTRUST and coming up with the Migration Architecture Design Document for the server migration which was done as a part of the Dodge project.

The release was aimed at migrating the existing portal server to the new portal server which is a more advanced. As a part of the change the IAM (Access Manager) was also getting updated from Oblix to Covisint IAM. As an Tech Lead I was tasked with coming up with the impact assessment to the business use cases if any and come up with optimum solutions for corrective changes. I was also leading a team to implement the changes required for the access management and for formulating frame work for a new Single Sign On mechanism (SSO) between the portal and the various applications which are hosted in the portal. Running vulnerability analysis tool SONAR and coming up with the analysis and fix for vulnerabilities that has been found were some of the other responsibilities.

• Upgrading the IAM (Access Manager) from Oblix to Covisint IAM
• Understanding the requirements relating to business and preparing a high level requirement document
• Preparing the impact analysis for the changes for the IAM and the applications that are currently hosted in the portal
• Formulating frame work for a new Single Sign On mechanism (SSO) between the portal and the various applications which are hosted in the portal.

The release was aimed at enhanced user experience. As a part of the release the internal Ally site was added with some features and some tools available in the dealer side. Also a dealer portal which only supported single window at a point of time is now upgraded to the multi tab and multi window there by allowing the user to open
multiple applications from the portal in different windows and tabs and using them simultaneously. Managing the session throughout the multiple windows and tabs was also in scope for the release.
Along with leading a team of developers I was also responsible for holding relevant discussions with the business stake holders on the requirements and then coming up with an design for the implementation for various business use cases. I was also responsible for coding and doing demo of a model screen with session management business capability to the client.

• Enhancing the dealer portal with rich facilities thereby enhancing the user experience
• Integrating multiple features like chat and dynamic contacts to the dealer and the branch portals
• Managing the session throughout the multiple windows and tabs.

The release was aimed at enhanced user experience. As a part of the release the internal Ally site was added
with some features and some tools available in the dealer side. Also a dealer portal which only supported single
window at a point of time is now upgraded to the multi tab and multi window there by allowing the user to open
multiple applications from the portal in different windows and tabs and using them simultaneously. Managing the
session throughout the multiple windows and tabs was also in scope for the release.
Along with leading a team of developers I was also responsible for holding relevant discussions with the business stake holders on the requirements and then coming up with an design for the implementation for various business use cases.

• Enhancing user experience
• Adding features and tools to the internal Ally site
• Upgrading the dealer portal to support multi-tab and multi-window functionality
• Managing the user session throughout the multiple windows and tabs.

This is a business capability that provides dealer users the ability to capture and input vehicle damage and excess wear details within an Ally application. All inspection data and pertinent customer data that is captured by the dealer entry will be forwarded to the back end system for wear calculations and document packet processing.
As a Tech Lead I was responsible for requirement gathering, design and development for the application. I was involved in developing application using Spring MVC architecture, leading the team in implementing the requirements as per the design document and the use case, coming up with a stored procedure to insert the vehicle damage details to the database tables and integrating that with the application. I was also responsible for code review, running the code review tools such as SONAR and VERACODE and resolving the security vulnerabilities found in the code.

• Enhancement on AAVR application to introduce Vehicle Inspection flow
• Understanding the requirements relating to business and preparing the high level requirement document
• Preparing the analysis document and estimation
• Implementing the requirements as per the design document and the use case
• Running vulnerability tool SONAR and coming up with the analysis and fix for vulnerabilities that has been found
• Running Security vulnerability analysis tool VERACODE and coming up with the analysis and fix for vulnerabilities that has been found.

The project was about Billing and customer management portal, containing more automation and validation and
allowing increased flexibility in configuration, making more streamlined product and an improved end user
experience. The architecture consists of the following layers. Application layer, the ESB layer, services layer and
the underlying DB. The application is completely developed using spring MVC and WebSphere portal technology.
As a Tech Lead I was responsible for requirement gathering, design and development for the application.
Developed application using Spring MVC architecture. I was also responsible for application integration with
service components, running the code review tools such as SONAR

• Enhancement on AAVR application to introduce Vehicle Inspection flow
• Understanding the requirements relating to business and preparing the high level requirement document
• Preparing the analysis document and estimation
• Implementing the requirements as per the design document and the use case
• Running vulnerability tool SONAR and coming up with the analysis and fix for vulnerabilities that has been found
• Running Security vulnerability analysis tool VERACODE and coming up with the analysis and fix for vulnerabilities that has been found.

Elsevier Xpharm was a document work flow management tool. The main goal of the project undertaken was to host the application on a latest version of server OC4J server (Oracle Container for Java). All the dependencies had to be analyzed and changes had to be made in code level, UI level and the database level so that the application functionalities work unaffected in the new server.
As a Lead developer I was responsible for requirement gathering, design and development for the application. Developed build files for application using Ant script. I was also responsible for doing required code changes for a use case requirement which mandated some work flow changes.

• Hosting the application on a latest version of server OC4J
• Analyzing dependencies and making changes in code, UI, and database to ensure the application functionalities work unaffected in the new server.

The CWS is the cooperate web site for Elsevier. The website makes use of a third party search engine called Fast. Fast is an advanced search engine. The CWS application uses the Fast API’s to make the service calls on search request. Upgrading the version of Fast API used by an enterprise application to the higher version by replacing all the API functionalities used by the application from the existing version of the Fast API with the similar ones in latest version.

• Upgrading the version of Fast API used by an enterprise application to the higher version
• Replacing all the functionalities used by the application from the existing version of the Fast API with the similar ones in the latest version.