TITLE: Full-Stack Developer — AI-Powered Platform (Web + Mobile + Backend) We are building a multi-language AI platform with a web dashboard, mobile app, containerized backend, and third-party service integrations. Details shared after screening. ━━━━━━━━━━━━━━━━━━━━━━ ABOUT THIS ROLE We are looking for a skilled full-stack developer — or a small coordinated team of 2–3 — to build a production-grade AI platform from complete design prototypes. The full project brief, architecture, and prototypes will be shared only with shortlisted candidates. To be considered, you must complete a short sample task that closely mirrors the kind of work this project involves. This tells us far more than a portfolio link. The sample task is unpaid but takes under 3 hours for the right developer. We use AI coding tools (Claude Code, Cursor AI) heavily. Developers who are fluent in AI-assisted workflows will complete this project on time. ━━━━━━━━━━━━━━━━━━━━━━ SKILLS WE NEED Next.js 14, React Native (Expo), Node.js + Express, TypeScript, PostgreSQL, Redis, Docker + Docker Compose, WebSocket (Socket.io), Stripe API, REST API design, i18n + RTL layout, Claude Code CLI, Cursor AI, CI/CD (GitHub Actions), Third-party API integration ━━━━━━━━━━━━━━━━━━━━━━ SAMPLE TASK — COMPLETE THIS TO BE SHORTLISTED Build a small working demo that demonstrates the core skills this project requires. Submit a GitHub repo link and a short Loom screen recording (under 5 minutes) showing it works. All five tasks below are required. TASK 1 — Live dashboard with real-time data [Web] Build a simple Next.js dashboard page that displays at least 3 live counters (e.g. requests made, tokens used, active connections). The counters must update automatically every 10 seconds by fetching from a small API endpoint you also write. No page refresh allowed — updates must appear live. Style it cleanly with Tailwind CSS. Demonstrates: Next.js 14, API polling or WebSocket, Tailwind CSS, real-time UI updates TASK 2 — Mobile screen with approve / reject flow [Mobile] Build one React Native (Expo) screen that shows a list of 3–5 messages fetched from a mock API. Each message has an AI-generated summary (hardcode the text). The user can tap Approve or Reject. Approved messages move to a "Handled" section. Rejected messages are removed. Must work on iOS and Android. Demonstrates: Expo, list state management, API fetch, conditional UI sections TASK 3 — Docker Compose multi-service stack [DevOps] Write a docker-compose.yml that starts three services: your Next.js app, a small Express API, and a PostgreSQL database. All three must connect to each other within the Docker network. "docker compose up" must be the only command needed. Include a .env.example file. Demonstrates: Docker Compose, multi-service networking, environment variable management TASK 4 — Multi-language with RTL support [i18n] Add a language switcher to your Task 1 dashboard with at least 3 languages: English, one RTL language (Arabic or Hebrew), and one other. All visible text must switch. The RTL language must correctly flip the page layout. Language preference must persist across page refreshes. Demonstrates: next-intl or react-i18next, RTL layout handling, preference persistence TASK 5 — Stripe metered billing flow [Backend] Build a page with a "Start Session" button and an "End Session" button. When started, a timer begins and running cost is shown ($0.02/second for demo). When ended, the final cost is displayed and a Stripe payment intent is created for that amount using Stripe test mode. Show the payment intent ID on screen. Demonstrates: real-time billing UI, Stripe API integration, per-second cost calculation ━━━━━━━━━━━━━━━━━━━━━━ HOW TO APPLY 1. Submit your GitHub repo link containing all 5 sample tasks 2. Submit a Loom screen recording (under 5 minutes) showing all 5 tasks working 3. Describe your Claude Code or Cursor AI workflow in 2–3 sentences 4. Solo or team? If team: who handles web / mobile / backend / DevOps? 5. What is your realistic availability over the next 7 days (hours per day)? Applications without a working GitHub repo and Loom recording will not be reviewed. A rough but functional demo beats a polished incomplete one.