Pranoy Bhattacharya

• The project follows strict quality compliance for all production releases. Coordinate with project managers, test managers to receive inputs regarding various stages of a planned project release.
• Maintain release tracker in an intranet site or a shared folder for the team to understand the current status, speedup their activities.
• Implement and utilize release management tools that allow teams to plan, manage and control the release schedule and track the status of each release.
• Work closely with QA and project teams to identify, create and/or implement processes to efficiently manage the release and testing of various applications.
• Identify environments, discuss with the environment managers and prepare a plan for each release.
• Reported release health directly to the Executive Committee through weekly status meetings Scheduled and facilitate all Release Management Meetings.
• Collaborate with development teams in the definition and breakdown of release content and review the work of the team.
• Implement and manage the release process globally in all project teams.
• Driving prod Go-Live Releases.
• Responsible for Configuration management of all Non-Production, Dev Environments.
• Involved in daily builds and deployment, Release Management process.
• Validate Test Evaluation reports according to the automated tests and scenarios.
• To Implement DevOps Practices such as Infrastructure as a code, continuous integration and continuous deployment.
• Drive weekly review and analysis of issues and changes going into Production.
• Installation, Configuration, maintenance, troubleshooting, and administration of various tools like BitBucket, Openshift, GitHub.
• Adhere to SDLC process.
• Checking of the Final payload going for deployment which includes checking and validating of code branches, database scripts and configuration management (toggles, memory allocation, load balancing).
• Improving the Release process by automation to reduce human effort utilizing Jenkins.
• Verify logs for the applications after deployment and monitor pods health status.
• Ensure code standards by using Veracode and waltz scanning and following up with Development teams in case of any discrepancies.
• Weekly/Monthly reporting of Releases and issues for the whole application.

Client : BNYM

• Analyze issues reported by Client.
• Monitor in built tools to proactively stop any production issue.
• Understand the system and providing fixes and contributing towards improving the production support.
• Work with Development team to understand the issues.
• Working on existing/new shell scripts to do housekeeping stuffs – mainly archival, removal and clean-ups of folders based on business logics.
• Working on modifying or sql used for business reports for trading apps; we do modify reports based on user requirements such as including or removing of columns, adding business criteria’s, etc.
• Monitoring of daily batch reports and work in case of any failures.
• Deployment of Applications using AppEngine.
• Work with the development team for deploying applications and perform data and connectivity testing.
• Send daily, weekly and monthly reports to the clients via automated process.
• Improving the time for the execution of reports by working with development team.
• It follows strict quality compliance for all production releases and BAU activities.
• Being a part of this project I was responsible for the daily BAU activities which included monitoring of daily reports and extracts running for different Business Line.
• I was responsible for the monitoring of accounts being loaded in the database and then run the scheduled extracts to send the clients the daily reports.
• I have worked on modifying existing scripts as per the requirement.
• I was the first inline to take care of any issues coming from any user/client and to drive it to the responsible team for resolving the issue.
• I was a part of the production releases for every month and I was responsible for the technology validations for the business lines available.
• I have worked in AppEngine and have been a part of deployment and routing of the applications via the tool.
• I have documented the issues for future purpose in sharepoint with the route cause analysis.
• I have worked on Lower environment as well (UAT,SIT,PERF).
• I have created reports and extracts in lower environments for testing and then getting them deployed in production.

Client : JP Morgan Chase

• Support non-production batches, resolving L2 and L3 level of issues.
• Analyzing issue, creating change request and work on change request assigned.
• Worked on different Build Developments like: Procedure tuning, Converting minor Sybase procedure to Informatica workflows, Altering CA and Autosys Job changes as per the business logics.
• Created JIL and updated existing jobs, calendars, resources, variables, etc in Autosys.
• Creating XML objects for ETL logics as per the business logic.
• It follows strict quality compliance for all production releases.
• The codes are deployed as packages to non prod environment for regression testing through rigorous batch execution and data validations by business users.
• The non-prod environments are classified as SIT, UAT, Integration, Test Lab, Performance test ground, etc.
• The plays a very important role of managing and monitoring the various test beds including data staging, batch execution and downstream deliveries.
• The role currently played by the team is extremely important in ensuring smooth production deployments.
• The success of this unit can be measured by comparing the reduction in the number of post-production issues from previous years.

Client : Oxford University Press

• Worked as Windows/Exchange Admin. Performing configuration changes in Exchange 2010 server to improve performance was also a part of my job.
• Worked on Database creation, and updated configurations through EMC.
• Performed changes in AD for successfully applying Group Policy.
• Performed Windows Patching to avoid threats.
• Investigated on issues related to Active Roles mainly when there is issue in creation of New User Mailbox accounts/ when the user account is deactivated and needs to be activated again.
• Also took active participation in Knowledge Transfer among team members with the help of SOP creation.
• Irrespective of these, took active participation in working on various daily incidents raised by caller for issues like shared drive access or permission issues.
• Distributed incidents among team members so that no one is over-burdened.
• Coordination among other team were also made, in order to get the right resolution for certain issues.