Founding Platform Engineer

Your job is to make Waniwani's infrastructure invisible at scale.

We launched the first insurance app inside ChatGPT. Now hundreds of companies want to deploy their own AI-native storefronts through our platform. Every one of them needs its own MCP server, its own codebase, its own distribution. All running flawlessly, all interconnected, all managed by you.

Waniwani is building the AI distribution infrastructure for the $10T services economy. We enable companies to sell quote-based services (insurance, wealth, …) directly inside LLMs, where buying decisions are moving. Think Shopify, but for services. We're building the rails for AI-native commerce.

Our ChatGPT insurance launch triggered $26B in market cap losses for the world's largest brokers in 48 hours. The press called it "the industry's ChatGPT moment." We call it Day 1.

We're past proof of concept. The product works. Now we need to run it for hundreds of customers simultaneously, each with their own MCP server, their own data pipelines, their own distribution dashboards, without the platform breaking a sweat.

This is a systems-level engineering problem. You'll own the architecture that lets Waniwani scale from dozens of deployments to thousands. Multi-tenant infrastructure. Multi-codebase orchestration. Real-time data flowing across hundreds of interconnected services. The kind of work where one bad abstraction costs you months, and one good one buys you years.

We expect 95% of your code to be written by AI. Your value isn't in typing. It's in knowing what to build, how to architect it, and when the AI got it wrong. You'll operate at the speed of someone who treats LLMs as a core part of their engineering workflow, not a novelty. The bottleneck is judgment, not keystrokes.

• Own the multi-tenant platform.Architect and maintain the infrastructure that hosts hundreds of MCP codebases. Each isolated, each configurable, all observable from a single pane of glass (or MCP).
• Build the data backbone.Design the pipelines that aggregate statistics, analytics, and performance metrics across every deployed instance. Make the data real-time, reliable, and actionable.
• Ship the core app.Work hands-on in the main Waniwani application: a Next.js/Type Script codebase with Drizzle ORM, React Query, and a modern component architecture. You'll build features that customers and internal teams use daily.
• Design for scale.Make architectural decisions that hold ti-codebase deployment strategies, database partitioning, caching layers, job queues. Whatever the problem demands.
• Automate everything.CI/CD pipelines, codebase provisioning, health monitoring, rollback systems. If a human has to do it twice, you build a system to do it forever.
• Instrument relentlessly.Logging, tracing, alerting. When something breaks at 2am across 300 instances, the system should tell you exactly where and why, before anyone notices.
• You will work directly with the CTO. The architecture is yours to shape. The stack is Type Script end-to-end.

• You've built and operated systems at real scale. You've dealt with multi-tenant architectures where tenant isolation actually matters. You've managed codebases that couldn't fit in one repo and data that couldn't fit on one machine.
• You're a senior engineer with 5+ years of production Type Script. You've been the person on-call when things break and the person who redesigns systems so they stop breaking.
• You think in systems, not features. When something works for one customer, you make it work for a thousand.
• Native or bilingual English required. French is a plus.

• Experience with multi-tenant SaaS platforms (tenant isolation, provisioning, billing)
• Built or operated big data pipelines (Kafka, Click House, Big Query, or similar)
• Deep Postgre
  
  SQL knowledge: partitioning, query optimization, connection pooling at scale
• Infrastructure-as-code experience (Terraform, Pulumi, or similar)
• Familiarity with MCP (Model Context Protocol) or LLM tool-use ecosystems
• Contributed to open-source infrastructure projects
• Experience with Next.js, Drizzle ORM, or similar…