- Recently implemented GCP Stackdriver error reporting API for checked exceptions to our Node & Python services- Migrated the product’s CI/CD toolchain from Jenkins to Google Cloud Build with integration to SAST analysis tools- Implemented product's release management activities using GIT HUB Actions reusable workflows having 1 click semantic release production

- Lead and implemented a major change in the IRW release management process. This change had been facilitated through technology & toolsets, training sessions and heavy change in people's mindset- Migrated IRW codebase and project management tool from IBM Rational CC & CQ to GIT HUB Enterprise & Jira- Implementing pure CI/CD workflow was not possible without breaking the application architecture and we also did not want to embrace the lift and shift approach of moving to cloud just for the sake of it- We took a decision of creating a containerised CI pipeline that runs on Red Hat OCP4 on IKEA private cloud- To enforce agility and adoption of a frequent go to production model we created a git branching strategy that came very effective considering the old architecture model of the application and teams WoW- The process was conceptualised, planned and executed by me in heavy co-operation with a toolchain expert hired by IKEA as a consultant- I had created standalone scripts in Core Java & bash to automate few repetitive tasks that were identified during initial phase of the project and they were quite handy during the cutover activity- The project was implemented in Docker, Groovy and python as far as CI and auto deployments are concerned. The CI workflow has been driven through a GIT HUB App that facilitates the communication between Jenkins and GH as a bot user- To enforce more Quality Gates to the CI workflow I had added SAST scanning and static code analysis using Syopsys Coverity and Sonar Qube tools- Integrated GH & Jira communication in order to achieve traceability- Implemented pre-commit hooks as validation checks- Later on I created an automated CasC Jenkins set up that is driven through Helm3 chart from security and LCM standpoint

- Lead and successfully upgraded the technical platform of Classic IKEA e-Commerce portal primarily known as IRW(IKEA Retail Web). It was a challenging task where the idea was to migrate the application's highly customised ootb IBM WebSphere Commerce platform from v6 to v7 latest FP along with the Relational DB. An year later we carried a similar activity and migrated the platform to v8 with great level of confidence- I was also involved setting up an on premise data centre in Shanghai China as part of IKEA cyber compliance program for IRW. I was also involved in the application development of customer profile data handling change requests- Expertise in various software design patterns and enterprise frameworks for developing complex business changes- Expertise in quality and timely change request deliveries in various software lifecycle practices including agile

As a Java/J2EE consultant, my primary job was to write backend code for web applications. During this period I was also involved with post production supportDuring this tenure, for a couple of years, I involved myself stepping into a completely new technology landscape called PLM(Product Lifecycle Management) and worked with Enovia tool and explored the area of 3D experience tools like CATIA for GE Electric.

- In this role my primary day job was to interact with customer, understand requirements and provide a ball park estimation along with an impact analysis document. Once done, I used to get involved with the development of the business functionality using Core Java 1.6, J2EE Struts framework maintaining code quality features and adhering to Object Oriented design principles

In this project, my job was to implement a scheduled cron job that fetches data from Amadeus server via traditional web services and save it in the relational database with strict business validations. It was a short and overwhelming project where I introduced myself in a highly challenging work environment. This was the first time when I worked in a critical live travel domain project and got hands on with Linux, Core Java 1.5, Apache Struts 2.0.x & JAX-WS