Manual QA: market
Manual QA (manual testing) — traditional tester role: writing test cases from requirements, exploratory testing, bug reports in Jira, regression testing before releases. The most capacious QA segment with the lowest entry barrier (after ISTQB courses 3-6 months). Role family: Manual QA Engineer (general — functional testing), Manual Tester (entry-level, simple manual scenarios), Mobile Manual QA (testing iOS/Android applications on real devices), Web Manual QA (cross-browser testing, accessibility), QA Lead (organization of testing, mentoring Juniors). Stack: Test design techniques (must — equivalence partitioning, boundary value, decision tables, state transition, pairwise), SQL (must — SELECT/JOIN/GROUP BY for verification of test data), Postman (API testing without code), Charles/Proxyman/Fiddler (HTTP traffic analysis), Jira + Confluence (bug reports + documentation), TestRail/Zephyr/qase.io (test management), DevTools (Chrome/Firefox for web testing), iOS Simulator/Android Studio Emulator + real devices, BrowserStack/Sauce Labs (cross-browser real devices in the cloud), Linux/macOS CLI basics. Top stack: jira, postman, sql, agile, rest. 33% — remote. Manual QA — the most accessible entry point to IT for people without programming background.
The Manual QA market currently has 262 open roles, 233 of them freshly observed. Median salary $2,709/mo.
33% of Manual QA vacancies — remote or hybrid. The most remote-friendly entry segment of IT.
⚠ salary known for 13 of 262 jobs; remote share from 195 with a stated format; 233 counted as fresh observations; trend and hiring difficulty are not shown
Demand and observed supply
| Open demand | 262 |
| Observed supply | — not published |
Manual QA forms a steady flow of vacancies — the most capacious entry segment of IT. Drivers: banks (huge Manual QA fleet for regression testing before deploys), outsourcers, new EdTech startups. Trend 2026: migration Manual QA → Automation continues, but Manual QA remains as entry point + Senior vacancies in banks/regulated industries.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
Salary distribution
One in ten earns under $1,641, one in ten over $6,090. Half the market falls between $2,000 and $5,500. Sample: 13.
⚠ percentiles from 13 salaries out of 262 jobs — a guide on a small sample
Demand geography
| country | jobs |
|---|---|
| RU | 108 |
| PL | 49 |
| UA | 33 |
| US | 6 |
| PH | 6 |
| KZ | 6 |
| HK | 3 |
| IN | 3 |
| RS | 3 |
| BY | 2 |
Leader by Manual QA job count — Russia (0 positions). Russia — banks + outsourcers dominate. Poland — large Manual QA segment for Russian-speaking on US/EU projects.
⚠ job counts only: salary by country is not published
Used together with
Top stack Manual QA 2026: Test design techniques (must — ISTQB Foundation Level), SQL (must for Senior), Postman (API testing), Charles/Proxyman/Fiddler (HTTP traffic), Jira + Confluence, TestRail/Zephyr/qase.io, DevTools (Chrome/Firefox), iOS Simulator/Android Studio Emulator + real devices, BrowserStack/Sauce Labs, Linux/macOS CLI basics.
Common pairs: ISTQB + Jira + TestRail, SQL + Postman, DevTools + Charles, iOS Simulator + real devices. Learning roadmap: ISTQB Foundation → SQL basics → Postman → DevTools → Jira + Confluence → mobile testing → Charles.
Demand by grade
| grade | jobs |
|---|---|
| middle | 56 |
| junior | 37 |
| senior | 31 |
| lead | 6 |
| principal | 3 |
The most capacious Junior market in IT (3-6 months of ISTQB courses = entry). Career flow: Junior → Middle → Senior → either QA Lead, or Automation (the most common progression), or BA/PM.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Employers
Demand is spread across 158 employers. The largest accounts for 5.2%, the top ten for 19.2%; the remaining 80.8% is long tail.
| share | value |
|---|---|
| top-1 | 5.2% |
| top-3 | 9.8% |
| top-10 | 19.2% |
| long tail | 80.8% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Where Zorky sees this market
Observed across 59 sources; the largest accounts for 10.3% — this market does not rest on a single channel.
Recent openings
- Manual Tester with API · PL
- Тестировщик · RU
- Manual Tester · PL
- Middle Manual QA Engineer (Mobile) · UA
- Manual QA Engineer · UA
- Тестировщик-автоматизатор Java · BY
- Вакансия. Manual QA Engineer · RU · $1,641
- Ищем QA-тестировщика в IT-проект! · RU · $2,000
Latest open Manual QA jobs — most recent 10 positions with adequate description quality. Full list — in our CRM or via the «see all» link below.
Adjacent markets
Manual QA — the most accessible entry point to IT. By median below Automation by 30-40%, but Junior market is the most capacious. Career progression to Automation is typical in 1-2 years. Comparison — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Data as of 2026-10-20
Direction: QA / Testing
Related specializations
Inside Manual QA: Manual QA Engineer (general — functional testing), Manual Tester (entry-level, simple scenarios), Mobile Manual QA (iOS/Android on real devices), Web Manual QA (cross-browser + accessibility), QA Lead (management + mentoring). Comparison with Automation/SDET — in the bar below.
Frequently asked questions
The most common questions about Manual QA: salaries, test design techniques, difference from Automation/SDET, remote, difference from BA/PM, how to become one (3-6 months — the most accessible entry to IT), Senior skills. Answers recompute automatically.
What stack is most often required from Manual QA?
Top-5: jira, postman, sql, agile, rest. Test design techniques — must (equivalence partitioning, boundary value, decision tables, state transition, pairwise testing). Knowledge of ISTQB Foundation Level — standard for Junior+. SQL — must for Senior (SELECT/JOIN/GROUP BY for verification of test data, INSERT/UPDATE for setup). PostgreSQL and MySQL bases. Postman — REST API testing without code (collections, environments, scripts). HTTP/REST understanding (status codes, headers, methods, JSON). Charles/Proxyman/Fiddler — HTTP traffic analysis (debug network calls). Jira + Confluence — bug reports + test documentation. Test management: TestRail, Zephyr, qase.io (optional). DevTools (Chrome/Firefox) — for web testing (Network, Console, Elements). Mobile: iOS Simulator/Android Studio Emulator + real devices, Charles for mobile traffic. BrowserStack/Sauce Labs — cross-browser real devices in the cloud. Linux/macOS CLI basics — for server logs reading. Knowledge of regression/smoke/sanity testing types.
Which test design techniques must be known?
Senior Manual QA owns 5+ core techniques (ISTQB Foundation Level + Advanced Level): Equivalence Partitioning (partitioning of inputs into equivalence classes — the most basic), Boundary Value Analysis (boundary values — must for numeric inputs), Decision Tables (complex business rules with many conditions), State Transition Testing (for stateful systems — login/checkout flows), Pairwise Testing (combinatorial testing when many input combinations). Advanced: Use Case Testing, User Story Testing, Exploratory Testing (based on charters), Risk-Based Testing (prioritization by risk for deploy). Knowledge of Black-box vs White-box vs Grey-box testing approaches. Book «Software Testing Techniques» Beizer — classic. ISTQB Foundation Level — must for Junior+ (market expects certificate as proof of fundamentals).
Can you work as Manual QA remotely?
Yes, 33% of Manual QA vacancies are full-remote or hybrid. Manual QA — the most remote-friendly entry segment of IT: work entirely in Jira/TestRail/Postman + screen sharing for bug demo. Physical presence not needed (except rare hardware testing cases). Russian banks — hybrid or office due to compliance with test environment. Outsourcers — almost always remote on US/EU projects. Relocant hubs: Poland (Warsaw/Krakow — huge demand), Germany, Czechia, Serbia, Georgia, Armenia, Turkey. English — must for international remote with premium +25-40%.
Manual QA vs QA Automation vs SDET — what career progression?
Manual QA (this page) — entry-level: test cases by requirements, exploratory testing, bug reports. Programming level: opt-out (can be completely without programming). Accessible after 3-6 months of ISTQB courses. QA Automation — middle-level: writes E2E/UI/API auto-tests on ready frameworks. Programming level: "confident middle". Career-jump Manual QA → Junior Automation in 6-12 months of self-study. Details — QA Automation. SDET — senior level: writes TEST FRAMEWORKS (not only tests), Backend-level programming + QA domain expertise. Career-jump QA Automation → SDET in 2-3 years. Details — SDET. Typical career trajectory: Manual (1-2 years) → Automation (2-3 years) → either SDET (deeper programming), or QA Lead (management), or BA/PM (business).
How is Manual QA different from Business Analyst / Product Manager?
Manual QA (this page) — tests an already developed product, finds bugs, verifies conformance with requirements. Focus: verification and validation. Business Analyst — collects and formalizes requirements BEFORE development. Focus: what and why to build. Knowledge of SQL + BPMN + UML is more important than programming. Product Manager — defines product vision, roadmap, prioritizes features. Focus: what product to make and why. Knowledge of market research + customer interviews + A/B testing is more important than testing techniques. Career switch Manual QA → BA — in 6-12 months (often, especially with SQL mastery). Manual QA → PM — in 12-24 months (requires product-thinking shift). Many Senior Manual QA become BA in banks/fintech due to deep product knowledge.
How to start in Manual QA in 2026?
Roadmap (the most accessible entry to IT — 3-6 months): 1) ISTQB Foundation Level — Syllabus + Foundation Level exam (~$200 — certificate). Books: «ISTQB Foundation Level» Black, «Software Testing» Patton. 2) Understanding of test design techniques (equivalence partitioning, boundary value, decision tables, state transition). 3) SQL basics — Stepik «SQL for everyone», SQLZoo. Master SELECT/JOIN/GROUP BY + basic INSERT/UPDATE. 4) HTTP/REST API basics + Postman — Postman official tutorial + one public API testing. 5) DevTools (Chrome/Firefox) — Network/Console/Elements. 6) Jira + Confluence basics — bug reports + test documentation. 7) Mobile testing basics — iOS Simulator + Android Emulator + real device testing. 8) Charles/Proxyman for HTTP traffic analysis. 9) Pet project: full test plan + test cases + bug reports for open-source web app (e.g. saucedemo.com). Courses: Karpov.Courses «Testing», Y.Praktikum «Testing engineer», Otus «QA Manual», HTMLAcademy «Tester», Skillbox «Software Tester». Books: «Software Testing» Patton (best entry book), «Lessons Learned in Software Testing» Kaner (advanced). Time to Junior — 3-6 months (the most accessible entry to IT). After Junior — immediately plan transition to Automation in 1-2 years.
How many Manual QA openings in CIS and Europe?
292 active open Manual QA jobs in Zorky CRM sample. Geography: Russia / Ukraine / Poland. Real market is wider due to huge US/EU outsource through EPAM. Time to fill Senior Manual QA — 2-4 weeks (faster than Automation due to lower bar).
What skills does a Senior Manual QA need?
Senior Manual QA owns the full testing cycle + mentoring. Test design: mastery of all 7+ ISTQB techniques (equivalence partitioning, boundary value, decision tables, state transition, pairwise, exploratory, risk-based), test planning for large features, test strategy design. SQL: advanced queries for verification of test data (window functions for analytics, complex JOINs for validation of business rules). API testing: REST/GraphQL deep (Postman pre-request + test scripts, OpenAPI specs reading), contract testing basics (Pact). Mobile testing: cross-platform (iOS + Android) on real devices + emulators, mobile-specific testing (network conditions, battery, permissions, deep links, push notifications). Cross-browser testing: BrowserStack/Sauce Labs + Lighthouse audits + Web Vitals checks. Security testing basics: OWASP Top 10, SQL injection / XSS testing (smoke level). Performance basics: JMeter/k6 at the level of "read scenario and analyze results". Soft: mentoring Juniors, written communication (bug reports), participation in requirements review (suggest improvements before development). English for Senior+ — must for outsource/EU relocation (B1-B2 level).
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.