Question 1

What stack is most often required from Manual QA?

Accepted Answer

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.

Question 2

Which test design techniques must be known?

Accepted Answer

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).

Question 3

Can you work as Manual QA remotely?

Accepted Answer

Yes, 32% 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%.

Question 4

Manual QA vs QA Automation vs SDET — what career progression?

Accepted Answer

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).

Question 5

How is Manual QA different from Business Analyst / Product Manager?

Accepted Answer

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.

Question 6

How to start in Manual QA in 2026?

Accepted Answer

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.

Question 7

How many Manual QA openings in CIS and Europe?

Accepted Answer

300 active open Manual QA jobs in Zorky sample. Geography: Russia, Poland, Ukraine. 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).

Question 8

What skills does a Senior Manual QA need?

Accepted Answer

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).

Demande ouverte	267
Offre observée	— non publié

pays	offres
RU	102
PL	55
UA	32
KZ	7
US	6
PH	6
BY	5
HK	3
IN	3
TH	2

niveau	offres
middle	63
junior	36
senior	36
lead	4
principal	2

part	valeur
top 1	4.9%
top 3	8.8%
top 10	18.1%
longue traîne	81.9%

Manual QA : marché

Timeline: postings and sources

New postings and active sources per week

Remote work over time

Remote postings, %

Technologies over time

Postings mentioning the technology, %

Countries over time

Postings in the country, %

Demande et offre observée

Distribution des salaires

Géographie de la demande

Utilisée avec

Demande par niveau

Employeurs

Où Zorky voit ce marché

Postes récents

Marchés voisins

À propos des données

Laisser une demande