This project centers on a web platform that lets dentists and dental clinics connect quickly for both permanent and (temporary) roles. See attached Core flow • Two role-based signup paths: “Dentist Seeking Work” and “Dental Clinic Hiring.” After registration, users land in dashboards designed for their needs—dentists can build a resume-style profile, upload credentials, set availability, and manage job applications, while clinics can create a practice profile, post vacancies, and track applicants. • A job board where listings are fully searchable and filterable (location, employment type, specialty, pay range, start date, etc.) so clinics reach the right talent and dentists locate the right positions fast. • A direct, in-site messaging system that triggers once an application is sent or a clinic shortlists a candidate, keeping all hiring conversations in one place and ensuring neither party needs to share private contact details prematurely. Additional requirements – Responsive UI that feels just as smooth on a phone in the operatory as on a desktop at the front desk. – Clear separation between active, closed, and archived postings so the board stays clean. – Admin area to moderate profiles, flag or remove listings, and export basic analytics on signups and placements. – Security best practices: hashed passwords, role-based access control, GDPR-compliant data handling, and the ability for users to delete their account entirely. Acceptance criteria 1. A dentist can sign up, complete a profile, and appear in search results within five minutes. 2. A clinic can filter for “temporary” plus a specific date range and receive accurate matches. 3. A first reply via the internal messenger reaches the recipient instantly (under 3 seconds average). 4. No protected page is accessible without authentication or the proper role. 5. Codebase ships with a README that details local setup, environment variables, and production deployment steps. When we finish, I will need the production-ready source code (front-end, back-end, database schema), a seed file with test users and jobs, and deployment instructions for a common cloud host (Heroku, Vercel, or AWS Lightsail—whichever fits your stack best).