Manual QA Tester
Manual QA Testers design, execute, and document the test cases that protect users from bad software. They read functional specs and acceptance criteria, write test cases in tools like TestRail, Zephyr, or qTest, run those cases against staging builds, file defects in Jira with reproducible steps and screenshots, and re-test fixes. They also run exploratory testing (no script, just product intuition + curiosity), validate cross-browser and cross-device behavior, do regression sweeps before each release, and verify accessibility, localization, and edge cases that automation misses. In India this is the largest QA hiring tier — TCS, Infosys, Cognizant, Wipro, Capgemini, Accenture, and most BFSI clients hire freshers in batches of hundreds for manual testing pools, and the role is the most common entry point into the broader software-testing career ladder. The pay tier is genuinely lower than developer or automation roles, but the entry bar is lower too — and 70%+ of Indian automation engineers and SDETs began their career here.
Overview
Manual QA Testers design, execute, and document the test cases that protect users from bad software. They read functional specs and acceptance criteria, write test cases in tools like TestRail, Zephyr, or qTest, run those cases against staging builds, file defects in Jira with reproducible steps and screenshots, and re-test fixes. They also run exploratory testing (no script, just product intuition + curiosity), validate cross-browser and cross-device behavior, do regression sweeps before each release, and verify accessibility, localization, and edge cases that automation misses. In India this is the largest QA hiring tier — TCS, Infosys, Cognizant, Wipro, Capgemini, Accenture, and most BFSI clients hire freshers in batches of hundreds for manual testing pools, and the role is the most common entry point into the broader software-testing career ladder. The pay tier is genuinely lower than developer or automation roles, but the entry bar is lower too — and 70%+ of Indian automation engineers and SDETs began their career here.
A Day in the Life
Reach the office (TCS / Infosys / Cognizant / Wipro / Capgemini in Bengaluru / Hyderabad / Pune / Chennai / Kolkata), or log in if hybrid; coffee, scan emails and Jira notifications from the dev team in the US time zone.
Daily 15-min standup with the QA pod (4-10 testers + lead) — share yesterday's test execution counts, defect count, and blockers.
Open TestRail / Zephyr / qTest, pick up the day's assigned test cases from the sprint plan; review acceptance criteria and any updates to specs.
Execute 20-40 manual test cases against the current sprint's staging build — typically 2-3 hours of focused testing in a checklist with screenshots and notes.
File 2-6 defects in Jira with reproducible steps, expected vs actual behavior, environment details (browser, OS, build number), screenshots / screen recordings, severity ratings.
Lunch with the QA team and developers; informal sync on a tricky acceptance criterion or a defect that the dev team disagrees with.
Re-test 3-8 fixed defects from earlier sprints — verify the fix, check for regressions, sign off or reopen with new repro details.
Run 30-60 minutes of exploratory testing on a new feature with no script — try unusual inputs, slow networks, edge cases, accessibility paths, boundary conditions.
Cross-browser (Chrome, Firefox, Safari, Edge) and cross-device (Android, iOS, common screen sizes) testing on a key user flow; log any browser-specific defects.
Write or update 5-15 test cases in TestRail / Zephyr for a new story being picked up next sprint, following the team's case-design standard.
Sprint demo or status sync — present test execution status, defect counts, release-readiness recommendation to the engineering manager and BA.
End-of-day status email to the offshore client / engineering manager; wind down. Release weeks add 1-2 evening hours; client UAT weeks may extend to 9-10 PM.
Common Mistakes
7- ⚠️Treating manual QA as a 20-year careerWhy: Pure routine-regression manual QA is shrinking at product companies; salary ceiling is ~₹18L for senior ICs while peers in automation / SDE clear ₹40L+ by year 7.Instead: Plan to transition into automation, QA management, exploratory specialist, accessibility, or product management within 3-5 years; treat manual QA as a strong starting role, not the destination.
- ⚠️Filing defects with poor reproducibilityWhy: Defects without clean steps / environment / screenshots get rejected as 'cannot reproduce' or 'works on my machine'; this damages tester credibility and slows release cycles.Instead: Treat every defect like a mini-essay: exact steps, environment, expected vs actual, screenshots / video, severity rationale, and a one-line summary that survives a dev's first skim.
- ⚠️Skipping ISTQB Foundation in services-company tracksWhy: Most Indian services QA ladders require ISTQB Foundation for promotion past 2-3 years; engineers who delay it lose increments and project-allocation priority.Instead: Earn ISTQB Foundation within the first 12-18 months; most services employers reimburse the ₹15-25K cost after one year.
- ⚠️Refusing to learn any codingWhy: Manual testers who can't read code or write simple SQL / Postman scripts stall at junior-IC; meanwhile peers who learn a little code get promoted into automation and out-earn them by 80-150%.Instead: Spend 30-60 min a day on SQL, HTML/CSS basics, Postman, and one scripting language (Python or JavaScript); even working proficiency dramatically opens career paths.
- ⚠️Letting regression suite repetition dull product instinctWhy: Running the same regression for 18+ months without exploratory work numbs the curiosity that distinguishes great testers; promotions slow and exit options narrow.Instead: Reserve 20-30% of your week for exploratory testing, accessibility / localization sweeps, or UAT facilitation; volunteer for the work that automation can't replace.
- ⚠️Avoiding difficult clients / domainsWhy: Tester credibility compounds via hard projects — regulated BFSI workflows, healthcare claim systems, defense releases. Engineers who only take 'easy' projects don't build the domain depth that gates senior roles.Instead: Volunteer for the regulated / domain-heavy projects in years 3-6; banking / insurance / healthcare domain knowledge is one of the few moats manual testers have.
- ⚠️Staying in services past year 5 hoping for an automatic promotionWhy: Senior IC manual-QA promotions at Indian services companies are slow (often 1.5-2 years between bands); peers who switch to product companies or move into automation typically out-earn lifers by year 8.Instead: By year 3-4, either commit to QA Lead / Manager track within services, switch to a product company, or transition into automation; passive tenure is the lowest-return path.
Salary by Indian City (Mid-level total cash comp)
6| City | Range |
|---|---|
| Bengaluru | ₹6-11 LPA |
| Hyderabad | ₹6-10 LPA |
| Pune | ₹5-10 LPA |
| Delhi NCR (Gurugram/Noida) | ₹5-10 LPA |
| Chennai / Mumbai | ₹5-9 LPA |
| Remote / International contract | ₹10-22 LPA |
Notable Indians in this career
5Communities + forums
7- Ministry of TestingWeb + SlackLargest global testing community; very active India chapter; TestBash conference, deep courses, and a Slack with senior QA leaders worldwide — the single highest-leverage community for manual testers.
- Indian Testing Conference / Indian Testing BoardIn-person + webIndian Testing Board administers ISTQB certifications in India and runs the Indian Testing Conference; the most credible India-specific networking and certification venue.
- Long-running global testing community started by Indian testers (Ajay Balamurugadas, Pradeep Soundararajan, Santhosh Tuppad) — weekly online sessions where testers do guided exploratory exercises together.
- Long-running India-based testing blog with vast tutorial library, interview-question banks, tool comparisons; one of the most-read manual-QA learning resources globally.
- Active global subreddits with strong India presence; honest discussion of career paths, services vs product transitions, automation upskilling timelines.
- Crowdsourced-testing community and forum (now part of Applause); useful for picking up side-project paid testing and seeing how senior testers approach exploratory and accessibility work.
- Pradeep Soundararajan / Smita Mishra / Ajay Bala (LinkedIn)LinkedInFollowing senior Indian testing voices on LinkedIn — they share career advice, industry trends, and conference talks; an under-appreciated learning channel for India-specific QA growth.
What to read / watch / follow
10- Foundations of Software Testing — ISTQB Certificationbookby Dorothy Graham, Erik van Veenendaal, Isabel Evans, Rex BlackThe official ISTQB Foundation textbook; required for Indian services-company QA certification and the foundation for most senior-level test reasoning.
- Lessons Learned in Software Testingbookby Cem Kaner, James Bach, Bret Pettichord293 concise lessons from three of the most influential testers in the field; one of the most widely cited references for context-driven and exploratory testing practice.
- Explore It! Reduce Risk and Increase Confidence with Exploratory Testingbookby Elisabeth HendricksonThe clearest practical guide to exploratory testing; covers session-based testing, charters, and structured exploration — the skill that separates senior testers from script executors.
- A Practitioner's Guide to Software Test Designbookby Lee CopelandDetailed coverage of test-design techniques: boundary value, equivalence partitioning, decision tables, state transition, use-case testing — load-bearing for every test plan.
- Agile Testing / More Agile Testingbookby Lisa Crispin & Janet GregoryStandard references for agile QA practice; covers in-sprint testing, BDD, the testing quadrants, and the shift from waterfall test-cycles to continuous-delivery testing.
- What If… (book series)booksby Ajay BalamurugadasShort, India-rooted books packed with exploratory-testing exercises, heuristics, and tester thinking; written by one of India's most respected testing teachers.
- Software Testing Help (blog + YouTube)blog / videoby STH teamComprehensive India-based tutorial library covering Jira, TestRail, Postman, SQL for testers, interview prep; one of the highest-traffic QA learning destinations globally.
- Pradeep Soundararajan / Moolya blog and talksblog / videosby Pradeep SoundararajanLong-form Indian thought leadership on what skilled, judgment-driven testing actually looks like; useful for testers who want to move past script execution into senior-IC territory.
- Ministry of Testing Dojo (free + paid courses)coursesby Ministry of TestingHigh-quality short courses on exploratory, accessibility, API testing, performance basics — paired with the slack community, the best non-services upskilling path for Indian testers.
- Curious Tester blogblogby Parimala HariprasadCareer-focused writing for QA professionals — covers exploratory thinking, women-in-QA, India-specific career advice; underrated and consistently practical.
Daily Responsibilities
7- Execute 20-60 manual test cases against the current sprint's build — typically 4-6 hours of focused testing in a checklist or test-management tool.
- File 2-8 defects in Jira with reproducible steps, expected vs actual behavior, screenshots or screen recordings, environment details, and severity ratings.
- Re-test 3-10 fixed defects from earlier sprints — verify the fix, check for regressions, sign off or reopen.
- Run 30-90 minutes of exploratory testing on a feature with no script — try unusual inputs, slow networks, edge cases, accessibility paths.
- Attend daily 15-min standup, sprint planning, sprint demo, and one ad-hoc sync with a developer or BA on a defect or unclear acceptance criterion.
- Write or update 5-15 test cases in TestRail or Zephyr for a new story being picked up next sprint, following the team's case-design standard.
Advantages
- The most accessible entry point into Indian IT — TCS, Infosys, Cognizant, Wipro, Capgemini, Accenture hire batches of hundreds every year, and any bachelor's degree plus ISTQB is enough to apply.
- Lower entry bar than developer roles — no DSA grind, no system design rounds; the interview is product reasoning, test-case design, and a defect-reporting writing sample.
- Excellent stepping stone — 70%+ of Indian automation engineers, SDETs, and even product managers started in manual QA. The role teaches the product end-to-end faster than any other entry-level job.
- Predictable hours and fewer 2 AM pages — most manual QA work is sprint-aligned, with overtime only during release weeks; on-call and production-incident pressure is rare.
- Career-switcher friendly — non-tech bachelors (B.Com, BBA, BA), career returners, and ex-BPO professionals routinely transition in with 4-8 weeks of focused study, much faster than an SDE switch (which takes 12-24 months).
Challenges
- Genuinely lower-paying than developer or automation roles — most freshers start at ₹2.5-4L and the senior individual contributor ceiling is ₹15-18L, which is 40-60% below an equivalent-tenure developer at the same company.
- Status pressure inside engineering culture — manual testers are often seen as 'less technical' by developers, even at companies that publicly value QA. This bias affects assignments, mentorship, and promotion velocity.
- Increasing automation pressure — many product companies have explicitly shrunk their manual-QA headcount over 2022-2026, replacing routine regression with automated suites. Roles still exist for exploratory, UAT, and accessibility work, but the headcount trend is downward.
- Repetition fatigue — running the same regression suite every sprint for 18 months is monotonous; the work-hours are reasonable but the cognitive variety is lower than developer or designer roles.
- Career upside requires a transition — to break the ₹18L ceiling you almost always need to either move into automation engineering, become a QA manager, or pivot to product management. Staying in pure manual testing past year 5 starts to compress salary growth significantly.
Education
6- Required (most common): Any bachelor's degree — B.Tech / B.E. / BCA / B.Sc / B.Com is widely accepted. Indian IT services hire B.Com and BBA grads into manual testing pools after a 4-8 week internal training.
- Strong alternatives: Any STEM degree with strong logical reasoning. ISTQB Foundation Level certification is the most commonly required formal credential and is achievable in 4-8 weeks of part-time study.
- Self-taught path: Real but harder. A portfolio of detailed bug reports against open-source apps, a public test-case bank on GitHub, and 1-2 months of TryHackMe / OWASP Juice Shop exercises can land entry roles at startups.
- Certifications that hire: ISTQB Foundation (table-stakes), CSTE (Certified Software Tester) for IT services, ISTQB Agile Tester for product-company roles. Cost is typically ₹15-25K and reimbursed by most services employers after one year.
- Indian bootcamps: Edureka, NareshIT, JanBask, Simplilearn run 6-12 week manual QA programs. Useful for career switchers from non-tech backgrounds (commerce, hospitality, BPO) who need a job-ready credential, but a degree from any college plus ISTQB beats any bootcamp.