🟡 SEVIMA
Onboarding Survival Kit
30-60-90 day plan, key stakeholders, quick wins, cultural adaptation notes, dan political landscape mapping untuk hari pertama di SEVIMA.
🚀 Onboarding Survival Kit
Konteks Freelance
Sebagai freelancer 3 bulan, Anda punya waktu terbatas untuk membuktikan value. Tidak ada masa honeymoon. Hari pertama = hari kerja. Plan ini memastikan Anda deliver cepat dan build trust early.
30-60-90 Day Plan
📅 Day 1-30: LEARN & Quick Win
Goal: Pahami codebase, deliver 1 quick win, build trust awal.
| Minggu | Focus | Deliverable |
|---|---|---|
| 1 | Environment setup, codebase deep-dive, stakeholder intro | Dev env running, first PR (kecil) |
| 2 | Domain understanding, existing service mapping | Architecture documentation draft |
| 3 | Start main task (sesuai scope kontrak) | Design document + prototype |
| 4 | Implementation sprint 1 | Working code + unit tests |
Quick Wins Hari Pertama:
- Fix 1 bug kecil — tunjukkan Anda bisa navigate codebase
- Setup linting/formatting yang belum ada
- Tambahkan 1 test yang missing
- Improve 1 README yang outdated
Prinsip Quick Win
Quick win bukan untuk show off. Ini untuk build trust dan membuktikan Anda bisa work independently. Pilih yang low-risk, high-visibility.
📅 Day 31-60: BUILD & Demonstrate
Goal: Major deliverable #1, weekly demos, build momentum.
| Minggu | Focus | Deliverable |
|---|---|---|
| 5 | Core implementation | Production-ready service v1 |
| 6 | Integration + testing | Integration tests, load tests |
| 7 | Security + monitoring | OWASP checklist, Grafana dashboard |
| 8 | Staging deployment | Deployed + demo to stakeholders |
Key Activities:
- Weekly demo ke lead engineer (15 min, recorded)
- Pair programming session 1x/minggu (knowledge sharing)
- Architecture Decision Record per major decision
- Bi-weekly written status update ke stakeholders
📅 Day 61-90: DELIVER & Transfer
Goal: Production deployment, documentation complete, knowledge transfer.
| Minggu | Focus | Deliverable |
|---|---|---|
| 9 | Production deployment | Blue-green deploy, monitoring live |
| 10 | Performance tuning | Benchmark report, optimization |
| 11 | Documentation sprint | ADRs, runbooks, API docs complete |
| 12 | Knowledge transfer + handover | Recorded sessions, handover doc |
End-of-Contract Deliverables:
- Production service deployed & stable
- Test suite (unit + integration + load)
- Documentation package (ADRs, runbooks, API docs)
- Knowledge transfer recordings (Loom)
- Handover document with next steps
- Performance benchmark report
Key Stakeholders to Map
Stakeholder Matrix
| Role | Nama (estimasi) | Importance | Strategy |
|---|---|---|---|
| Decision Maker | CFO/VP Eng | ⭐⭐⭐⭐⭐ | Impress di demo, deliverable-focused |
| Tech Lead | Lead Engineer | ⭐⭐⭐⭐⭐ | Collaborate daily, respect expertise |
| Peer Engineers | Tim engineering | ⭐⭐⭐⭐ | Knowledge share, pair programming |
| HR/Admin | Shafa Amelia | ⭐⭐⭐ | Payment, compliance, good terms |
| Product | Product Manager | ⭐⭐⭐ | Understand requirements, manage scope |
First Week Meeting Checklist
- 1-on-1 dengan hiring manager: align expectations, success criteria
- 1-on-1 dengan tech lead: understand code standards, workflow
- Team standup observation: understand dynamics, communication style
- Codebase tour dengan senior engineer: key modules, pain points
- Product demo: understand user journey end-to-end
Cultural Adaptation Notes (dari Research)
SEVIMA Culture CHEAT SHEET
| Aspek | Insight | Adaptasi |
|---|---|---|
| Jam kerja | 7 jam/hari (08:00-16:00) | Respect batasan, jangan overtime tanpa alasan |
| Communication | Kekeluargaan, informal | Friendly tapi tetap professional |
| Engineering | Code review, TDD culture | Contribute ke review, tulis tests |
| Management | Top-down keputusan (3.0 rating) | Pick battles wisely, focus on deliverables |
| Documentation | Kurang, tribal knowledge | Buat documentation = immediate value-add |
| Stack | PHP legacy + Go baru | Respect PHP devs, don't trash legacy code |
Do's & Don'ts
✅ DO:
- Tunjukkan initiative tanpa diminta
- Document everything (ini rare skill di sana)
- Ask questions — tunjukkan genuine interest
- Share knowledge — pair programming, code review
- Respect existing code — even if it's messy
❌ DON'T:
- Kritik arsitektur lama secara publik
- Compare dengan tempat kerja sebelumnya
- Ambil credit sendirian — highlight team contribution
- Promise yang tidak bisa deliver
- Terlalu agresif push perubahan di minggu pertama
Emergency Playbook
Jika Minggu Pertama Terasa Salah
| Situasi | Action |
|---|---|
| Scope tidak sesuai proposal | Meeting dengan decision maker, clarify scope, update kontrak |
| Codebase jauh lebih berantakan dari expected | Adjust timeline, communicate trade-off |
| Tim hostile/unwelcoming | Give it 2 minggu, jangan reactive |
| Tidak ada dev environment/tools | Setup sendiri, document langkahnya |
| Micro-managed padahal di-sell "autonomous" | Set boundary: "Saya deliver weekly, report weekly" |
Kapan Harus Escalate
ESCALATE jika:
⚠️ Scope berubah >30% tanpa discussion
⚠️ Payment terlambat >7 hari
⚠️ Lingkungan kerja hostile/abusive
⚠️ Diminta melakukan sesuatu yang unethical
JANGAN ESCALATE untuk:
✅ Codebase berantakan — fix it, that's your value
✅ Rekan kerja lambat respond — follow up professionally
✅ Tools/infra kurang — setup sendiri
✅ Miscommunication kecil — klarifikasi langsungEdit on GitHub
Last updated on