Duty Doctor Roster

Additional rule: Any doctor who remains unassigned after mandatory shift allocation should be assigned to the Day Shift.

• Generate the roster monthly.
• A doctor can work only one shift per day.
• A doctor can work a maximum of six shifts per week.
• Weekly offs are mandatory and cannot be overridden.
• Approved leave blocks all shift assignment for that doctor on that date.

Seed the roster with 4 approved leave days on the dates below. These doctors must be treated as unavailable on their leave date (same as weekly off). Do not assign any shift to them on these days.

Your UI should display these leaves on the calendar. Admins may add more leave days later; generation must re-run with updated availability.

Eligible: Dr. Meera Kapoor, Dr. Priya Sharma, Dr. Kavya Menon

Not eligible: Dr. Rohan Khanna, Dr. Aditya Nair, Dr. Imran Siddiqui

Distribute OBGYN duties equally among eligible female doctors.

Applies to everyone except Dr. Rohan Khanna. After a Night Shift, the next working day can only be an Afternoon Shift or an off day. Morning, Day, and OBGYN shifts are not allowed the day after a night.

Consecutive Night shifts are not allowed for any doctor except Dr. Rohan Khanna.

Maximum 1 shift per day and 6 shifts per week for every doctor.

Apply constraints in this order:

1. 1. Gender restrictions
2. 2. Weekly offs
3. 3. Approved leave days
4. 4. One shift per day rule
5. 5. Maximum 6 shifts per week
6. 6. Fixed Night shift allocation for Dr. Rohan Khanna
7. 7. Dr. Imran Siddiqui’s restrictions
8. 8. Post-night recovery rule
9. 9. No consecutive Night shifts
10. 10. Equal Night shift distribution
11. 11. Equal OBGYN duty distribution
12. 12. Assign remaining available doctors to the Day Shift

• Day 1: Night Shift
• Day 2: Afternoon Shift or off
• Day 3: Resume normal eligible duties

Expect difficult scheduling around weekends, female-only OBGYN coverage, and recovery windows — especially Fridays through Sundays.

• If 2 doctors are unavailable → remove OBGYN Shift (keep Morning, Day, Afternoon, Night).
• If 3 doctors are unavailable → remove OBGYN and Day Shifts (keep Morning, Afternoon, Night).
• Unavailable = weekly off, leave, recovery block, ineligible shift, weekly limit reached, same-day conflict, or consecutive-night block.
• When removing shifts, retain in order: Night Shift → Morning Shift → Afternoon Shift → Day Shift → OBGYN Shift.

• Use Node.js packages only on the backend (npm). No Python microservices or OR-Tools for this take-home.
• Use raw SQL queries against Supabase/PostgreSQL — no ORM tools (no Prisma, Drizzle, TypeORM, Sequelize, etc.).
• Do not integrate AI/LLM APIs into the roster app (no OpenAI, Claude, Gemini, etc. at runtime).
• AI-assisted coding tools (Cursor, Copilot, etc.) are permitted while building — the submitted app must not call AI services.
• Persist all roster data in Supabase (PostgreSQL). Provide your schema SQL and seed scripts.
• Generate a real monthly roster stored in the database — not hard-coded JSON or a mock-only UI.
• Frontend must be editable: admins can manually assign, change, or clear any doctor on any shift for any day.
• Manual overrides must be saved to Supabase and survive page refresh (set is_manual_override / source=manual).
• Re-generation must not silently overwrite manual overrides unless the user explicitly chooses to reset that day or month.

• Node.js + TypeScript API using raw SQL (no ORM) that generates a valid monthly roster and writes rows to Supabase.
• Supabase schema + seed data (doctors, shifts, 4 leave days) — extend the reference schema as needed.
• React UI: month calendar/grid showing the real persisted roster.
• Per-day, per-shift editing: change doctor, clear slot, or mark shift inactive (reduced staffing).
• Manual overrides saved immediately to Supabase; show visual indicator for overridden cells.
• “Generate roster” action for a month; warn before overwriting non-manual assignments.
• Validation toasts/errors when a manual pick breaks scheduling rules (optional override with note).
• No AI/LLM runtime integration in the submitted application.
• README: setup, env vars, algorithm, and how manual overrides interact with re-generation.
• Deploy (Vercel + Supabase) with a public GitHub repo.

Apply on the careers page under Full Stack Developer. You will receive a Test ID and 24-hour deadline. Submit your repo and deployment link via the submission form.