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
Causal

Member of Technical Staff — DevOps

  • Seen live on Causal's site 2 days ago
  • Senior
Pay
Not stated
Location
San Francisco
Open for
12+ days
First seen
Oct 23, 2026
Apply on Causal's site (opens in a new tab)

Posting record

No flags

Open 12+ days

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

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

Member of Technical Staff — DevOps

We look for infrastructure engineers who are obsessed with engineering velocity. Everything we do — research, training, serving, customer deployments — moves only as fast as our tooling. Your mission is to design, build, and operate the platform underneath it all, including the internal infrastructure for agentic development, so every engineer and researcher can iterate rapidly with agents doing more of the work.

Responsibilities

  • Measure developer velocity, and partner with researchers, product engineers, and forward-deployed engineers to find what slows them down and remove it
  • Build internal infrastructure for agentic development: sandboxes, tool access, context, and eval harnesses that let autonomous research and coding agents run end to end
  • Self-host and serve open-source LLMs for internal agent use
  • Own CI/CD, build and test infrastructure, reproducible dev environments, and infrastructure-as-code so research and product code ship quickly and safely
  • Build the monitoring, alerting, and on-call for our product and customer-facing services to catch failures before users do
  • Own cost across the dev stack: track and cut spend on compute, tools, and inference

What we're looking for

We value a relentless approach to problem-solving, rapid execution, and the ability to quickly learn in unfamiliar domains.

  • AI-pilled: uses coding agents daily and has built internal infrastructure for agentic development, not just used it
  • Experience self-hosting and serving open-source LLMs (e.g. vLLM, SGLang)
  • Strong systems background: Linux, networking, containers and orchestration (e.g. Docker, Kubernetes), infrastructure-as-code (e.g. Terraform)
  • Experience building CI/CD and developer tooling (e.g. GitHub Actions, Buildkite, Bazel, Nix)
  • Knowledge of cloud platforms (GCP, AWS, or Azure) and best practices for observability and security
  • Track record of measurably improving developer velocity
  • Owns deliverables end-to-end, from requirements through autonomous execution

Something wrong with this posting?