A complete application in a minute
Tailored resume and cover letter, ready to send.
Peec AI is building the data plane for AI visibility, handling millions of chats and ingestion pipelines. You will own the systems behind scraping, chat processing, and analytics, making them reliable, cheaper, faster, and easier for the team to reason about.
The role fits someone who can diagnose outages, design efficient queues, deploy TypeScript services, and document postmortems clearly for future engineers.
Peec AI is the analytics platform for AI search. People increasingly discover products and make buying decisions through ChatGPT, Claude, Gemini, and Google's AI Overviews instead of traditional search, and most brands have no idea where they show up in those answers. Peec gives marketing, SEO, and growth teams the data to see exactly that: how visible their brand is across AI platforms, how they compare to competitors, and where to win.
We are defining this category, and the market is moving with us. Peec is a Series A company backed by 20VC and Singular, that went from $0 to $15M ARR in 18 months, with a 100+ person team across our Berlin HQ and our New York office.
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.
Compensation: €100K – €150K