Aug 2020 – Aug 2021 · 1 yr · Hyderabad, Telangana, India

• Working with LiDAR visualisation, semantic segmentation for 2d and 3d, image and point clouds understanding and sensor fusion related to self-driving cars.
• Created multi-sensor data labelling tools to accelerate computer vision training for autonomous vehicles, robotics and more.

Jul 2019 – Aug 2020 · 1 yr 1 mo · Greater Hyderabad Area

Nov 2017 – Jul 2019 · 1 yr 8 mos · Noida, Uttar Pradesh, India

• Significantly reduce the execution time - parallel execution using a device farm.
• I worked on enabling parallelization in Acrobat Android automation. - Older Acrobat Android automation takes ~24 hrs for completion as it runs on a single device in serial order. I took up the task of enabling parallelization in Acrobat Android automation. I explored various open source frameworks & cloud testing services and finally created our test farm using Open STF. I modified existing automation framework to support STF & enabled parallelization in execution. With his effort, we were able to support multiple devices in automation & reduce the total execution time considerably. STF based test farms also opens a door to lot of other possibilities like sharing automation devices across teams, remote debugging/testing and managing device inventory.
• Helping the team transition from writing Device based tests to device independent tests.
• The team previously used to write a lot of device dependent testcase which would only run on one particular model of device as we do not get Ui Objects for PDF elements. I explored various C++ core PDF APIs and got them exposed to the java layer which when used helped the QE team to write test in a non-device dependant format that could be run on array of devices.

May 2016 – Oct 2017 · 1 yr 5 mos · Noida, Uttar Pradesh, India

• Developed generic framework for automation that can be used for any Android app + Migration from UiAutomator to Espresso(Black Box to an API based automation).
• I worked on upgrading Acrobat’s core automation framework which was worked upon intensively since long and had over 2000+ test cases running through it. A lot of these test cases were flaky and would fail at random network/core calls which made it really difficult to debug and the number of these failures was also huge, almost 200+.
• Then I decided to move to a more robust and easily debuggable framework and decided to transition to Espresso. I was the only member to have this implemented this in acrobat android and since nobody else was doing it at that time it was mostly a self driven effort. This made acrobat one of the most early adapters of Espresso framework. Also this framework is very generic and with a few changes it could be consumed by any of the android apps.

Jul 2015 – Apr 2016 · 9 mos · Noida, Uttar Pradesh, India

Jul 2014 – Jun 2015 · 11 mos · Noida, Uttar Pradesh, India