We are seeking a skilled QA Programmable Platform Engineer with expertise in functional testing, regression testing, and programmable platform validation for embedded systems. The ideal candidate will play a key role in ensuring product quality, reliability, and platform compatibility through comprehensive validation, test automation, and continuous integration practices.
Key Responsibilities
Define, develop, and execute functional, regression, integration, and system-level test plans for programmable platform solutions.
Design and maintain test cases, test scenarios, and validation procedures to ensure comprehensive test coverage.
Identify, track, and report defects, collaborating closely with development teams to ensure timely resolution.
Validate hardware and software compatibility across supported platforms and environments.
Develop and maintain automated test suites using tools such as Selenium and other automation frameworks.
Support and integrate testing activities within Continuous Integration (CI) pipelines.
Verify platform functionality, performance, stability, and reliability throughout the product lifecycle.
Collaborate with firmware, software, hardware, and product engineering teams to improve product quality and release readiness.
Contribute to test strategy, process improvements, and quality assurance best practices.
Required Technical Skills
Core Testing Skills
Functional Testing
Regression Testing
System Testing
Test Planning, Execution & Reporting
Defect Tracking & Management
Automation & CI/CD
Selenium Test Automation
Automation Framework Development & Maintenance
Continuous Integration (CI) Practices
CI/CD Environment Exposure
Platform & System Validation
Programmable Platform Validation
Linux-Based System Testing
BIOS Testing & Validation
Hardware/Software Compatibility Verification
Firmware Testing & Validation
Communication Protocols: Hands-on experience with:
Modbus
BACnet
MQTT
Primary Technology Focus
Programmable Platform Validation
Functional & Regression Testing
Firmware and Embedded System Testing
Test Automation
Linux-Based Systems
Continuous Integration (CI/CD)
Communication Protocol Testing
Preferred Qualifications
Bachelor's degree in Electronics, Electrical Engineering, Computer Science, or a related discipline.
6-8 years of experience in Software QA, Firmware QA, Embedded System Testing, or Programmable Platform Validation.
Hands-on experience with test automation frameworks and CI/CD environments.
Strong understanding of Modbus, BACnet, and MQTT communication protocols.
Familiarity with Cyber Resilience Act (CRA) requirements is desirable.
Ability to read and interpret hardware schematics is an added advantage.
Strong analytical, troubleshooting, debugging, and communication skills.
Ideal Candidate Profile
A quality-focused QA professional with strong expertise in:
Functional and Regression Testing
Firmware & Embedded System Validation
Test Automation and Selenium
Linux-Based Platform Testing
Hardware-Software Integration Testing
Continuous Integration Practices
Industrial Communication Protocols (Modbus, BACnet, MQTT)
The ideal candidate should be capable of driving end-to-end quality assurance activities and ensuring reliable, high-quality releases for programmable platform and embedded system products.
This guide is for freshers in India preparing for their first QA or software testing job, and for manual testers with one to ten years of experience preparing for a switch. It has 60 questions with answers in three levels: easy covers the basics every fresher is asked, medium covers real project work such as test design techniques, API checks, JIRA and agile, and hard covers test strategy, risk, metrics and release decisions. The answers are written the way a strong candidate would say them, with examples from everyday Indian apps such as UPI payments and OTP logins. Read a question, answer it aloud first, then compare with the answer, and take the mock test to check yourself against the clock.
Questions you may be asked
What is software testing, and why do companies need testers if developers already test their own code?
What is the difference between verification and validation?
Explain the difference between an error, a defect and a failure.
What is the SDLC, and at which stage should a tester get involved?