Principal Quality Assurance Engineer

Principal QA Engineer (Web & API Automation)

Location : [Pune]

Experience : 5 - 7 Years

Role summary

We are seeking a highly motivated and experienced Principal QA Engineer to drive the quality strategy for our complex, web-based applications and microservices. The ideal candidate possesses a deep understanding of software testing principles, has significant hands-on experience in functional, API testing. This role is a blend of hands-on automation, architectural design, and technical leadership.

Minimum qualifications

• Experience : 5-7 years of professional experience in Quality Assurance / Test Automation.
• Functional & systems testing : Expert-level knowledge of software testing methodologies, writing detailed test plans, and designing comprehensive, end-to-end functional test cases.
• API expertise : Proven, hands-on experience in testing RESTful and / or GraphQL APIs, including deep knowledge of protocols and status codes, and experience with dedicated API testing tools / frameworks.
• Automation proficiency : Strong hands-on experience developing and maintaining automated test scripts for complex web applications using a programming language such as Java, JavaScript .
• Web automation tools : Experience with a leading web automation tool (Selenium WebDriver, Playwright).
• Agile : Experience working within an Agile / Scrum environment with tools like Jira.
• Databases : Proficiency in writing and executing SQL queries for data validation. Basic conceptual knowledge and ability to interact with at least one NoSQL database.
• Command-line & system interaction : Strong proficiency with the Linux command line (e.g., ssh, grep, tail, curl). Ability to troubleshoot, analyze server logs (Java / JavaScript systems), and perform basic diagnostics / shell scripting. Familiarity with Docker concepts and basic commands to interact with containers via CML.
• Networking fundamentals : A solid understanding of basic networking concepts (e.g., firewalls, whitelisting, load balancing, DNS) to effectively triage issues and determine if they originate from the frontend, backend, or infrastructure layer.