Rahul Bishnoi

So I have been working with Cost 24 for about 3 years now, and I have total experience of about 5 years as a back-end developer. My skills basically include Java, Spring Boot, developing microservices, RabbitMQ, using messages like RabbitMQ, and all these things. So, at Cost 24, I have worked with the Australian team, the Australian default team majorly, where I have also been promoted as a team lead. So our goal was to be part of the refurb team, which would essentially control the acquiring of the vehicle, refurbishment of the vehicle, and then making them perfect for them to be landed on our web portal. So, efficiently, I played an important role in reducing the default cost, as more vehicles were referred per month. The same number of mechanics were able to refer more vehicles by the kind of app and the kind of features they could develop. Also, we started recording the progress and the work that a particular mechanic was doing in the workshop, and we were showing the view of it to the managers on the screen, thus reducing manual intervention. So, by this, we reduced the number of managers required for x numbers of mechanics because now they didn't have to go manually and check. They could just at the end of the day, come to our portal, see the view of the sheet, and they would get an idea of what kind of work each mechanic had done. And similarly, we also created a vehicle pipeline. The pipeline was a kind of a thing that would tell us which vehicle was at worst at a given time. Again, they didn't have to check manually. And, also, this reduced the calls that were lost. So, earlier, there were a few calls that would get lost because we didn't have any proper system.

A static field will even pass static analysis.

Finally, it is not final yet.