> Markdown version of [/jobs/ext/2748325-senior-backend-engineer](https://www.wearedevelopers.com/jobs/ext/2748325-senior-backend-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Backend Engineer - **Company:** Peec AI - **Location:** Berlin, Germany - **Experience:** Expert - **Salary:** €100,000.0 - €150,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Cloud Computing, Databases, Software Debugging, Distributed Systems, Python (Programming Language), PostgreSQL, Node.Js, RabbitMQ, Redis, Prometheus, Search Technologies, TypeScript, Data Logging, Google Cloud, Cloud Platform System, Large Language Models, Grafana, Firebase, Backend, Kubernetes, Vertica, Webhooks - **Published:** September 6, 2026 - **Apply:** https://www.adzuna.de/details/5872139858 ## About the Role * 5+ years of backend, platform, infrastructure, or distributed systems engineering experience in a production environment. * Deep hands-on TypeScript experience. We run TypeScript services on Bun, and we care about people who can design clean, reliable backend systems rather than only write application code. * Strong understanding of queues, workers, retries, rate limits, idempotency, distributed locks, webhooks, and failure handling. * Experience operating systems under real production pressure: incidents, provider outages, customer escalations, noisy alerts, slow dependencies, and incomplete data. * Comfort with cloud-native infrastructure. Our stack includes GCP, Kubernetes, Cloud Tasks, Pub/Sub, RabbitMQ, Redis, Postgres, Firestore, ClickHouse, Prometheus, Grafana, and OpenTelemetry. * Ability to debug across layers: application code, logs, metrics, queues, provider APIs, databases, network behaviour, and deployment state. * Product-minded judgement. You can separate internal detail from customer-safe explanation, and you understand when a "small infra change" has customer, security, or cost implications. * High ownership and low ego. We want people who take responsibility for ambiguous systems, ask sharp questions, and make the team better through clear thinking and kindness. * A bias toward durable fixes. You do not stop at "restart the pod" if the real issue is retry amplification, missing backpressure, an unsafe parser assumption, or a provider limit we do not model. Tech stack * Languages: TypeScript, Python * Runtime/frameworks: Bun, Elysia, Node-compatible services * Cloud/infrastructure: GCP, Kubernetes, Cloud Tasks, Pub/Sub, Firebase/Firestore, Postgres, ClickHouse, Redis, RabbitMQ * Observability: Prometheus, Grafana, OpenTelemetry, structured logging * Product/data domain: LLM chats, AI search, source scraping, citation extraction, provider integrations, customer-facing analytics * AI/model providers: OpenAI, Anthropic/Claude, Perplexity, Gemini, Google AI Mode / AI Overview, plus scraping/provider APIs around them ## Description Peec AI is building the data plane for AI visibility: millions of chats, scrapes, citations, sources, model responses, and customer-facing insights running through a fast-moving backend. This role is for an engineer who wants to own the systems behind that. You will not just add endpoints or close tickets. You will make our scraping, chat-processing, source-ingestion, and analytics infrastructure more reliable, cheaper, faster, and easier for the rest of the team to reason about. The best fit looks like someone who can debug a provider outage in the morning, design a better queueing model before lunch, ship a TypeScript service change in the afternoon, and write the postmortem or follow-up ticket clearly enough that the next engineer immediately knows what to do. We are especially interested in people who have built or operated systems with real constraints: rate limits, flaky third-party APIs, queues, webhooks, retries, distributed locks, data migrations, observability gaps, customer pressure, and cost ceilings. ## Related Videos - [Reducing LLM Calls with Vector Search Patterns - Raphael De Lio (Redis)](https://www.wearedevelopers.com/videos/1714-reducing-llm-calls-with-vector-search-patterns-raphael-de-lio-redis) - [5 steps for running a Kubernetes environment at scale](https://www.wearedevelopers.com/videos/88-5-steps-for-running-a-kubernetes-environment-at-scale) - [Stop using Node.js like in 2020! What changed and what you can do today with Node.js](https://www.wearedevelopers.com/videos/100011-stop-using-node-js-like-in-2020-what-changed-and-what-you-can-do-today-with-node-js) - [Inside Bitpanda's Tech Stack: Scaling a European Fintech Leader - Markus Dorner](https://www.wearedevelopers.com/videos/1979-inside-bitpanda-s-tech-stack-scaling-a-european-fintech-leader-markus-dorner) - [Accelerating Authentication Architecture: Taking Passwordless to the Next Level](https://www.wearedevelopers.com/videos/733-accelerating-authentication-architecture-taking-passwordless-to-the-next-level) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Backend Developer Salary in Germany [2023]](https://www.wearedevelopers.com/magazine/196-backend-developer-salary-in-germany-2023) - [Find a Developer Job: 12 Best Job Sites For Developers](https://www.wearedevelopers.com/magazine/165-find-a-developer-job-12-best-job-sites-for-developers) - [The Biggest German Tech Companies](https://www.wearedevelopers.com/magazine/424-the-biggest-german-tech-companies) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)