Full-Stack Developer (AI-Native)

Welcome back!Don't have an account? Sign upContinue with GoogleContinue with LinkedInorEmailPasswordForgot password?LOG INSend a MessageTypeTitleDescriptionCancelSendFOR EMPLOYERSLOG INSIGN UPView all jobsFull-Stack Developer (AI-Native)LocationLondon, United KingdomWork modeFully remoteExperience5+ yearsPosted1 month agoSkills & LanguagesMust-haverequiredGo Lang3 Year(s)Aws3 Year(s)Claude3 Year(s)Languages requiredEnglish About the Role We're hiring a Full-Stack Developer who is AI-native from day one — not a traditional engineer who occasionally uses AI, but a builder whose default way of shipping software is through agentic coding tools.  You will architect, build, and operate end-to-end systems with Claude Code as your primary development environment, ship them on AWS + Cloudflare's edge, and own everything from the Vite/React frontend to the Go backend. This role exists because the way software gets built has fundamentally changed, and we're looking for someone who already lives in that change: who builds and ships complete features in a single Claude Code session, knows how tool calls and agent loops actually work under the hood, writes their own skills and MCPs, and is comfortable composing systems out of edge functions, containers, and small fast services. If you've ever stayed up too late hacking on your own TUI or Neovim config, you'll fit in here. Must-Have Skills 1. Claude Code Daily, fluent use of Claude Code as your primary development environment. You should be comfortable with agentic workflows, sub-agents, plan mode, bypass / skip-permissions mode (running with --dangerously-skip-permissions responsibly), slash commands, hooks, and orchestrating long-running multi-step tasks. We expect to see real projects you've shipped with Claude Code — not just chat transcripts. Codex (OpenAI Codex CLI) experience is preferred; Codex + Claude Code together is a strong plus. 2. End-to-End Systems Built with Claude Code You must be able to take a problem from spec → schema → backend → API → frontend → deploy entirely through Claude Code, owning the full slice. This means agentic planning, generating and reviewing your own diffs, writing your own tests, and shipping production code without hand-holding. Show us a system you built this way. 3. AWS + Cloudflare (Workers + Containers + R2) AWS for primary cloud infrastructure — EC2 for compute, EKS / Kubernetes for orchestration, plus supporting services (S3, RDS/Aurora, VPC/networking, IAM). Kubernetes. Cloudflare Workers for edge compute, request routing, and low-latency APIs. Cloudflare Containers for running container workloads alongside Workers with a Worker-based control plane. Cloudflare R2 for object storage, plus working knowledge of KV, D1, Queues, and Durable Objects as appropriate. Cloudflare for Platforms / Workers for Platforms — building multi-tenant SaaS on top of Workers, dispatch namespaces, isolating customer code, and per-tenant routing. This is core to how our platforms are built. Cloudflare for SaaS — custom hostnames, automated SSL/TLS issuance, and per-customer domain onboarding so customers can run on their own branded domains. Terraform for infrastructure as code — modules, state management, plan/apply discipline, and provisioning across both AWS and Cloudflare from a single source of truth. Comfort wiring AWS services and Cloudflare's edge into a single coherent architecture. 4. Vite + React Frontend (Strict DOM) Vite as the build tool and dev server — fast HMR, ESM-native dev, Rollup-based production builds. React on react-strict-dom — write components against the strict DOM subset so the same code is portable and predictable. Modern React patterns: Suspense, transitions, server components where they fit, and careful state management. 5. Go Backend Idiomatic Go for backend services, APIs, and tooling. Comfortable with net/http, context, goroutines, channels, structured logging, and clean module/package layout. Building small,...