Senior Headless Commerce & Odoo Integration Architect (BFF / Node / Typesense)

Summary & Project Context:We are a slim, fast-moving e-commerce framework business based in Switzerland. We are currently migrating our entire multi-shop ecosystem (including a high-volume sports equipment store and multiple premium single-product niche brands) into a modern, fully decoupled Headless Architecture.Our Tech Stack: Astro / React / Tailwind on the frontend $\rightarrow$ Connected via GraphQL to a dedicated BFF (Node.js/Hono/GraphQL Yoga) $\rightarrow$ Synchronized with Odoo 19 on the backend.To eliminate performance bottlenecks, we are seeking a Senior Headless Commerce Architect. You are NOT here to build native Odoo apps or standard views. You are here to design the orchestration layer (BFF), offload heavy frontend operations from the ERP, and enforce strict data contracts between Odoo 19 and our async frontend team.Your Core Responsibilities (The 5 Architecture Laws):Enforce the BFF Law: Design and maintain the Backend-for-Frontend layer (Node/Hono/GraphQL Yoga). Direct frontend access from Astro to Odoo 19 is strictly forbidden to prevent tight coupling.Data Contract Architecture: Build and validate versioned data contracts (e.g., via Zod schemas) within the BFF, including strict multi-language fallbacks (DE/FR/IT/EN for the Swiss market) and explicit validation states.Prop Sparsity Rule: Optimize payloads for Astro Server Islands. Ensure only small, serializable identifiers (e.g., product/variant IDs) are passed as props to dynamic islands—never pass raw, heavy product JSON blocks into the browser.Search & Facet Offloading: Protect Odoo from heavy live queries. Implement and maintain a decoupled search engine stack (Typesense/Meilisearch) connected to the BFF for all global search and interdependent faceted filtering. Odoo must only be touched for transactional operations (checkout, order creation, final stock confirmation).Template Governance: Maintain a unified multi-shop white-label core. Shop-specific logic (e.g., custom variant matrices) must be strictly isolated via toggleable modules—never hardcoded into the global core template.Requirements:6+ years of backend/infrastructure architecture experience with a proven track record in high-volume Headless Commerce.Deep understanding of Odoo ORM, database relations (product variants, attributes), and backend API capabilities (JSON-RPC/REST).Expert level in building ultra-fast BFF layers (Node.js, TypeScript, Hono, Fastify, or similar).Hands-on experience setting up external search servers (Typesense, Meilisearch, or Algolia) and real-time syncing pipelines (Webhooks/Cron).High structural discipline: We value clean, readable code and manage our entire engineering process strictly in writing.Application Question (To filter out automated copy-paste agencies):To be considered for an interview, please start your application with the phrase "BFF COMMERCE" and briefly answer this question:How would you architect the real-time synchronization between Odoo 19 and a decoupled search engine (like Typesense) to ensure stock updates are reflected instantly during a high-traffic flash sale without bottlenecking Odoo's database performance?