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 (Index, Search Crawler)

  • Office
  • 6+ years

Salary

Not stated

Similar roles pay £90K - 130K a year · our estimate

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

Trustworthy AI answers depend on the information behind them. The company grounds its answers in current, real-world sources, and the index is what makes that work.

The team is hiring an engineer for the indexing and data processing layer of the Search Crawler. You will build systems that take in large amounts of crawled content and turn it into structures that can be queried efficiently. Most of the work sits in offline and nearline pipelines that keep data fresh, complete, and available to downstream retrieval. Datasets change constantly, so throughput, scale, and correctness all matter.

Responsibilities

  • Design, build, and run large-scale indexing systems and data pipelines that sit at the center of the company's search infrastructure.
  • Create and refine indexing approaches that trade off speed, freshness, and resource use.
  • Work on storage formats, compaction, and update methods that keep data current and easy to reach.
  • Keep pipelines dependable and predictable when throughput is high.
  • Write well-tested components with clear ownership and stable interfaces that can change as the system grows.
  • Set up observability for offline and nearline pipelines, covering structured logs, metrics, and data quality signals.
  • Track throughput, resource consumption, and cost, and make improvements as priorities shift.
  • Work with the retrieval, ranking, and ML teams so indexing output fits what they need.
  • Support safe testing of indexing strategies and processing logic through staged rollouts and well-defined quality measures.

Requirements

  • 5+ years of experience building production backend or data infrastructure systems.
  • Solid programming experience in Go, C++, or Rust.
  • Experience with high-throughput data processing and very large datasets.
  • Experience building or running databases, storage systems, data planes, or indexing pipelines.
  • A strong grasp of distributed systems, including fault tolerance, consistency, and scalability.
  • Experience operating production systems and responding to incidents.
  • A systems-level way of thinking, with the ability to reason about data flow from end to end.

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 37 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
  • Go
  • C++
  • Rust
Seniority
Staff
Type
Full-time
Industry
AI
Specialty
Backend
Region
United Kingdom
Show 6 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Staff
Experience
5+ years
Tech stack
  • Go
  • C++
  • Rust

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