Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Peec

Senior Backend Engineer

  • Seen live on Peec's site yesterday
  • Senior
Pay
€100k to €150k a year
Location
Berlin
Open for
12+ days
First seen
Oct 23, 2026
Apply on Peec's site (opens in a new tab)

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Peec's site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Peec, so its true age is longer.

Last checked Nov 3, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Pay
€100k to €150k a year

Not stated: Real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Skills mentioned

About the role

About Peec AI

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.

About the role

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.

What we’re looking for

  • 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

What we offer

  • Exciting and challenging work with real impact and ownership at one of Europe’s fastest-growing Series A startups
  • Regular team events and off-sites
  • Aggressive equity compensation package
  • Paid Dinner & Uber home when working late
  • The most beautiful office space and work environment in Berlin

Something wrong with this posting?