🟡 KANGAROO HEALTH
Onboarding Plan
90-day onboarding plan untuk sukses di KangarooHealth: week-by-week activities, key milestones, dan success metrics.
🚀 Onboarding Plan
Welcome to KangarooHealth
First Day
Your first day sets the tone. Come prepared, ask questions, and take notes. The goal: leave day 1 with a clear understanding of your first-week priorities.
30-60-90 Day Framework
Month 1: LEARN
┌─────────────────────────────────────────────────────────────┐
│ MONTH 1: LEARN │
├─────────────────────────────────────────────────────────────┤
│ │
│ WEEK 1-2: ORIENTATION │
│ ├── Complete HR paperwork & equipment setup │
│ ├── Meet team members 1:1 (CTO, Staff Eng, QA peers) │
│ ├── Get access to all systems (GitHub, Jira, Slack) │
│ ├── Read documentation (architecture, runbooks, QA docs) │
│ └── Set up local development environment │
│ │
│ WEEK 3-4: DEEP DIVE │
│ ├── Study KangarooHealth platform end-to-end │
│ ├── Review existing test suites and coverage │
│ ├── Shadow team during sprint ceremonies │
│ ├── Identify gaps in current QA approach │
│ └── Begin Playwright learning (if not already proficient) │
│ │
└─────────────────────────────────────────────────────────────┘Month 2: CONTRIBUTE
┌─────────────────────────────────────────────────────────────┐
│ MONTH 2: CONTRIBUTE │
├─────────────────────────────────────────────────────────────┤
│ │
│ WEEK 5-6: INITIAL DELIVERABLES │
│ ├── Take ownership of 1 test suite (e.g., API tests) │
│ ├── Fix flaky tests or improve coverage │
│ ├── Add documentation for test framework │
│ └── Submit first PR with improvements │
│ │
│ WEEK 7-8: EXPAND SCOPE │
│ ├── Build Playwright E2E test for 1 critical flow │
│ ├── Integrate tests into CI/CD pipeline │
│ ├── Establish test data management approach │
│ └── Present findings to team (show initiative!) │
│ │
└─────────────────────────────────────────────────────────────┘Month 3: LEAD
┌─────────────────────────────────────────────────────────────┐
│ MONTH 3: LEAD │
├─────────────────────────────────────────────────────────────┤
│ │
│ WEEK 9-10: STRATEGY │
│ ├── Propose QA strategy for upcoming feature │
│ ├── Lead test design for 1 major initiative │
│ ├── Mentor junior engineers on testing best practices │
│ └── Identify automation opportunities │
│ │
│ WEEK 11-12: IMPACT │
│ ├── Demonstrate measurable improvement (coverage, bugs) │
│ ├── Present roadmap for next quarter │
│ ├── Conduct knowledge transfer sessions │
│ └── Review OKRs with CTO / manager │
│ │
└─────────────────────────────────────────────────────────────┘Week-by-Week Breakdown
Week 1: Day 1-5
| Day | Focus | Deliverable |
|---|---|---|
| Day 1 | Setup, introductions | Dev environment ready |
| Day 2 | Platform overview | Understand core features |
| Day 3 | Architecture deep-dive | Complete architecture doc review |
| Day 4 | Meet the team | 1:1 with CTO, Staff Eng |
| Day 5 | First sprint ceremony | Participate in standup |
Week 2: Day 6-10
| Day | Focus | Deliverable |
|---|---|---|
| Day 6-7 | System access audit | All access granted |
| Day 8 | Review existing tests | Gap analysis doc |
| Day 9 | Shadow sprint planning | Understand sprint process |
| Day 10 | First contribution idea | Proposal for quick win |
Week 3-4: Foundation
| Focus | Activities | Success Criteria |
|---|---|---|
| Learn platform | Use app as patient/caregiver, study data flows | Can explain core patient journey |
| Learn codebase | Read test files, understand patterns | Can navigate test directories |
| Learn tools | Playwright docs, pytest tutorials | Complete Playwright course |
| Build relationships | Coffee chats with team | Names + roles + projects |
Key Systems to Access
Week 1 Access Checklist
| System | Who to Ask | Priority |
|---|---|---|
| GitHub (org access) | Staff Engineer | 🔴 Critical |
| Jira/Linear | CTO | 🔴 Critical |
| Slack/Discord | CTO | 🔴 Critical |
| AWS Console | Staff Engineer | 🟡 Important |
| Datadog/New Relic | Staff Engineer | 🟡 Important |
| Staging environment | Staff Engineer | 🟡 Important |
| Production read-only | Staff Engineer | 🟢 Nice to have |
| CI/CD (GitHub Actions) | Staff Engineer | 🔴 Critical |
Access Request Template
Hi [Name],
I need access to [system] for my QA work.
Can you help me get set up?
Thanks,
FaisalTeam Structure
Key People to Meet
| Person | Role | Why Meet | When |
|---|---|---|---|
| Noval Agnung Prayogo | CTO | Align on QA vision | Week 1 |
| Surya Dewangga | Staff Engineer | Technical guidance | Week 1 |
| QA Team | QA Engineers | Learn current approach | Week 2 |
| Backend Team | Backend Engineers | API understanding | Week 2 |
| Mobile Team | Mobile Engineers | Flutter app testing | Week 3 |
| Product Manager | PM | Prioritization insights | Week 3 |
| Clinical Team | Clinical Staff | Healthcare domain | Week 4 |
1:1 Meeting Template
┌─────────────────────────────────────────────────────────────┐
│ 1:1 MEETING STRUCTURE │
├─────────────────────────────────────────────────────────────┤
│ │
│ 5 min: Updates — what you've been learning │
│ 10 min: Questions — specific topics you need help with │
│ 10 min: Feedback — what can the team do to help you │
│ 5 min: Action items — clear next steps │
│ │
│ Questions to ask CTO/Staff Eng: │
│ • What are the biggest QA pain points? │
│ • What would success look like in 90 days? │
│ • What's the testing philosophy here? │
│ • What should I prioritize first? │
│ │
└─────────────────────────────────────────────────────────────┘Technical Onboarding
Development Environment Setup
# Required installations
- Node.js 18+ (via nvm recommended)
- Python 3.10+ (for pytest)
- Docker Desktop
- VS Code / WebStorm / PyCharm
- Git (configured with your name/email)
# Clone repositories
git clone git@github.com:kangaroohealth/backend.git
git clone git@github.com:kangaroohealth/mobile.git
git clone git@github.com:kangaroohealth/qa-automation.git
# Install dependencies
cd qa-automation && npm install && npm install -D playwrightArchitecture Reading List
| Document | Where to Find | Priority |
|---|---|---|
| System Architecture | Confluence/Notion | 🔴 Critical |
| API Documentation | Swagger/OpenAPI | 🔴 Critical |
| Device Integration Guide | Confluence | 🟡 Important |
| Security & Compliance | Confluence | 🟡 Important |
| CI/CD Pipeline | GitHub Actions | 🟡 Important |
| Test Strategy Doc | GitHub README | 🟡 Important |
Success Metrics
30-60-90 Day Deliverables
| Milestone | Target | Evidence |
|---|---|---|
| Week 2 | Environment ready | All systems accessible |
| Week 4 | Platform understanding | Can explain patient journey |
| Week 6 | First PR merged | Your code in main |
| Week 8 | Playwright competence | Can write E2E tests independently |
| Week 12 | QA initiative ownership | Leading 1 test strategy area |
Self-Assessment Checklist
┌─────────────────────────────────────────────────────────────┐
│ 30-DAY SELF-ASSESSMENT │
├─────────────────────────────────────────────────────────────┤
│ │
│ Can I explain KangarooHealth's core value proposition? │
│ □ Yes □ Partially □ No │
│ │
│ Have I met everyone on the team? │
│ □ Yes □ Partially □ No │
│ │
│ Can I navigate the codebase and find tests? │
│ □ Yes □ Partially □ No │
│ │
│ Have I written any tests? │
│ □ Yes □ In progress □ No │
│ │
│ Do I understand the CI/CD pipeline? │
│ □ Yes □ Partially □ No │
│ │
│ Have I identified 3+ gaps in current QA approach? │
│ □ Yes □ Partially □ No │
│ │
└─────────────────────────────────────────────────────────────┘Common Onboarding Pitfalls
🚩 Things to Avoid
| Mistake | Why It's Bad | Better Approach |
|---|---|---|
| Working in isolation | Miss context, duplicate effort | Ask questions early |
| Trying to change everything | Alienates team, misses context | Learn first, then improve |
| Avoiding the CTO | Miss strategic direction | Regular 1:1s |
| Ignoring healthcare domain | Can't contextualize testing | Study HL7/FHIR basics |
| Skipping documentation | Knowledge stays in your head | Document as you learn |
✅ Best Practices
| Practice | Benefit |
|---|---|
| Take extensive notes | Capture context, show organization |
| Ask "dumb" questions early | Day 1 questions are free |
| Over-communicate | Team knows your progress |
| Shadow everything | Learn by watching |
| Show initiative on quick wins | Build credibility |
| Regular 1:1s with CTO | Stay aligned on vision |
First Week Checklist
Day 1
- Complete HR paperwork
- Get laptop and equipment
- Set up email and Slack
- Meet CTO (brief intro)
- Meet Staff Engineer (technical intro)
- Set up dev environment
- Join all relevant Slack channels
- Read company wiki/Notion
Day 2-3
- Complete security training
- Get GitHub access
- Clone repositories
- Run existing tests locally
- Study platform (as patient/caregiver)
- Read architecture docs
Day 4-5
- Attend first standup
- Attend sprint planning (if applicable)
- Meet QA team members
- Review existing test coverage
- Identify 3 quick wins
- Schedule 1:1 with CTO
Resources
Internal Resources
| Resource | Description | Access |
|---|---|---|
| Slack | Day-to-day communication | #engineering, #qa, #general |
| Confluence/Notion | Documentation | Link from welcome email |
| Jira/Linear | Project tracking | Request from CTO |
| GitHub | Code and tests | Request from Staff Eng |
| Runbooks | Operations procedures | In Confluence |
External Learning
| Resource | Why | Priority |
|---|---|---|
| Playwright docs | Primary testing tool | 🔴 Critical |
| pytest docs | API testing | 🟡 Important |
| HL7/FHIR basics | Healthcare standards | 🟡 Important |
| HIPAA compliance guide | Healthcare regulation | 🟡 Important |
Action Items
- Day 1: Complete all HR and setup tasks
- Week 1: Meet CTO, Staff Engineer, QA team
- Week 1: Get all system access
- Week 2: Read architecture and platform docs
- Week 2: Run existing tests, understand coverage
- Week 3: Identify your first quick-win contribution
- Week 4: Submit first PR
- Week 6: Complete Playwright proficiency
- Week 8: Lead test strategy for 1 feature
- Week 12: Present 90-day achievements to CTO
Edit on GitHub
Last updated on