Software QA Engineer (Manual Testing)

TEOCO

Hatgachha, West Bengal, INFull-timeMidPosted Jun 12, 2026

SeleniumJavaPythonJavaScriptSQLJIRA

Best fit for

This role is best for mid-level QA engineers with hands-on experience in Selenium, Java, Python, JavaScript / TypeScript open to working from Hatgachha, West Bengal, IN.

Skills you need for this role

Detected from the job title, description, and tags.

Automation skills

Selenium — Still the most-asked browser automation framework in QA interviews and legacy suites.

Programming languages

Java — Dominant language for enterprise QA + Selenium/RestAssured stacks.
Python — Popular for API testing, data validation, and Playwright/Pytest suites.
JavaScript / TypeScript — Required for Playwright, Cypress, and modern front-end test tooling.
SQL — Data validation and back-office QA rely on solid SQL.

Domain & process

Agile / Scrum — You'll be expected to describe how you fit QA into short iterations.
Test management (Jira / Zephyr / TestRail) — Process fluency — writing test cases, tracing coverage, and reporting defects.

Job description

Job Summary We are seeking a detail-oriented and motivated Telecom Software Test Engineer to join our Quality Assurance team. The ideal candidate will have 2.5-4 years of experience in Manual Testing and a strong understanding of software testing methodologies. This role involves validating telecom software applications, understanding business requirements, executing test cases, identifying defects, and working closely with cross-functional teams to ensure high-quality product releases. Key Responsibilities

Learn Telecom data and domain knowledge.
Understand requirements and participate in the testing lifecycle, including requirement analysis, test case design, test execution, defect logging, root cause analysis, and providing feedback to developers.
Participate in feature testing, regression testing, and service patch sanity testing, and be responsible for delivering high-quality output.
Develop and execute test cases for various product functionalities.
Analyze and understand test data and apply that knowledge during manual testing activities. Required Skills & Competencies
Around 3 years of experience in Manual Testing and Functional Testing, including designing, developing, and maintaining test cases.
Experience with tools such as JIRA, Bugzilla, or other ALM (Application Lifecycle Management) / bug tracking tools.
Strong troubleshooting and problem-solving skills.
Basic understanding of SQL and PL/SQL.
Knowledge of the Defect Lifecycle and bug reporting. Preferred Skills / Tools Knowledge
Knowledge of any programming language such as Java, Python, or JavaScript.
Automation testing skills using Selenium or any other automation tool.
Basic understanding of HTML/CSS.
Prior experience working in a Scrum team. Education
B.Tech / B.E. / MCA in Computer Science, Electronics & Communication, Information Technology, or related disciplines. Experience
Software Testing background with 2.5-4 years of experience in Manual Testing. Employment Type: FULL_TIME

Job highlights

•Role: Software QA Engineer (Manual Testing)
•Company: TEOCO
•Location: Hatgachha, West Bengal, IN
•Type: Full-time
•Experience: Mid
•Seniority: Mid
•Posted: Jun 12, 2026

Key skills: Selenium · Java · Python · JavaScript · SQL · JIRA

How to prepare for this interview

A 5-step prep plan tailored to this job's stack.

1Revise Selenium deeply — locator strategy, waits, parallelisation, and how you'd structure the framework from scratch. Selenium interview Q&A →
2Read through the general QA/SDET interview prep guide to refresh core testing concepts. Job Interview Prep →
3Warm up on SQL joins, group-bys, and window functions — most QA rounds include a data-validation query. SQL Q&A →
4Do at least one AI mock interview end-to-end so you're comfortable narrating your answers under time. AI Mock Interview →
5Run your CV through the ATS review so it clears keyword filters for this role before you apply. Resume ATS Review →

Likely interview questions for this role

Tuned to the stack we detected on this job.

Q1.Explain the Page Object Model and how you'd structure it in Selenium.
Q2.How do you handle dynamic waits without using Thread.sleep in Selenium?
Q3.Write a SQL query to find duplicates across two columns and how you'd fix them in test data.
Q4.Walk me through a bug you found that shipped anyway — how did you handle it?
Q5.How do you decide what to automate vs test manually for a new feature?