Cue is a modern customer service chat software company. Our Live Chat, Chatbot and Broadcast products help businesses to provide customer support at scale across WhatsApp, Messenger, Web chat, email and Telegram. We’re looking for deeply experienced engineers to join our team in a role that’s genuinely new: designing and architecting backend systems, then directing AI agents to build them, and critically verifying the results.
This isn’t a traditional coding role. You’ll spend your time understanding problems, designing solutions, writing specs, and working with AI tooling to bring those solutions to life — fast. The catch: you need the hard-won experience to know when the AI gets it wrong. Use AI agents and tooling to accelerate implementation Review and verify AI-generated code and architecture with a critical eye Collaborate with the team to evolve our engineering practices as AI tooling matures
Strong Linux, networking, and infrastructure fundamentals (SRE/platform background ideal) Fluency reading and writing code — you don’t need to be the fastest coder, but you need to understand code deeply Active use of AI coding tools and LLM-based workflows The confidence and experience to challenge AI output when it doesn’t meet the bar A track record of owning projects from conception through production A collaborative working style — you enjoy designing in the open, sharing early ideas, and building on other people’s thinking Infrastructure : AWS (multi-account), Terraform + Terragrunt, Atlantis for automated deployment Kafka (MSK), SQS (standard + FIFO) with dead letter queues Data : Aurora Serverless v2 (PostgreSQL), Elasticsearch, Redis (ElastiCache), InfluxDB Networking : Traefik ingress with NLBs, ExternalDNS, cert-manager, Route53, CloudFront, VPC peering GuardDuty, Security Hub, Elasticsearch SIEM, CrowdSec WAF, Firezone (Zero Trust) We don’t care about your degree, which languages you’ve used, or whether you can invert a binary tree on a whiteboard. Are excited about AI as a tool, but not naive about its limitations Have war stories from production Kubernetes — OOMKills, node scaling failures, networking mysteries Have stared at a database failover and understood why connections didn’t recover When you’re on, you’re focused, making decisions, and shipping. We expect you to unblock yourself, ask for help when it’s genuinely needed, and take responsibility for outcomes….