• Team leadership & mentorship. • C, C++, Linux, Python, MATLAB. • Test case, script development, and validation. • Oscilloscopes, logic analyzers, pulse generators, CANalyzer, CANape • High-level understanding of electrical, electronics, mechanical, and embedded SW • Document, and track software defects. • Root cause issues analysis in electrical, mechanical, and software systems.
• Researching and documenting detailed test plans and cases, and testing procedures • Reporting and presenting test results, critical insights, and testing strategies. • Performed integration testing, regression testing, SIL, and HIL testing of software for embedded systems. • Researched and tested communication protocol and low-level interfaces including I2C, SPI, CAN, and Ethernet. • Tested and validated APIs using MQTT and RESTful protocols, ensuring scalability, performance, and reliability in distributed systems developed in Java and C++. • Collaborate with developers, hardware engineers, and system architects to enhance product reliability. • Tested software in embedded system (ArmXL, Raspberry Pi), and Linux environment, and worked with Raspberry Pi for automation testing, used Pytest, Robot Framework, and Postman for automation testing. • Researched and tested automated test cases to validate robust algorithms, performed regression testing, and conducted regular code reviews to ensure software quality • Led the validation release process for multiple customer releases, defining test strategy scopes, executing tests, and signing off the final release. • Participated in OCPP and charging standard certification, tested software with industry across CPOs, EVSE manufacturers, and OEMs.
Very straightforward lasted about an hour, the interviewer was very nice and mostly just talked about what it is they do. Make sure to ask many questions and show overall interest.
The interview process involved a 1-hour panel discussion with multiple team members. They asked about my technical expertise, past experience, problem-solving skills, and knowledge of relevant tools, frameworks, and best practices in software develo
A call with recruiter to discuss about the role, location, and every common things, and then followed by a interview with 3 different members of the team. Overall, it was an average kind of interview because the question seems some weird.
Very straightforward lasted about an hour, the interviewer was very nice and mostly just talked about what it is they do. Make sure to ask many questions and show overall interest.
The interview process involved a 1-hour panel discussion with multiple team members. They asked about my technical expertise, past experience, problem-solving skills, and knowledge of relevant tools, frameworks, and best practices in software develo
A call with recruiter to discuss about the role, location, and every common things, and then followed by a interview with 3 different members of the team. Overall, it was an average kind of interview because the question seems some weird.