1. Project Title: Product and service management system for Cab Booking product. Technologies: .NET Core, SQL, SQL CLR, WCF Services, MVC, EF, Agile, FileZilla, JIRA, Confluence, Angular 9 Project Description: This application is specially designed for the transportation domain (Cab Booking), it will help end-users to book jobs (journey location and passenger details), it is available in terms of mobile applications and websites as well. For the backend team, they can book jobs directly through the call and email in our system (Web application), to achieve function complexity we use Signal-R to get Real-time updates related to Driver and Jobs. Drivers are those entities who perform all jobs which are being logged in the system, the driver will appear in the system by signing on to a mobile application and they can switch their status and parallelly job status also can update, system expect each driver for their location, for the continuous connection between driver application and server we implemented Windows application with Socket which will bridge between driver app and server and of course we provided WCF Services for services solution, we used jQuery and java scripts to simplify problems. Also, our system is continuously monitoring driver status and job status threw SQL jobs, and if any issues there then it will notify the admin / remove that driver from the system. Also, our system triggers push notifications to the users (Android and iOS) through windows services. Our system is trackable in terms of user activity on each and every insert/update our system logging entries to achieve we used SQL triggers, in fact, this user can pay the charges by their cards (stripe was integrated with the mobile app and web app) and also admin users can refund if required (stripe). We also use google API to track drivers on map/job track on the map or our application have own dispatch engine which will trigger a job to the nearest driver (there are many other criteria to trigger a job) to achieve this problem we created a CLR by which we can call google API and also we can check to optimize route SQL side itself. As it is a small-scale company, we need to take care of end-end things means we need to take care of requirement gathering by communicating with the client and estimating effort for the same, and delivering to the client.

Role and Responsibilities:

● Implemented core features that play significant roles in the project.

● Responsible for creating user stories in JIRA

● Involved in Requirement discussion with client and analysis.

● Worked as a mentor for the team, for example, helping them in requirement understanding, and pair programming in case of any issue, or a new feature was being developed. ● Building and Deploying application. 2. Project Title: Complete solution for the construction domain for a US-based firm. Technologies: C#.NET, EF, MVC, AngularJS, CICD, Agile, Confluence, ESB, Azure Functions Time Center: Source of this module is Daily Plan (for Data only) but moving further use can add additional hours, tasks, and employees from this module. Weekly Timesheet: It'll provide information about an employee like how many projects this employee is associated, same for equipment and task as well addition is: user can add hours against an employee without daily plan dependency, in this module all records will display, I mean to say whatever record inserted from the weekly timesheet and whatever record is inserted against an employee from daily play both will display here. Here we are using the ESB concept. Quantity Plan, Work Plan, and Daily Plan modules Quantity Plan: It'll maintain the quantity of equipment (this entity will come from the different modules) that are going to use on-site and provide a set of the quantity which will facilitate the project (project term used for an assignment). Work Plan: It'll help to design workflow on-site and users can create work orders as well. Daily Plan: This module majorly uses by field users and created by back-office operators because it'll manage the day-to-day routine and it gives an update of tasks, equipment, and employees who are associated with that assignment and it'll consume hours for that, employee get sign-in and out from this module only.

Role and Responsibilities:

● Implemented backend and frontend code.

● Enhance front-end functionality like charts and graphs.

● Provided training sessions about CICD and product walkthroughs to the team.

● I was involved in working with major issues and enhancements.

● Writing test cases using JUnit. 3. Project Title: Complete solution for the construction domain for a US-based firm. Technologies: .NET Core, MVC, Web API, SQL, REST, Agile, Angular 12, JQuery,TFS Description: This project is related to a company that is supplying Xerox machines for customers on-sell or lease purpose, for selling its straight forward process in that customer needs to provide their details like the address to deliver and building floor and timing to allow luggage inside the lift and all and then the customer can pay the amount by this way customer can check out. In another word customer can ask for equipment as well like paper try, ink, refill, and maintenance (as service) customer also can ask for rental of machines for that they need to sign a contract their machines are connected over the system (this application API) which will pass count of copies processed by machine because final billing will have figured out based on the number of copies, in other word based on usage customer can ask package. The payment gate is also integrated and autopay functionality is also there also we can hold payment for the same.

Role and Responsibilities:

● Developed project architecture.

● Developed API using rest.

● Requirement understanding and modeling

● Interaction with sales team for product improvement

● Providing product demos to the customer.

● As a Scrum master responsible to conduct daily scrum.

● Writing user stories based on customers’ requirements.