Flutter Takeover Sprint : UI Links and AI Engine Integration

Project Overview & Role We are entering a high-velocity development sprint to finalize and deploy RapScene AI, a game-changing music platform that enables hip-hop creators to produce, target, and monetize their music globally. The core architectural foundation is set; we now need an elite, autonomous Full-Stack AI Engineer / Software Architect to execute the final push to cross the finish line. Key Responsibilities Finalize AI Orchestration: Complete the integration of our core AI models, optimizing for low-latency lyric generation, automated vocal processing, and smart track tagging. Optimize Global Infrastructure: Refine backend routing pipelines to handle worldwide traffic while managing regional user preferences and high-yield ad localization. Bridge Backend to Frontend: Polish high-performance, secure APIs to ensure a flawless connection between the client interface and our AI processing layer. Streamline Production Deployment: Eliminate system bottlenecks, implement robust error handling for heavy audio rendering, and push the platform to a production-ready state. Technical Requirements AI & Audio Systems: Proven experience deploying LLMs and handling digital signal processing (DSP) or audio framework integrations. Full-Stack Mastery: Expert-level command of scalable backend architectures (Python/FastAPI or Node.js) and database management (including Vector DBs). DevOps & Cloud Scale: Deep familiarity with containerized deployments (Docker) and major cloud infrastructure (AWS/GCP) optimized for heavy media scaling. Sprint Mentality: Ability to audit an existing codebase rapidly, identify critical-path items, and write clean, production-grade code under a tight schedule RapScene AI handles heavy, concurrent audio rendering combined with real-time LLM orchestration. Briefly describe your architectural approach to managing a user's request that simultaneously generates AI lyrics via an LLM, applies automated vocal effects/DSP, and routes the final audio based on regional preferences. How would you structure the backend to prevent API timeouts, minimize latency, and handle heavy processing spikes during a high-traffic sprint