Workforce Scheduling & Team Management Platform
TeamPlaner
Implemented the complete frontend of a workforce scheduling platform and contributed to backend development and API integration.
- Role
- Front-End Ownership · Backend Contribution
- Focus
- Entire frontend · Day / week / month views · Scheduling business rules
- Tech stack
- TanStack Query
- Zustand
- Zod
- C#
- .NET
- Product scope
- Employee management
- Appointments
- Locations
- Availability
- Time off
- Backup employees
- Unassigned appointments
- Day / week / month views
Why this is senior work
Scheduling is business logic first. The work was turning rules about availability, time off, backups, and assignments into interactive workflows and application state, then presenting them consistently across day, week, and month views.
Key contributions
What I built
Frontend ownership
Implemented the entire frontend application.
Scheduling workflows
Implemented interfaces for scheduling, employee assignment, availability, appointments, and time-off workflows.
Complex business logic
Translated scheduling requirements and business rules into interactive frontend workflows and application state.
Calendar UI
Implemented day, week, and month scheduling views.
Backend contribution
Worked on parts of the backend and integrated the frontend with the underlying API and data flows.
Architecture
Structured the application around reusable components and a predictable data flow between the interface and the API.
Engineering challenge
Many rules, one calendar
Availability, time off, backup employees, and unassigned appointments all shape what a schedule shows and allows. I translated those rules into application state and interactive workflows, so the day, week, and month views apply them the same way.