56 / 57 · 21 Communication & Stakeholder Management · Remote and Distributed Teams← prev⊞ allnext →☰ Read as one page
7.7Onboarding New QA Team Members Remotely
Remote onboarding is harder than in-person onboarding because new team members cannot absorb context through osmosis. Everything must be explicit.
The Remote QA Onboarding Plan
Week 1: Setup and Orientation
| Day | Activity | Owner |
|---|---|---|
| Day 1 | Tool access: JIRA, Git, CI/CD, test environments, Slack channels | QA Lead |
| Day 1 | Intro calls: meet each team member 1:1 (15 min each) | New hire |
| Day 2 | Walk through the test strategy document and decision log | QA Lead |
| Day 3 | Run the existing test suite locally. Ask questions about any failures. | Buddy |
| Day 4 | Shadow a pair testing session (observe, do not drive) | Buddy |
| Day 5 | First small task: write 2-3 test cases for a well-defined story | New hire |
Week 2: First Contributions
| Day | Activity | Owner |
|---|---|---|
| Day 6-7 | Execute manual test cases for a current sprint story | New hire + Buddy |
| Day 8 | File first bug reports. Buddy reviews for quality and tone. | New hire + Buddy |
| Day 9 | Write first automated test. Code review from QA lead. | New hire + QA Lead |
| Day 10 | Sprint review: observe and note how QA presents | New hire |
Week 3-4: Increasing Independence
- Take ownership of testing for 1-2 stories per sprint
- Participate in refinement and planning with prepared questions
- Begin contributing to test automation regularly
- First solo pair testing session (drive, buddy observes)
The Buddy System
Every new remote QA hire should have a designated buddy for their first month:
- The buddy is the first point of contact for questions
- The buddy reviews the new hire's first bug reports, test cases, and automation code
- The buddy has 30 minutes blocked daily for the new hire (this is non-negotiable)
- The buddy provides honest, private feedback on the new hire's integration into the team