Full-Stack Developer for AI-Powered Talent Management Platform with Voice AI and SaaS Architecture

##Project Overview We are looking for an experienced full-stack developer or development team to design and develop a modern, web-based talent management and workforce operations platform for an IT staffing and technology services business. The platform will help manage employees, client deployments, projects, attendance, leave, skills, performance, feedback, and workforce availability. It should also identify employee performance concerns early, help understand the reasons, and track improvement before issues escalate with clients. An important part of the project is an **AI-powered voice assistant** that allows users to speak naturally, ask questions, retrieve information, and perform permitted actions within the platform. The system must be built with a **SaaS-ready architecture from the beginning**, so it can eventually be offered as a subscription-based product to multiple staffing companies and their clients. We do not want a one-off application that would need to be rebuilt to support multiple organizations. ## 1. Required User Roles and Workspaces The application should have separate workspaces with role-based access and clearly defined data permissions. ### A. Platform Administrator / Staffing Company Admin The administrator should have access to the staffing company's overall operations, including: - Employee management and onboarding - Client accounts and client-specific teams - Employee deployment and allocation - Attendance, leave, and availability - Skills, certifications, and training - Projects, deliverables, and blockers - Performance tracking and improvement plans - Client feedback and employee development - Reports, dashboards, and analytics - User management, permissions, and system settings ### B. Client Workspace: Director and Manager Access The client workspace must support a hierarchy of users, especially **Directors and Managers**, with different levels of visibility. **Director access** Directors should be able to view consolidated information across the client organization and its departments or teams, including: - Overall workforce and deployment summaries - All relevant managers and the teams they oversee - Employee performance and quality indicators - Project status, delivery progress, and open blockers - Feedback submitted by managers - Employees requiring attention or intervention - Department-wise reports and workforce availability - Historical trends and management-level dashboards Directors should have a high-level view across the areas they are authorized to oversee, without needing to manage each employee individually. **Manager access** Managers should only see the employees, teams, projects, and departments assigned to them. They should be able to: - View their respective employees and assignments - Track performance, work progress, and deliverables - Review skills and availability - Submit employee feedback and raise concerns - Record blockers and request support - Create or update improvement actions where authorized - Monitor follow-ups and review progress - Generate reports for their own teams Managers must not automatically gain access to other managers' teams. Directors should have broader visibility based on their assigned organizational scope. The system should support configurable reporting relationships and permissions rather than hardcoding one fixed hierarchy. ### C. Employee Workspace Employees should have access to their own relevant information, including: - Personal and professional profile - Current client deployment and project details - Skills and certifications - Attendance and leave requests - Availability and assignment information - Feedback and development goals - Assigned tasks, deliverables, and blockers - Improvement plans or follow-up actions, where applicable Employees must not be able to access another employee's private information unless explicitly authorized. ## 2. Core Platform Modules The platform should include the following modules: **Employee and Talent Management** - Employee records, onboarding, roles, and employment details - Skills, experience, certifications, and training - Employee status and availability **Client and Deployment Management** - Client accounts, departments, teams, and projects - Employee allocation and deployment history - Assignment start/end dates and allocation status **Attendance, Leave, and Availability** - Attendance records and leave requests - Approval workflows - Employee availability and upcoming deployment gaps **Performance and Quality Management** - Performance indicators and feedback - Delivery, technical capability, communication, and reliability tracking - Early identification of performance concerns - Improvement plans, assigned actions, follow-ups, and closure - Historical performance records and trends **Projects, Work, and Blockers** - Project and team dashboards - Deliverable status and progress - Blockers, dependencies, and escalation tracking **Feedback and Reporting** - Client-to-staffing-company feedback workflows - Feedback follow-up and resolution tracking - Role-specific dashboards and reports - Filters, exports, and historical reporting The system should support a workflow such as: Identify a concern → Understand the reason → Plan an intervention → Assign actions → Follow up → Review results → Close the concern. ## 3. AI-Powered Voice Assistant A major requirement is an integrated AI voice assistant available within the relevant user workspaces. Users should be able to record or send a voice message in natural language. The system should understand the request, retrieve the appropriate information, and perform an action when authorized. The experience should support both voice input and text-based responses, with spoken responses where appropriate. **Example requests** Directors: - "Give me an overview of employee performance across all departments." - "Which teams have unresolved delivery issues?" - "Summarize the concerns raised by managers this month." Managers: - "Show me the employees assigned to my team." - "Which employees have upcoming availability?" - "Summarize the open blockers for my project." - "Create a follow-up action for this performance concern." Employees: - "How many leave days are available to me?" - "Show my current assignment." - "What feedback have I received?" - "Help me submit a leave request." Staffing company administrators: - "Find available employees with GenAI and AWS experience." - "Show pending leave approvals." - "Which client deployments need attention?" These are illustrative examples. The final list of voice commands and actions should be agreed during requirements and architecture design. **Expected voice AI capabilities** - Voice recording and audio upload - Speech-to-text transcription - Natural-language intent understanding - Context-aware answers based on authorized platform data - Integration with backend APIs to retrieve information and perform actions - Text and spoken responses - Support for confirmations before sensitive or consequential actions - Clear handling of unclear requests, errors, and unavailable information - Conversation and action history, subject to agreed privacy and retention policies The assistant must understand the user's role and permissions before retrieving data or executing actions. It must never bypass normal application authorization or expose another client's or employee's restricted information. Actions such as submitting requests, updating records, or changing assignments must use validated backend workflows. The assistant should clearly distinguish between an action being suggested, awaiting confirmation, and successfully completed. The architecture should allow speech recognition, language models, and text-to-speech providers to be changed in the future without rebuilding the entire application. ## 4. SaaS Architecture and Scalability The application must be designed for future commercial SaaS use, not just for one staffing company. **Multi-tenant architecture** - Support multiple independent staffing companies or organizations. - Each organization should have its own users, employees, clients, projects, settings, and records. - Support multiple client organizations and departments within each staffing company. - Enforce strict tenant-level data isolation. - Allow organization-specific configuration, branding, roles, and permissions where required. - Support centralized platform administration without exposing tenant data improperly. - Design for subscription plans, usage limits, and billing integration in a future phase. - Allow future onboarding of new organizations without requiring separate application deployments for every customer, unless an isolated deployment is intentionally configured. **Technical architecture** Please propose an architecture that covers: - Frontend and backend separation - Secure API design - Database structure and tenant isolation strategy - Authentication, authorization, and role/permission management - Organization, client, department, manager, and employee relationships - AI voice service and model-provider integration - Background jobs, notifications, and audit logs - File and document storage, where required - Error handling, monitoring, backups, and recovery - Deployment environments and CI/CD - Scalability and future integration options We expect the developer to produce an architecture diagram and a database/entity relationship design before major implementation begins. The design should explain how tenant isolation and the Director → Manager → Employee hierarchy will work. The architecture should also make it possible to introduce future features such as subscription billing, usage metering, additional AI agents, external HRMS integrations, and mobile applications. ## 5. UI/UX Requirements - Modern, clean, enterprise-grade interface - Responsive design for desktop, tablet, and mobile browsers - Separate dashboards based on user role - Easy navigation across modules - Clear charts, tables, filters, and status indicators - Useful notifications and action-oriented dashboards - A simple, accessible voice interaction interface - Consistent design system and reusable components The product should feel like a professional workforce management platform rather than a basic employee database. ## 6. Preferred Technical Expertise Please recommend the most suitable stack for a secure and maintainable SaaS product. Relevant experience may include: - React / Next.js and TypeScript - Node.js with NestJS, Express, or an equivalent backend framework - PostgreSQL or another suitable relational database - Secure authentication and role-based access control - Multi-tenant SaaS application architecture - AI/LLM API integration and tool/function calling - Speech-to-text and text-to-speech integration - Cloud deployment, CI/CD, logging, and monitoring - Automated testing and API documentation We are open to alternative technologies if you can explain why they are a better fit for the requirements. ## 7. Expected Deliverables 1. Requirements clarification and technical specification 2. System architecture diagram 3. Database schema / entity relationship diagram 4. Tenant isolation and role-permission design 5. UI/UX wireframes and approved designs 6. Working web application with the agreed modules 7. Director, Manager, Employee, and Staffing Company Admin workspaces 8. Integrated AI voice assistant with agreed actions 9. Backend APIs and database implementation 10. Testing, bug fixing, and security checks 11. Deployment to the agreed hosting environment 12. Technical documentation and setup instructions 13. Source code and repository handover 14. Knowledge-transfer session and post-launch support ## 8. Development Approach We prefer an iterative development process with milestones: - Phase 1: Requirements, architecture, and database design - Phase 2: UI/UX and core application foundation - Phase 3: Authentication, tenant isolation, and role permissions - Phase 4: Employee, client, deployment, and operational modules - Phase 5: Performance, feedback, dashboards, and reports - Phase 6: AI voice assistant and approved action integrations - Phase 7: Testing, security review, deployment, and handover The architecture should be reviewed and approved before extensive development. We expect regular demonstrations and working software at agreed milestones. ## 9. What to Include in Your Proposal Please provide: - Relevant examples of SaaS or workforce management applications you have developed - Your experience with multi-tenant architecture and role-based permissions - Your approach to implementing the Director/Manager/Employee hierarchy - Your proposed AI voice technology and how it will execute authorized actions - Your recommended technical stack and architecture - Estimated timeline and milestone breakdown - Fixed-price quote or milestone-based estimate - Ongoing hosting, AI usage, and maintenance costs, where applicable - Team composition and the person responsible for architecture - Any assumptions, dependencies, or requirements that need clarification **Important:** We are looking for someone who can think beyond individual screens and features and design the right foundation for a secure, scalable SaaS product. Please explain how you would approach the architecture and data permissions, not just how quickly you can build the UI. We would prefer to begin with a clearly defined scope and architecture, followed by milestone-based development.