Rahul Bishnoi

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

A static field will even pass.

Finally, it is not final.