Senior Full-Stack Engineer

Senior Full-Stack Engineer — ADAM (adam.ua & Adam OS)

About ADAM

ADAM (adam.ua) is an AI Agronomist for Ukrainian farmers — a farm-management product steered through an AI chat, with an in-app marketplace of verified input vendors as the monetization layer. First feature: a farmer photographs a plant, the AI diagnoses it, recommends the right product, and the farmer buys in-app. We are Year 1 (2026), pre-PMF, on a $250K pre-seed, and post-pivot: ADAM 1.0 was a classic marketplace farmers bypassed (78.8% B2B churn); in ADAM 2.0 the AI is the product and the moat. Our North-Star metric is Weekly Active Farmers on the AI Agronomist. The market is greenfield: 17,444 farms (100−5,000 ha), a $2.7B TAM, no incumbent platform — the real competitor is Viber groups and a phone call.

The role

One of four board-funded priority hires the pre-seed exists to make, alongside a CTO, PM, and Customer Success. You report to CEO Viktor Kovalchuk, then to the CTO once hired. The Year-1 team plan is seven: CEO, Product/Data, two developers, two sales managers, a CRM manager.

Your funded mandate is the customer-facing product: the ADAM 2.0 platform plus its mobile experience (farmers are smartphone-first on budget Android). You will also build inside Adam OS, our internal company operating system — [FILL IN: final split of Adam OS ownership between this role and the incoming CTO]. Same stack, two codebases, end-to-end ownership from migration to merged PR.

• First 90 days:* ship what gets the first 50 pilot farmers using the AI every week. The Q3−2026 bar: 30 weekly active farmers on the AI Agronomist, ≥10% of AI recommendations converting to marketplace requests, 25 verified vendors.

What you will ship

• On adam.ua (primary):* the photo-diagnosis flow on the Claude API (vision); the AI Agronomist chat agent (13 tool-use skills, 3-layer pgvector memory — already designed); extensions to the live quote-first Chat→Quote→Order workflow with Nova Poshta delivery; hybrid semantic search (Voyage 1024d, HNSW, RRF); the mobile experience — on a DB of 94 tables, ~170 functions, 376 migrations.

• On Adam OS (secondary, sequenced with the CTO):* already shipped: Admin/RBAC, Files + semantic search, a corpus-grounded AI Assistant, Settings, Brand, CRM/Tasks Phase 0. Your territory: Financials, Sales reporting, AI-composed Reports, Leads, a read-only Farmers mirror, Automations, Inbox, Dashboard wiring, plus the collaboration spine (comments, @mentions, activity, saved views).

How you ship

• End-to-end: SQL migration → SECURITY DEFINER RPCs → server queries → React UI → i18n → tests → PR
• Postgres schemas with RLS, audit rows on sensitive writes, self-documenting COMMENT ON metadata
• AI features on the Vercel AI SDK: tools, RBAC-scoped execution, server-enforced preview→confirm write gates, cost capture
• Every gate green: typecheck, lint, vitest, a 14-gate docs/hygiene check; skills and docs maintained as part of shipping

Tool stack

Next.js 16 (App Router) · React 19 · TypeScript 5 strict · Tailwind v4 (CSS-first) · shadcn/ui · TanStack Query v5 + Zustand + zod · Supabase (Postgres, Auth, RLS), one project per product · Vercel AI SDK — Adam OS pins one Claude Sonnet; adam.ua's agent design is multi-provider (GPT-4.1-mini/nano, Claude Sonnet, Gemini Flash; $0.38/farmer/month target) · Voyage embeddings + pgvector · next-intl (uk/en product, en/uk/ru internal) · Bun · Cloudflare R2 + Images · Vercel.

Requirements (must-have)

• Senior-level TypeScript in strict mode (any is banned by the rules contract) and production React/Next.js App Router experience
• Real Postgres depth: RLS, SECURITY DEFINER functions, migration-file-only schema changes — Adam OS is fully RPC-only; adam.ua bans client reads on protected tables
• LLM application experience — tool use, RAG/embeddings, evals; the headline deliverables are AI features
• Daily fluency building with AI coding agents — Claude Code in a rules/skills/eval-gated repo is our standard working mode
• Product ownership: you scope, build, verify in the running app, and ship without a ticket-writer above you; pre-PMF priorities shift on evidence
• Professional working English (all code, docs, PRs)

Nice to have

• Ukrainian and/or Russian — a real advantage; all regulated agronomic copy passes editorial review anyway (no blind machine translation)
• B2B marketplace, agtech, or logistics-integration background
• Playwright/scraping (two standalone scraper sub-projects feed our product and CRM data)
• Mobile (PWA or native) shipping experience

How we work

AI-native engineering, genuinely: both repos carry agent-skills infrastructure and promptfoo evals; Adam OS adds a hard .agent/rules contract, ~25 domain skills with trilingual triggers, and machine-enforced AI safety — a CI gate guarantees a model can never self-approve a write. Documentation is blocking: broken cross-references fail the commit, every table documents itself. Branch-per-task with PR review; nobody pushes to main. Culture: cite-or-refuse epistemics, ICE+S prioritization, evidence over assumption — we called 100 farmers in 19 regions and kept the finding that falsified our own hypothesis. The war is a permanent operating condition: no Russian-affiliated vendors or infrastructure, ever.

What we offer

• A funded founding-engineer seat in a greenfield market, with end-to-end ownership across two codebases
• [FILL IN: compensation range]
• [FILL IN: employment type — org plan has dev roles as contractors via Crocos; confirm contractor vs employee]
• [FILL IN: location / remote policy]