Own the data plane for an offline-first mobile app: schema, security, sync, and the Edge Functions between the client and downstream services. Correctness and data integrity are the bar — a single lost write is a failure.

What you'll build

• Core Postgres schema + RLS on every user-scoped table. Append-only, event-sourced spine with correlation/version stamping on every event.
• Edge Functions (Deno/TypeScript): auth webhook, CRUD functions, a resolver service against external data sources, third-party webhook handlers.
• The sync engine and its conflict-resolution contract — last-write-wins with client_id dedup, merge strategies for structured records. You own the rules; the client implements against them.
• Storage access policies for user files; encrypted third-party tokens.
• Migration discipline, RLS-validated CI, backups/PITR.
• Production Postgres at depth — schema design,...