You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Perplexity

Member of Technical Staff (Site Reliability Engineer, Search Crawler)

  • Office
  • 6+ years

Salary

Not stated

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

Keeping a crawler running is not the same as keeping it productive. Queues can grow while servers look healthy, and a small change can become a fleet-wide bottleneck. On Perplexity's Crawler team, you'll improve throughput, plan capacity, and build operational reliability through safer deployments, better observability, and durable fixes.

Responsibilities

  • Operate and optimize Kubernetes workloads and supporting infrastructure for crawler services, including fetching and rendering fleets.
  • Build and maintain infrastructure as code and CI/CD pipelines, with safe rollouts, validation, and fast rollback.
  • Define SLOs and build monitoring, alerting, and observability for availability, latency, throughput, and resource saturation.
  • Own capacity planning and resource efficiency; diagnose queue backlogs, network failures, and resource bottlenecks with service owners.
  • Participate in the team's on-call rotation, lead incident response, and turn blameless postmortems into durable reliability improvements.
  • Write production software to automate diagnosis and routine remediation, with validation and approval gates for high-impact actions.

Requirements

  • 5+ years of experience in SRE, production engineering, or infrastructure-heavy backend roles, with strong programming skills in Python, C++, Rust, or Go.
  • Hands-on experience with cloud infrastructure, production Kubernetes, infrastructure as code such as Terraform, and automated deployment workflows.
  • Strong Linux and networking fundamentals, including TCP/IP, DNS, TLS, HTTP, and load balancing.
  • Experience building observability with tools such as Datadog, Prometheus, or Grafana, and using SLOs to guide reliability improvements.
  • Proven experience diagnosing distributed-system failures, leading production incidents, and improving system performance or resource efficiency.
  • Experience operating web crawlers, search infrastructure, or browser fleets at scale.
  • Experience with distributed queues, backpressure, workload isolation, or multi-region recovery.

Where you’d work

From the office

About the company

Perplexity

  • Industry: AI

Offices in London, United Kingdom, Dublin, Ireland

Also hiring in San Francisco, United States, New York City, United States, Palo Alto, United States and 4 more places

3 of their 36 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 1 red flag

Still hiring?

13 checks

No red flags

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • Python
  • Go
  • Kubernetes
  • Terraform
  • Linux
  • CI/CD
  • Prometheus
  • Grafana
  • Datadog
Seniority
Staff
Type
Full-time
Industry
AI
Specialty
SRE
Region
United Kingdom
Show 6 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
SRE
Seniority
Staff
Experience
5+ years
Tech stack
  • Python
  • Go
  • Kubernetes
  • Terraform
  • Linux
  • CI/CD
  • Prometheus
  • Grafana
  • Datadog

Location

Work model
Office
Region
United Kingdom
Offices
  • London, United Kingdom
  • Dublin, Ireland

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Company

Industry
AI

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason