Pocketclass Coding Assessment: Booking System Design
Assessment Overview
Welcome to PocketClass ([Link])! Our platform connects instructors with students in
sports, arts, and music, making skill development easy and accessible.
For this assessment, your primary task is to design a booking system that meets the needs of both
students and instructors, considering ease of use, scalability, and eBicient data handling. Use Airbnb
and Calendly as inspirations, as they’ve set high standards for user-centric, streamlined booking
systems.
Primary Assignment
1. System Design
• Instructor Interface: Describe how you would structure a calendar feature that allows
instructors to:
o Set available time slots by day and time.
o Edit, delete, or update availability as needed.
o View upcoming bookings made by students.
• Student Interface: Outline the student’s interaction with the system, including:
o Viewing available slots for specific instructors in real-time.
o Selecting a time slot, booking it, and receiving confirmation.
• Data Management & Booking Logic: Explain how you would structure the database (using
Firebase) to manage instructor availability, confirmed bookings, and user profiles.
o Address any measures you would implement to prevent double-booking and handle
conflicts eBectively.
o Describe how you would structure a scalable backend ([Link] + Firebase) to handle
user traBic and bookings.
2. Technical Walkthrough
• Architectural Choices: Describe how you would approach key challenges, including:
• Database Schema and Endpoints: Share a high-level view of the Firebase schema and
necessary API endpoints (CRUD operations for booking, updating availability, user
authentication).
• User Experience Considerations: Outline how you would make the booking process user-
friendly for both students and instructors. For instance, how would you streamline the booking
form, and what notifications or reminders might you include?
o Open to any innovative and out of the box ways to make the booking process eBective
and smooth for students and instructors.
• Conflict Handling Considerations: Calendar systems with multiple users can have complex
scheduling conflicts. Please detail specific methods for conflict detection and resolution (e.g.,
locking mechanisms, live availability updates, or retry queues). This provides insight into their
approach to consistency, a core part of a robust calendar system.
Bonus Points
1. Code Submission
• While optional, you can earn bonus points by submitting a functional prototype using [Link],
[Link], and Firebase. Your implementation can be basic but should reflect core
functionalities like:
o Instructor setting and updating availability.
o Student viewing and booking available slots.
o Basic validation to avoid double-booking.
Deliverables
• System Design (incl. System Flows or Diagrams if applicable): Describe the components of
the booking system.
• Technical Walkthrough: Explain key decisions and the reasoning behind your technical
choices.
• Bonus Code Submission: If you choose to submit code, provide a GitHub repo or a zip file with
a ReadMe that outlines:
o Technologies used and any libraries implemented.
o Setup instructions for running the project locally.
Evaluation Criteria
• System Design and Clarity: How eBectively does your design meet the project requirements
and provide a smooth user experience?
• Technical Depth and Problem-Solving: Are your choices thoughtful and well-justified,
particularly with regard to scalability, data management, and conflict handling?
• Creativity and Optimization: Do you bring new ideas or optimizations that add value to the
booking system?
• Optional Coding Proficiency: If code is provided, we’ll assess the quality, readability, and
functionality of your submission.