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
Whitecircle

Research Engineer (Evals)

  • Seen live on Whitecircle's site today
  • Mid level
  • Remote
Pay
Not stated
Location
Paris
Open for
12+ days
First seen
Oct 23, 2026

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Whitecircle'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 Whitecircle, so its true age is longer.

Last checked Nov 4, 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

Not stated: Pay, 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.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

TL;DR: We're looking for a research engineer to build and maintain our internal suite of benchmarks, covering single/multi-turn content and agentic guardrails. The research engineer would also work with the team on projects studying agent behaviours in the wild.

About us

White Circle is an AI Safety company building the safety, reliability, and optimization layer for AI systems. At the core of our platform are policies – simple natural-language rules that define what an AI model should and shouldn’t do. We automatically test, enforce, and continuously improve these policies at scale.

  • We’ve recently raised our Series A funding round, taking our total funding to $70M. Our investors include top funds, founders, and senior leaders at OpenAI, Anthropic, HuggingFace, Mistral, DeepMind, Datadog, Sentry, and others
  • We process over 100M+ API calls every month
  • We fine-tune and train our own LLMs so they run faster and cheaper than any open or proprietary model

We’re a small, highly focused team. If you want to work deeply on hard problems, see your work ship to production quickly, and influence how AI safety is actually built – you’re the one we need.

About the team

White Circle's fundamental research team works on the science of how AI systems fail in the real world: where agents break, how misalignment actually looks like to the end user, and how it is present in the model internals. We build the evals, benchmarks, environments, and tooling that empirically study high-impact agent reliability concerns — some of which become the guardrails shipped in our products, and some of which become public writeups.

What you’ll do

Own and maintain our internal benchmark suite, covering single/multi-turn content guardrails and agentic safety.

  • Build benchmarks that distinguish specific model capabilities.
  • Work with the product team to build evals covering core functionality of our flagship models.
  • Build benchmarks for new features coming out of the research team.
  • Adapt and extend evals to new verticals and changing product data.
  • Work on research projects that study and quantify realistic agentic and LLM failure modes in the wild.

You’ll fit right in if you

  • Have built an LLM benchmark from scratch that distinguished specific model capabilities (i.e., produced a measurable, defensible capability difference, not just a score).
  • Have built synthetic data for post-training textual or multimodal models.
  • Can reproduce a published benchmark result and identify where the original methodology is fragile or misleading.
  • You write Python that other people can build on. Our whole stack is Python; we want someone who has shipped and maintained production code and who factors messy problems into clean abstractions others can extend.
  • You can write efficient LLM inference setups, including sensible orchestration of parallel calls, retries, rate-limit handling.
  • An AI power-user — fluent with frontier models and coding agents day to day.

A big plus

  • Automated red-teaming experience
  • Have worked across a range of agentic scaffolds and reproduced public benchmark results on them
  • Strong knowledge of existing reward-model / monitoring / safety benchmarks
  • One or more published papers in the evals / safety-evaluation space

Compensation & benefits

  • Competitive compensation, including equity
  • Flexible time off
  • Office in central London/Paris with flexible hybrid setup
  • Relocation support if you’re moving to Paris, available after your probationary period
  • Premium private health insurance
  • Mental health support, including coverage for therapy when you need it
  • Lunch and dinner covered when you work from the office
  • Learning and development support for courses, conferences, and opportunities to grow your skills
  • All the hardware, subscriptions, tools, and services you need
  • Team off-sites twice a year: we’ve recently been to the Alps, Saint-Tropez, and Marbella

Process

  • Intro call with Talent
  • Test assignment
  • Technical interview with Head of Fundamental Research
  • Final interview with CEO

Something wrong with this posting?