Working hours & leave
Working hours
We operate on three time zones. Individual schedules are flexible within sensible limits.
Expectations
- Core window coverage: be online and responsive during 10:00–14:00 Beijing/Bali time (13:00–17:00 AEDT). This is non-negotiable for most roles.
- Beyond the core window: work when it suits you, as long as your commitments are met.
- 40-ish hours per week for full-time roles. We don’t clock-watch. Delivery matters.
- No weekend work expected except for on-call or pre-arranged coverage.
Deep work blocks
You’re encouraged to block out focus time when you need it. Mark your Slack status and calendar. Nobody should expect an immediate reply during your declared deep-work hours.
Time zone etiquette
- Don’t schedule meetings outside someone’s normal working hours without asking
- If a meeting needs all three zones, rotate the inconvenience — not always the same team taking the early/late slot
- Record and take notes on every meeting so the absent zone can catch up async
Leave
Annual leave
- 20 days per year, plus local public holidays
- Book ≥ 2 weeks in advance for anything longer than 2 days
- No “unlimited leave” — that tends to mean people take less, which we don’t want
- Use it. Burnout serves nobody.
Public holidays
- Observe your local country’s holidays
- Announce in
#generala week ahead so your zone’s coverage is arranged
Sick leave
- Take it. Don’t work sick.
- Notify your manager and location lead by 10:00 local
- No doctor’s note needed for ≤ 3 consecutive days
Personal / bereavement leave
- Up to 5 days, use your judgment, manager approval
- Ray approves anything beyond
Parental leave
- Follow local statutory minimum
- We top up where we can — discuss with Ray
On-call & after-hours
For SEV1 incidents (see Incident response):
- Primary on-call: [TBD — rotation TBD]
- Secondary: Ray (always)
- After-hours page → WhatsApp primary, then phone
On-call weeks get compensated with time back or a small stipend — TBD when we have a real rotation.
Overtime
If you find yourself regularly working > 45 hours, something’s wrong with the scoping or the team size. Surface it, don’t power through.