Sunil Chitalkar

Lead Software Test Specialist - C++

Siemens Technology and Services Private Limited•  June 2021 - Present

• Working in Siemens Mobility domain - Simis W Electronic Interlocking Project. • It is transitioning Project from Pascal to C++ Programming language. • Involved from SRS document preparation to the actual Project transitioning Work. • Responsible for leading testing efforts during transition of the project.

Software Development Engineer in Test

Nvidia•  April 2018 - June 2021

Professional Summary: • C/C++ Automation Experience , along with little hands on experience with Python. • Familiar with Perforce, Swarm, Jira, and Confluence. • Good hold on problem solving, Data structures and Algorithms. • Experience of doing peer code reviews and leading the design discussion meetings. • Have Training experience to groom someone to write automation tests in C++. • Experience of working with WINAPI and NVAPI. • Strong experience in debugging and fixing Script issues. • Strong expertise in manual and automation testing of graphics driver. • Strong experience in testing computer games and finding defects. • Good knowledge on different types of displays like G-Sync, HDR, Free-Sync, Tiled displays. • Efficient in creating new test cases and testing it manually, running automation tools and analyzing logs. • Strong experience of finding defects and actively driving it with developers to fix it. • Experience of computer Hardware troubleshooting.

Software Quality Assurance Engineer II

Nvidia•  October 2015 - March 2018

Release/UDA Team: In this team I was responsible for assuring quality of graphics driver. finding defects and tracking it . working on PC gaming , streaming , multimedia , multi-display and GPU power/Thermal Testing.

Software Quality Assurance Engineer I

Nvidia•  June 2013 - September 2015

Upstream Team : This team was responsible for doing sanity and regression testing of graphics driver build to decide whether build should be approved for in depth testing or has very obvious issues and can not be approved for in depth testing without fixing those blockers. Some of the responsibilities under this team: 1) Analyzing weekly bugs fixed by developers. 2) Noting the root cause of bugs and fixes made by developers. 3) Take inputs from developers for suspected areas needs to be tested. 4) Use past testing experience + analyze the data captured in above points and decide the test plan. 5) follow both Black box and white box testing methodologies to find the blockers and report it and get it fixed by following up with developers as soon as possible.