Job Description
đź“‹ Description
• Architect and own the backend foundation of NOA Grid AI, a live platform that already automates 500k ARR worth of solar-grid-connection paperwork and is racing toward 1 million ARR by mid-2026. You will design PostgreSQL schemas that model every nuance of German grid-operator requirements, write 26+ migrations without downtime, and harden Supabase with Row-Level-Security so installers only see their own projects.
• Build and orchestrate 87 LangGraph workflows that turn messy PDFs, photos, and form inputs into perfectly formatted grid-connection applications. You will chain Claude, Gemini, and AWS Bedrock models, design deterministic state machines, and tune prompts so that AI agents never hallucinate a cable cross-section or a fuse rating.
• Ship bullet-proof Supabase Edge Functions (18 and counting) that encapsulate business logic, call external grid-operator APIs, and trigger downstream automations. You will keep cold-start times under 300 ms, write exhaustive unit tests, and document every endpoint for frontend and AI consumers alike.
• Lead the early-2026 database migration that will split monolithic tables into a scalable multi-tenant architecture. This is not a side quest—it is the company’s next inflection point. You will draft the migration plan, rehearse rollbacks, and pair with the LangGraph team to guarantee zero data loss and zero broken workflows.
• Collaborate daily with Darshan (Director of Engineering), Jan (AI Lead), and Kirill (Full-Stack) in fully-remote, async-first rituals. You will review PRs, debate schema designs in Notion, and demo features every Friday to installers who depend on your code to get heat pumps connected before winter.
• Champion pragmatic engineering: prefer a working 80 % solution today over a perfect 100 % solution next quarter, instrument everything with logs and metrics, and refactor mercilessly when the data tells you to.
• Stay on the bleeding edge of AI engineering. When Anthropic drops a new Claude model or LangGraph releases a breaking change, you spike a proof-of-concept on Monday and roll it out to production by Thursday if it improves accuracy or cuts token cost.
• Communicate like you’re the only engineer awake in your timezone. Clear Loom videos, concise Slack threads, and exhaustive READMEs are your currency so that Berlin wakes up to green CI and zero surprises.