Senior SaaS Solutions Architect / Technical Lead — Multi-Tenant Workforce & Remote Workspace Platfom

Senior SaaS Solutions Architect / Technical Lead — Multi-Tenant Workforce & Remote Workspace Platform Project Type: Existing SaaS Platform Expansion Experience Level: Expert Engagement: Initial architecture and technical audit, with potential long-term implementation Initial Duration: 3–4 weeks Location: Remote Project Overview We are seeking an experienced Senior SaaS Solutions Architect / Technical Lead to assess an existing AI-enabled SaaS application and design its expansion into a scalable, secure, multi-tenant workforce management and staffing platform. The existing application includes recruitment, candidate management, AI-assisted screening, assessments, interview workflows, and employer-facing functionality. Our objective is to extend the existing platform into a comprehensive ecosystem supporting staffing marketplaces, workforce deployment, remote desktop access, virtual office collaboration, employee management, IT assistance, client management, and commercial operations. We are not looking for a complete rebuild unless a technical assessment demonstrates that it is necessary. The selected architect will be responsible for evaluating the existing architecture, recommending the appropriate technology and infrastructure, defining system boundaries, and preparing an implementation-ready technical roadmap. Proposed Platform Scope 1. Existing SaaS Assessment and Integration • Audit the existing frontend, backend, APIs, database and infrastructure. • Identify reusable modules and components. • Review current authentication and authorization architecture. • Evaluate database scalability and tenant isolation. • Identify architectural limitations, technical debt and security risks. • Recommend an integration strategy for new workforce modules without disrupting existing functionality. 2. Multi-Tenant SaaS Architecture Design a scalable platform supporting multiple independent organizations with: • Organization and workspace management. • Role-based and permission-based access control. • Secure tenant-level data isolation. • Centralized authentication and optional enterprise SSO. • Modular subscription and licensing management. • Audit logging and security monitoring. • Tenant provisioning and configurable organizational policies. • Support for independent deployment of selected services. 3. User Portals and Access Management The platform is expected to support multiple role-specific portals: Platform Administration Portal • Tenant administration. • Subscription management. • System monitoring. • Global configuration. • Security and compliance oversight. Company / Organization Portal • Employee and resource management. • Workstation allocation. • Workforce monitoring. • Projects, tasks and approvals. • Department and manager dashboards. • Reports and analytics. Client Portal • Resource requests and deployment visibility. • Assigned workforce information. • Attendance and timesheet approvals. • Project status and deliverables. • Communication and reporting. Vendor / Service Provider Portal • Resource listings and availability. • Staffing proposals. • Candidate submissions. • Contract and deployment management. • Invoice and payment status. Employee Portal • Secure workspace access. • Attendance and timesheets. • Task assignments. • Team communication. • Support requests. • Employee self-service. IT Support Portal • Device and workstation management. • Remote assistance with appropriate authorization. • Support tickets and incident management. • Session auditing and infrastructure health. Manager Portal • Live workforce dashboard. • Resource allocation and workload monitoring. • Task supervision. • Communication and support coordination. • Operational analytics. Finance Portal • Subscription billing. • Approved timesheets. • Vendor and client invoicing. • Workforce costing and financial reporting. Users may hold multiple roles and must receive access according to explicit permissions. 4. Secure Remote Workspace Design an enterprise-grade remote workspace solution using suitable open-source or commercially licensed components. Expected capabilities: • Secure remote access to assigned workstations and virtual machines. • Browser-based or native remote desktop connectivity. • Windows RDP integration. • Centralized access permissions. • Session connection and disconnection tracking. • Workstation availability and health monitoring. • Configurable clipboard and file-transfer policies. • Session audit trails. • Permission-based remote IT assistance. • Support for company-hosted and customer-hosted infrastructure. • Appropriate performance for engineering and other resource-intensive applications. Experience with Apache Guacamole, MeshCentral, RustDesk, RDP, Windows environments, and secure networking is highly desirable. The architect must assess performance, licensing, scalability, security, and operational limitations before selecting the final solution. 5. Workforce Management and Attendance • Employee and contractor profiles. • Work schedules and shifts. • Connected, active, idle and break-time tracking. • Timesheet generation and approval. • Resource utilization reporting. • Workforce availability and allocation. • Manager dashboards. • Transparent monitoring policies and configurable privacy controls. Attendance and activity data must be distinguishable from actual project productivity. 6. Virtual Office and Communication • Team presence and availability. • Department-based virtual office views. • Individual and group messaging. • Voice and video communication. • Screen sharing. • Permission-based IT assistance. • Project communication rooms. • Real-time notifications. • Team collaboration dashboards. Evaluate suitable WebRTC, signaling, TURN and messaging infrastructure. 7. Staffing Marketplace and Resource Deployment • Company and vendor registration. • Staffing requirement publication. • Resource availability and listings. • Candidate and resource matching. • Proposal submission and comparison. • Resource selection and onboarding. • Contract and assignment management. • Client and vendor coordination. • Deployment tracking. • Timesheet-linked commercial workflows. The solution should integrate with existing recruitment and assessment capabilities where feasible. 8. Project and Workforce Operations • Project creation and management. • Resource allocation. • Task assignment and tracking. • Project milestones. • Deliverable tracking. • Approval workflows. • Team utilization and workload reports. • Client-facing project visibility. 9. AI and Analytics Evaluate the architecture for: • AI-assisted candidate and resource matching. • Workforce analytics. • Automated operational summaries. • AI-assisted reporting. • Project and resource risk identification. • Knowledge-base search and assistance. • AI recommendations with appropriate human oversight. 10. Industry-Specific Integrations The architecture should allow future integration with engineering and design applications, including: • BIM and CAD software. • Project collaboration systems. • Engineering model management platforms. • Software licensing and workstation telemetry. • Project-specific productivity and delivery metrics. Industry-specific integrations should be modular and must not be mandatory for customers in other sectors. Technical Architecture Requirements The architect should evaluate and recommend: • Next.js / React / TypeScript frontend architecture. • Node.js / NestJS or other justified backend technologies. • PostgreSQL and/or MongoDB based on existing application requirements. • Redis and background processing infrastructure. • REST APIs and event-driven communication. • WebSockets and WebRTC. • Containerization using Docker. • Appropriate deployment orchestration. • Secure remote desktop gateways. • Cloud and hybrid infrastructure. • CI/CD pipelines and infrastructure as code. • Centralized logging, monitoring and alerting. • Backup, disaster recovery and high availability. • Secure secret management. • Database migration and versioning strategies. We prefer proven, maintainable technology and will not adopt unnecessary microservices or infrastructure complexity. Initial Engagement — Required Deliverables The first engagement is focused on assessment, architecture and planning. Deliverable 1 — Technical Audit Report • Existing system assessment. • Code quality and dependency review. • Database structure and performance review. • Security and access-control findings. • Infrastructure assessment. • Technical debt and risk register. Deliverable 2 — Proposed Architecture • Current-state architecture diagram. • Target-state architecture diagram. • Module and service boundaries. • Multi-tenant security model. • Recommended technology stack. • Integration strategy. • Infrastructure and deployment design. Deliverable 3 — Database and API Design • Proposed entity relationship diagrams. • Tenant and identity model. • Major API contracts. • Data ownership boundaries. • Migration and compatibility approach. Deliverable 4 — Development Roadmap • Prioritized modules and MVP scope. • Work breakdown structure. • Dependencies and milestones. • Recommended team structure. • Effort and cost estimates. • Testing and acceptance criteria. Deliverable 5 — Proof of Concept • A limited technical validation of the highest-risk integration, subject to agreed scope and budget. • Documented findings, performance considerations and next-step recommendations. Required Experience We are looking for a senior professional with: • 8+ years of relevant software engineering experience. • Demonstrated experience designing production SaaS systems. • Strong knowledge of multi-tenant application architecture. • Experience auditing existing production codebases. • Advanced backend and database design expertise. • Experience with authentication, authorization and API security. • Knowledge of scalable cloud and hybrid infrastructure. • Familiarity with CI/CD, observability and automated testing. • Experience integrating third-party and open-source services. • Ability to produce professional architecture diagrams and technical documentation. • Experience guiding engineering teams through implementation. Experience with remote desktop infrastructure, workforce management, staffing platforms, or enterprise collaboration products is a strong advantage. Working Expectations • Work collaboratively with an existing development team. • Provide clear, actionable technical recommendations. • Explain architecture trade-offs and associated costs. • Document all major decisions. • Recommend reuse of existing functionality wherever appropriate. • Establish measurable engineering quality standards. • Provide milestone-based progress reports. • Support a secure and maintainable long-term implementation. How to Apply Please include: 1. Two or three examples of production SaaS platforms you have architected or technically led. 2. Your experience with multi-tenant database design and security. 3. Your experience auditing and modernizing existing applications. 4. Any relevant experience with remote desktop, virtual workspaces, WebRTC or workforce management. 5. Your proposed approach for the initial 3–4 week audit and architecture phase. 6. Your estimated effort, availability and proposed commercial terms. Generic proposals without relevant architecture experience may not be shortlisted. We are seeking a long-term technical partner capable of making sound architectural decisions and supporting a commercially scalable product. Confidentiality: Additional technical details will be provided to shortlisted professionals through the appropriate Upwork process. All pre-contract communication and contracting will remain on Upwork.