Senior SaaS Product Designer — Figma Developer Implementaition/ Handoff

BIQc is an AI-powered business intelligence platform We are looking for a senior product designer with strong Figma, UX architecture and B2B SaaS experience to complete and consolidate our remaining design work. This is not a greenfield redesign. The product is already implemented across several areas, and we have: * A live development environment. * Existing screens and user flows. * A developing Radix-based Figma component foundation. * A Tailwind-based frontend. * Existing Billing desktop/mobile designs. * An existing Homepage implementation. * Multiple Figma and implementation references that need to be consolidated. Your role is to review what currently exists, close the genuine UX/UI gaps and establish one authoritative Release 1 design and handoff source. We do not want the product unnecessarily redesigned from scratch. Initial engagement * Project Upwork contract. * Rolling module-level delivery. * Daily progress and blocker updates. * Availability for at least 2 regular overlap with the Australian team. * Opportunity for further modules following a successful R1 close-out. Initial Scope Authentication and three-day trial Review and complete: * Sign up. * Login and logout. * Email/OTP verification. * Invalid and expired OTP. * Resend verification. * Forgotten and reset password. * Session expiry. * Guest and returning-user states. * Trial activation. * Trial countdown and nearing-expiry states. * Expiry during an active session. * Returning after expiry. * Locked access and upgrade entry. * Desktop and mobile behaviour. Ask BIQc Review the existing implementation and complete the authoritative Figma experience for: * New Ask BIQc session. * Suggested questions. * Question submission. * Answer streaming. * Stop and retry. * Sources and evidence. * Follow-up questions. * Copy and feedback actions. * Loading, interruption and error states. * Usage/token-limit states. * Responsive desktop and mobile behaviour. Chat History and Projects Complete: * Conversation history. * Search. * Archive. * Delete. * Unarchive. * Empty and unavailable states. * Project creation and deletion. * Assigning conversations to Projects. * Project detail and navigation. * Responsive behaviour. Approved Release 1 connectors Review and complete the customer journeys for the approved connector set, including: * AroFlo. * Zapier. * Microsoft Outlook and Exchange. * Gmail. * Calendar. * Inbox. * Supported Merge.dev connectors that do not require BIQc-owned credentials. Required states include: * Available. * Connect. * Permission or authorisation. * Connected. * Syncing. * Failed. * Expired. * Reconnect. * Disconnect. * Permission denied. * Unsupported or support required. * Admin and Member visibility where applicable. Settings Review and finalise: * Account. * General preferences. * AI Models and Personas. * Team and Governance. Team and Governance should account for: * Owner/Admin/Member roles. * Member list. * Invitations and invite acceptance. * Suspend, revoke and remove. * Immediate access revocation. * Connector and AI-setting permissions. * Appropriate empty, validation, success and error states. Homepage and guest entry Complete the existing app-style Homepage and guest-entry direction, including: * Desktop and mobile presentation. * Guest Ask BIQc treatment. * Suggested questions or product demonstration. * Trial and login entry points. * Existing-video placement recommendation. * Clear status of any placeholder content. This is not a full marketing-site redesign. Figma and design-system requirements You will inherit the current BIQc files and component foundation. ou will be expected to: * Use the approved Radix-based component direction. * Align Figma components with the Tailwind frontend architecture. * Apply the approved BIQc colours, typography, spacing and variables. * Use existing components wherever suitable. * Create only the missing R1 variants and states. * Avoid rebuilding the entire design system unnecessarily. * Establish one authoritative Release 1 index. * Archive or clearly separate superseded designs. * Clearly label every module and flow by status. * Create a critical-path clickable prototype. * Prepare clean Dev Mode handoff. Required statuses include: * In Progress. * Ready for Product Review. * Ready for Technical Review. * Approved for Development. * Blocked — Decision Required. * Deferred. * Superseded/Archived. Required deliverables * Release 1 module and route register. * One authoritative Figma index. * Completed remaining R1 module flows. * Required desktop and mobile screens. * Loading, empty, validation, success and error states. * Critical-path clickable prototype. * Interaction and behaviour notes. * Component and asset references. * Missing-state and blocker register. * P0/P1/deferred design backlog. * Module-by-module developer handoff. * Final Release 1 design-readiness recommendation. Working method The selected designer must: * Review DEV, Figma and the approved requirements before redesigning anything. * Identify conflicts and blockers immediately. * Deliver modules progressively rather than waiting until the final day. * Provide direct Figma links with every handoff. * Ask focused product or technical questions. * Avoid inventing backend behaviour, commercial rules or unsupported features. * Maintain accurate status labels throughout the engagement. * Be comfortable taking ownership of a complex inherited design environment. Required experience * Senior-level product design experience. * Advanced Figma components, variables, variants and prototyping. * Complex B2B SaaS or enterprise-platform experience. * Authentication, billing, permissions and integration UX. * Responsive desktop/mobile product design. * Developer handoff and design QA. * Experience working with Radix UI/Themes, Tailwind or comparable component systems. * Ability to work effectively with an existing implementation. How to apply Please include: 1. Two relevant Figma examples showing complex SaaS workflows. 2. An example of inheriting and consolidating an inconsistent Figma or design system. 3. Your experience aligning Figma with Radix, Tailwind or a coded component library. 4. How you would approach the first eight hours of this engagement. 5. Your estimated hours for each major module. 6. Your availability and Australian-time overlap. 7. Confirmation that you are comfortable working from an existing product rather than redesigning it unnecessarily. Please begin your application with the words “KOALA KOALA ” so we know you have reviewed the complete brief.