3 Work Hours, Time Zones & Scheduling

We are remote‑first with flexible hours. Publish your working window in your Slack profile (e.g., 10:00–18:00 local time).
Maintain a daily IST overlap of ≥ 4 hours for coordination unless exempted by your manager.
Notify your manager/team when deviating from your usual window (appointments, travel, etc.).

Put your working window and time zone in your Slack profile and POM (Personal Operating Manuals).
Block deep‑work windows on your calendar; use Slack Focus/Do‑Not‑Disturb.
If you shift your hours for a week, notify your manager.

Use the shared calendar to set your working hours and OOO.
Propose meeting times with tools that display participants’ local times. Avoid habitual after‑hours booking.

Company‑wide meetings are scheduled in IST with recordings and notes shared. Live attendance is encouraged.
Decline with a note when you’re not required; suggest async updates where suitable.

Timing: Check‑in within your first hour; check‑out in your final 30 minutes. If you return later, add a short addendum.
Quality bar for updates:
- Good: “Deploy v1 section to staging; write test for edge case #142; draft RFC for data export. Blocked on S3 policy—need @ops to grant GetObject by 14:00 IST. Links: …”
- Weak: “Working on dashboard; some bugs.”
Managers: Reply to reprioritize if needed.
Contractors: Ensure updates align with timesheets and include task/PO numbers where applicable.
Context: If your focus shifts, note % split by project for that day.
Core Overlap: Aim for a predictable 4‑hour IST overlap (e.g., 12:00–16:00 IST) so teams can plan handoffs.
Calendar Hygiene: Keep your Working Hours, Out‑of‑Office, and Focus blocks updated weekly; accept/decline invites promptly.
Time‑Zone Labels: When sharing times, include the zone (e.g., “14:00 IST / 08:30 UTC”). Use calendar tools that show local time for invitees.
Split Days: If you split your day (errands/classes), post a brief mid‑day update in #check-in-check-out.
Traveling: If changing time zones for ≥3 days, notify manager with dates and your temporary working window.
Handoffs: Close your day with a short handoff note in the project channel (state, next action, owner, when you’re back online).

We use Solidtime (https://time.pihexlabs.com/dashboard) as our shared time-tracking tool.
If work is not logged in Solidtime you will not be compensated for that time.

You get paid for the hours you log.
The company uses Solidtime logs to bill clients accurately and to provide breakdowns by project and task.
Time logs help you and managers understand how long different kinds of work actually take, improve estimates, and surface obstacles or learning time.

Log your hours every working day, as you go or at least before you check out.
Always choose the correct project. If you cannot find the right project, ask your manager or post in #help-desk instead of guessing.
Use clear descriptions for each block of time, for example:

Client X – report pagination – implemented limit/offset + tests; debugging 500 error.

Mention obstacles and learning in the description when relevant (e.g., “1h reading K8s docs”, “blocked by IAM permission issue”).
When helpful, include a short Solidtime summary or screenshot in your check-out message in #check-in-check-out.

Projects should have a spec broken into tasks with estimates; Solidtime entries should map to these tasks where possible.
If you are spending time on something that is not tied to a defined task that is a warning sign. You should check before continuing.
If you are working on an approved task that is not logged in Solidtime, you may flag it by starting your description with Task:. This will be far more likely on internal projects that are not tied to a client project and can help you divide your work into different tasks (e.g., Task: Refactor export pipeline for pagination).