Summary of "QA в 2026: есть ли смысл или уже поздно? Как не слить 1–2 года впустую"

Key topics: QA/Testing market, AI impact, and career paths

The speaker says the QA/testing market was “battered” because hiring and onboarding became harder around 2025 compared to 2024.
Hiring cycles/rollouts were described as taking roughly 3–4 months, with “blocking” issues appearing.
A hiring “auto-filtering” stage is referenced (mentions “neurofilters” / “glasses”).
Even with a market slowdown, the speaker believes manual testing is relatively safe from AI replacement.

AI is framed as reducing routine work, such as:
- editing documents
- helping interpret requirements
The main claim: manual testers are hard to replace because they rely on:
- human judgment
- communication across teams and stakeholders
The speaker argues that “the future of clicking buttons” (e.g., in Postman-like tooling) doesn’t remove the difference between:
- the tester’s role: requirements understanding, interaction, reasoning about user paths
- automation/engineering: running checks, scripting, verifying endpoints

QA is described as a cross-functional communication layer between:
- business requirements / analysts
- developers implementing features
- clarification loops when requirements and implementation diverge
Good QA is characterized as being spread across the entire lifecycle, driven by constant communication, not only executing test scripts.
The speaker notes that software/product work is often “more expensive” than hardware, which underscores the importance of software correctness and alignment.

The speaker suggests basic QA knowledge can be “enough” if you focus on:
- fundamentals
- commonly used tools
The biggest real obstacle is portrayed as job search, not studying:
- many bootcamp/graduates (e.g., Yandex Practicum / Skillbox-like) enter the market with large applicant batches and similar resumes/claims.

The speaker describes a likely hiring funnel:

Automated/first filtering based on whether the resume matches expected “responsibilities” and the “stack canonically.”
A human recruiter who can detect repetition (e.g., “why so many people with the same company/stack?”).
If there’s interest, a more personal conversation follows.

They emphasize candidates should be realistic and align with the role they claim to fit.

Recommended approach: gain experience in different areas/industries first (e.g., fintech, e-commerce) to find a niche.
Growth options mentioned:
- become senior within a domain
- move toward automation testing
- transition into development (if you want to code)
- move into analytics
- move into management (e.g., testing lead / project management)
QA experience is positioned as giving a broad understanding that can support transitions into other roles (analytics/management/etc.).

AI is described as useful for:

The speaker also suggests an example idea:

potentially copying/generating test cases from inputs/data (they note they haven’t deeply done it personally, but believe it’s possible)

Hiring should not be only technical:
- technical gaps are easier to teach than communication issues
They prioritize “behavioral adequacy”, including:
- a clear dialogue thread during the interview
- appropriate conduct (not chaotic behavior)
Team communication is treated as critical infrastructure:
- poor interpersonal behavior is described as disruptive for developers and the process.

The episode references online training, including maps/roadmaps, and the speaker (Pasha) offers guidance.
No explicit product reviews appear; instead, the episode functions as:
- a career guide / interview strategy
- a discussion of how hiring works for QA

Pasha — software testing lead and QA/testing mentor (primary interview subject; also self-referenced as the training provider).
Interviewer/Host — asks about market trends, AI impact, career paths, and hiring criteria.