Interact is the bank associate application for opening any customer accounts. It’s architecture consists of javascript, jsp files and some java classes. SOAP calls are made to external angular2 services and external databases for certain customer data processing steps. Twelve or so teams collaborate on maintaining this project. A large portion of the members of each team work offshore in India.My responsibilities on this project include writing new javascript functionality for the user interface code, as well as modifying the java side of the project to send the correct data to the external systems. I also created and maintained some AutoSys jobs for batch updates. One of my other tasks was to transition the project to use Jenkins and Ansible for build and deployment s respectively.

Responsibilities:

• Involved in Designing, Developing, and Bug fixing of the system.
• Tracked defects and updated defect notes using ALM and Jira.
• Created new code for and added to existing account opening, safe deposit box, business, and IRA flows.
• Developed and maintained Autosys jobs.
• Used TortoiseSVNinitially, then GITfor source code version control
• Used JBoss servers to host the code.
• Deployed various code through the use of ubuild and udeploy
• Integrated the use of Jenkins,Sonar2, and Ansible for deployments
• Used Maven to buildcode

This project is focused around assisting Charles River Investment Management Solutions with managing investment data between systems. Messaging between systems is handled through Solace, and code has been created to process and transform the investment data at various points. For this project I created some message driven beans, associated services, Application Programming Interfaces, data access objects, unit tests, complex logic to handle and correct data mismatch between systems, and hibernate queries. I also refactored code to make it more readable, handled code build and deployments on unix machines, updating old code to use new systems, gave frequent feedback to business analysts on story designs, and worked hand-in-hand to fix defects with the quality assurance team. Recently became a leader developer for the ui team. focusing on Angular 7 and bootstrap 4 work.

Responsibilities:

• Involved in Designing, Developing, and Bug fixing of the system.
• Tracked defects and updated defect notes using ALM.
• Checked and modified test data in the Oracle databases through the use of SQL Developer
• Created and added to existing transaction, trade, account, and asset flows to add features and functionality to the existing codebase.
• Created Microservices with the help of REST which are consumed by our AutoSyssystem
• Used JPA in conjunction with Hibernate for querying the Oracle databases
• Used TortoiseSVNinitially, then GITfor source code version control
• Altereddatabase result sets using SQL
• Used JBossservers to host the code instead of container system like Docker and Solaceto facilitate message traffic.
• Edited and checked XML messages using Notepad++
• Responsible for adding functionality to seed incoming accounts with associated data.
• Added the complex logic to check processed taxlots between two systems to ensure that quantities on buys and sells match
• Deployed various code to the Unix machines
• Integrated the use of Jenkinsto test for test and code failure prior to deployment
• Used Mavenand AntHillProto buildcode
• Upgrading the existing ui projects to Angular 7 and Bootstrap 4using typescript and css.

The project involved adding new features toa web-based application, which would allow the users add more specifications to client data and have increased functionality. The original system was just built around LEO, which with its own UI enabled the onboarding of bank clients and tracking of associated risks and checks. When other businesses wish to do business with Bank of America, say in terms of a loan or mutual fund, the risk of the requested agreement must first be adequately assessed. This involves multiple stages of approval and a hierarchy of employees who are responsible for the onboarding. The new system includes both LEO and Lynx, my assignment being to the Lynx team. Lynx builds upon LEO and is integrated to work with it, including a new UI and new data viewing methods. One of the focuses for this part of the project has been to create a bridge between two systems that are responsible for adding new users to the system, so that they would not have to be added to both separately in order to access Lynx with proper onboarding permissions. The rest of the project has been focused on ensuring smooth transmission of data between Lynx and LEO databases and UI’s, since this was not yet complete.

Responsibilities:

• Involved in Designing, Developing, and Bug fixing of the application.
• Tracked defects and updated defect notes using ALM.
• Transferred updated project files to the Unix boxes using PSFTP and monitored logging with Putty
• Copied logs and whole applications using WinSCP
• Created Microservices with REST and integrated them where needed within our Mule flows
• Checked and modified test data in the Oracle databases through the use of Toad
• Performance enhancements using SQL Scripts.

The focus was on the server to database portion of communication involved with the order a customer submits to gain the services that Comcast provides. The specific goal was to switch over to using a NoSQL database, in this case we chose Couchbase, from a SQL based Oracle database. The actual services code was left untouched, so new adapter and connector code was created. The new code allowed for data previously stored in tables to be stored in JSON documents within Couchbase. The advantages of the new database is its self-replicating system and ability to quickly bring requested data in and out of memory for reads and writes.This project was completed successfully and a few months ahead of time.

Responsibilities:

• Created a large portion of the adapter code, which took data mean to be added to SQL code and instead used it to create objects to be sent to the database as JSON objects.
• Tracked defects and updated defect notes using ALM.
• Helped to create the Couchbasedatabase connector, which connected to the database, opened buckets, retrieved data from the buckets, and saved data to the buckets.
• Wrote views in the database and later implemented the reference docs which replaced the views. View querying was found to be not efficient enough. These primary-foreign key pair documents solved the issue.
• Carried out the creation of the TTL system for the JSON document objects, as well as the beans that were purely kept in memory.
• Spent many hours testing and fixing integration issues through the help of SoapUI and JUnit testing.
• Backup data sent to Oracle through Kafka
• Created builds through Hudson, to bedeployed on the WebLogicserver
• Handled version control through the use of Tortoise SVN
• Configured Spring to work with new classes and beans
• Paas usage enabled the storing of applications on the cloud
• Used generics for creating general methods, for the purpose of building view queries, creating JSON objects, and structuring a save to database method that worked for different object types.
• Common collections used included ArrayLists to store main bean types within another class object, as well as to store multiple beans retrieved from the record of one customer. Sets were used to store multipe variables in one field of a bean, such as addresses or account records of one customer.Hashmaps were used to keep track of key value pairs, to enable pushing backup data to Oracle through kafka.
• Multithreading implementation broke up the process of taking user submitted data and sending it through different validation processes, before going to the biller.

The project involved buildinga web-based application, which would allow the customer to access their bank account through Internet. Customers can access their accounts, such as credit, saving, loan, and mortgage, through the use of personalized ID’s and passwords. The application provides customer account, payment, and payment option information. Users can update their own profile as they see fit.

Responsibilities:

• Involved in Designing, Developing, Bug fixing, documenting and unit testing of the application.
• Worked on Production support for the new applications going live.
• Maintained existing applications by doing performance and interface enhancements.
• Performance enhancements using SQL Scripts.
• Tracked defects and updated defect notes using ALM.
• Worked on Service requests and change requests for various applications.
• Analyzed and developed the application using Struts2MVC Framework
• Used AJAX for client-to-server communication
• Used Hibernate and JDBC to access the database
• Wrote JSPs to render output to the browser
• Used SVN for source code version control
• Supported the interface supports in holiday season.
• Used Struts2 tag libraries and Controller to implement the workflow application
• Developed functions and store procedures using SQL and PL/SQL for the application
• Designed the business object with Hibernate ORM mapping and interfaced with the business mangers using Spring DAO.
• Coded web pages using HTML, and Struts2 tag libraries.
• Designed the JSP pages using Eclipse and integrated the Custom developed components for better look and feel.
• Used JBossin the development
• Used Maven for the project dependencies
• Created the action class Servlet and EJBs to initiate the application workflow
• Performed the unit testing using JUnit framework.
• Generics implementation allow for fewer methods, such as comparator methods, handling different UI request, and creating abstract classes.
• Worked withcollections, such as vectors to store related numerical data, arrays to organize request variables, and hashtables to store related account numbers together.
• Multithreadingsegmented the different processes involved with handling a request from the interface.