kyra - Senior Back End Engineer UK Based

• 4+ years backend development with Node.js and TypeScript in production. • Strong PostgreSQL — schema design, query optimisation, migrations (Prisma a plus). • AWS experience — ECS or similar container orchestration, RDS, S3, Lambda. You've deployed and managed production services, not just used S3 for file uploads. • Docker — writing Dockerfiles, multi-stage builds, container orchestration. • CI/CD — GitHub Actions or equivalent. You've built and maintained pipelines, not just triggered them. • Queue systems — BullMQ, SQS, or similar. Background job processing patterns. • REST API design — Express or similar framework, Swagger/OpenAPI documentation. • Git workflow maturity — branching strategies, code review, migration safety. You understand why you don't run --accept-data-loss on a production migration. • STRONGLY PREFERRED • ClickHouse or columnar analytics databases — we run heavy analytics queries across millions of posts. • Redis — caching patterns, session management, queue backing store. • DDD / domain-driven design — our backend is structured as 70+ domain modules with explicit boundaries (repositories, services, guards, event emitters). • Cloudflare — tunnels, DNS, CDN configuration. • Monitoring/observability — Sentry, New Relic, LogRocket, or equivalents. You've triaged production issues, not just configured dashboards. • SuperTokens or similar auth systems — OAuth, OTP flows, session management. • AI/LLM integrations (OpenAI API, Claude) — we use AI for content analysis, chat agents, and automated QA. • Prisma 7 specifically (we're on the latest, including schema-level features). • Social media platform APIs (TikTok, Instagram Graph API, YouTube Data API). • RabbitMQ (used in our discovery service alongside BullMQ). • Elasticsearch for search. • Monorepo tooling (pnpm workspaces, yarn workspaces, NX). • Frontend awareness — you don't need to write React, but understanding how the frontend consumes your APIs (React Query, Zod validation on the client) helps. • WHAT THIS PERSON LOOKS LIKE • Debugs across boundaries — when a metric shows the wrong number, you can trace it from the React component → API hook → Express controller → Prisma query → ClickHouse table and figure out where it breaks. • Owns infrastructure without being asked — you notice the ALB health check is misconfigured before it causes an outage. • Writes code that doesn't need babysitting — Zod schemas, proper error handling, repository patterns that other team members can follow. • Communicates proactively — posts in Slack when deploying, writes migration plans before running them, documents API contracts for the frontend team. • Moves fast without breaking things — we deploy to production multiple times a week. You should be comfortable with that cadence while still being careful.