Department
🛠 Production
Comp Notes
L1 Salary
$30,000 to $37,000
L2 Salary
$33,600 to $47,500
L3 Salary
$44,000 to $61,500
L4 Salary
$58,000 to $79,000
L5 Salary
$75,500 to $100,000
L1 Hourly Wage
$20 to $25
L2 Hourly Wage
$22 to $32
L3 Hourly Wage
$29 to $41
L4 Hourly Wage
$39 to $53
L5 Hourly Wage
$50 to $67
Billable Target Min
80
Manual Testing
Mission 🙏
To help the production team produce the highest quality work efficiently and reliably.
Definition of Success 📈
- We discover at most one critical bug in production per project per year
- Our sites satisfy our stated site standards unless otherwise documented and agreed internally and with the client
Key Responsibilities 💪
- Manual testing for completed websites and new features across various browsers and device profiles
- Implementation & maintenance of automated testing tools
- Reviewing wireframes and visual designs to detect quality issues early
- Assisting devs and designers with creation and maintenance of site documentation
Key Skills 🤹🏽
| Skill | Roles | Level 1 | Level 2 | Level 3 | Level 4 | Level 5 |
|---|---|---|---|---|---|---|
QA Engineer | Can accurately compare a finished web page to a design comp/QA checklist and note the differences. Can test invisible functionality like Google Analytics with coaching. Needs a few passes and may miss some bugs. Can write a clear and accurate bug report using our template. | Tests rigorously and thinks of edge cases that others haven’t tried yet. Finds most bugs with a few passes. Uses the CMS to test different permutations of content.
Can guess when a bug is likely a content issue vs. when it is a code problem and note so in the report. | Knows the basics of web development and can guess when an issue is frontend, backend, or content. Avoids logging erroneous issues. Can intuit when differences between comps and pages are likely acceptable. Can test invisible functionality like Google Analytics without much coaching. Needs fewer passes to catch most bugs. | Knows a good amount about web development and can usually tell what part of the stack a bug is coming from. Understands the nuances of the application they are testing and tailors testing to each product. Understands the most common types of bugs well and can articulate why they occur. Can write own QA documentation based on a project’s UX documentation and a demo. Usually finds most issues on the first pass.
Can begin to make suggestions about where in the code a problem might lie. Checks the code for hints when encountering an infrequent/unusual problem. | Can read and understand code so they know how to best challenge a site’s bug-proofness. Has a strong intuition around what aspects of a site are likely to be the biggest problems. Understands the common types of programming bugs and security vulnerabilities and can test against them specifically. Only needs one pass to catch almost any bug.
Can write and assign issues directly to developers with recommended solutions based on the contents of the source code. Can assess independently whether an issue has to do with content, and can write a report directly for clients. | |
QA Engineer | Is actively learning about using automated tools to test sites. | Understands the different types of automated testing available. Can monitor and adjust existing automated testing setups. | Can implement at least one strategy for implementing automated acceptance/integration testing | Can implement multiple strategies for writing acceptance tests and connecting them to our continuous integration tools requiring minimal help from DevOps. | Is an expert in automated testing technology. Understands multiple platforms and approaches and when they are appropriate. Can integrate automated testing tools with a CI/CD pipeline without help. | |
QA Engineer | Knows the basic principles of web accessibility and what makes for an accessible website. Can test for keyboard accessibility. | Knows how to use at least one screen reader to test websites. Knows all the common accessibility antipatterns (keyboard traps, labels in images, etc) and can identify them on sites. Can use automated tools like AXE to analyze websites and report back to developers on issues. Can check all WCAG AA 2.1 rules which do not involve looking at actual code. | Can check the full WCAG AA 2.1 checklist including reviewing code for invisible or structural problems. Understands common solutions to accessibility issues. | Understands the qualitative experience of disabled users. Has extensively used a screen reader and knows how to use it the way a real-world user would. | Is an expert on web accessibility, knowing the WCAG criteria intimately but also understanding the qualitative experience of disabled users. | |
QA Engineer | Can articulate issues to developers accurately | Works efficiently with developers to help them replicate bugs. | Can contribute to conversations around Cantilever dev strategies based on findings in prior QA processes. | Can pair with devs to break down issues by looking at the code. | Works with our dev team to modify their practices in response to recurring problems noticed within our source code |