What QA Engineers Actually Do
What They Build
Chaos Engineering
Automated resilience testing with Chaos Monkey and fault injection.
Backstage
Developer portal for service discovery and infrastructure management.
SRE Platform
Site reliability tooling with SLOs, error budgets, and incident management.
Actions CI/CD
Scalable workflow automation running millions of jobs daily.
The role varies, but typically includes:
Test Automation (30-40%)
- Writing automated tests - Unit tests, integration tests, end-to-end tests
- Building test frameworks - Creating reusable testing infrastructure
- CI/CD integration - Integrating tests into deployment pipelines
- Test maintenance - Keeping tests up-to-date and reliable
Manual Testing (20-30%)
- Exploratory testing - Finding edge cases and unexpected behaviors
- Test case design - Creating test plans and test cases
- Regression testing - Testing existing functionality after changes
- User acceptance testing - Validating features meet requirements
Quality Processes (15-25%)
- Test strategy - Defining what to test and how
- Quality metrics - Tracking test coverage, bug rates, quality trends
- Bug triage - Prioritizing and tracking bugs
- Release process - Ensuring quality gates before releases
Performance & Specialized Testing (10-20%)
- Performance testing - Load testing, stress testing, performance analysis
- Security testing - Finding security vulnerabilities
- Accessibility testing - Ensuring accessibility compliance
- Cross-browser/platform testing - Testing across different environments
QA Engineer Archetypes: Know What You Need
Test Automation Engineer
- Focuses on writing automated tests and building frameworks
- Strong software engineering skills
- Common at companies with mature testing practices
- Risk: May lack manual testing expertise
Manual QA Engineer
- Focuses on exploratory and manual testing
- Strong domain knowledge and attention to detail
- Common at companies building complex products
- Risk: May lack automation skills
SDET (Software Development Engineer in Test)
- Strong software engineering background
- Builds testing infrastructure and tools
- Common at larger tech companies
- Risk: May focus too much on tooling, not enough on testing
Quality Engineer
- Focuses on quality processes and metrics
- Improves quality across the organization
- Common at companies prioritizing quality culture
- Risk: May lack hands-on testing experience
Be explicit about which type you need.
Interview Focus Areas
Testing Fundamentals
- Test strategy and test case design
- Types of testing (unit, integration, E2E, performance)
- Bug reporting and tracking
- Quality metrics and test coverage
Test Automation
- Can they write automated tests?
- Experience with testing frameworks (Selenium, Cypress, Playwright, etc.)
- CI/CD integration
- Test maintenance and reliability
Software Engineering
- Can they write code?
- Understanding of software development lifecycle
- Code review and quality practices
- Debugging and troubleshooting
Quality Thinking
- How they approach quality
- Balancing thoroughness with speed
- Risk-based testing
- Improving quality processes
Common Hiring Mistakes
1. Hiring Manual Testers Who Can't Code
Modern QA Engineers need to write automated tests. Don't hire manual testers who can't code—they'll become bottlenecks as teams move faster.
2. Treating QA Engineers as "Bug Finders"
QA Engineers should prevent bugs through test automation and quality processes, not just find them. Look for candidates who think about quality systematically.
3. Not Testing Automation Skills
"Tell me about testing" tests knowledge. "Write an automated test for this feature" tests skills. Focus on automation ability, not just testing knowledge.
4. Ignoring Software Engineering Skills
The best QA Engineers understand software development and can write code. They integrate testing into development workflows, not add it as an afterthought.
Red Flags
- Only talks about manual testing - Modern QA Engineers need automation skills
- Can't write code - QA Engineers need software engineering skills
- No experience with test automation - Automation is essential for modern QA
- Adversarial relationship with developers - Good QA Engineers partner with developers
- Only focuses on finding bugs - Should think about preventing bugs
- Hasn't built test frameworks - QA Engineers should build testing infrastructure
- Doesn't understand CI/CD - Tests should be integrated into deployment pipelines
What Makes QA Engineers Different from Other Roles
Understanding the distinction helps you hire the right person:
QA Engineer vs. Manual Tester
Manual testers execute test cases without writing code. QA Engineers write automated tests, build testing frameworks, and integrate testing into CI/CD pipelines. The key difference is software engineering skills—QA Engineers solve quality problems through code and automation.
QA Engineer vs. SDET
SDET (Software Development Engineer in Test) is often used interchangeably with QA Engineer, but SDETs typically have stronger software engineering backgrounds and focus more on building testing infrastructure. At some companies, SDETs contribute to production code.
QA Engineer vs. Developer
Developers focus on building features; QA Engineers focus on validating them. However, modern QA Engineers need strong coding skills for test automation. The best teams have developers write unit tests while QA Engineers focus on integration, E2E, and exploratory testing.