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 — Security Engineering

  • 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

Our mission is general causal intelligence; AI that is capable of (1) predicting the future and (2) identifying the actions to alter it.

To achieve this breakthrough, we are building a Large Physics foundation Model (LPM) because physical systems, unlike text or images, are governed by verifiable cause and effect. We believe that scaling on physics will enable an understanding of causality required to predict and control physical systems, starting with weather.

Our founding team has built and deployed AI against the physical world in robotics, drug discovery, and particle physics at institutions like DeepMind, Waymo, Cruise, Insitro, Nabla Bio, and CERN.

About Security at Causal Labs

As we build and deploy our Large Physics Model, we operate an environment that spans petabytes of continuous physical observations, massive distributed GPU clusters, and high-stakes customer deployments.

Your mission is to design and operate the security posture across our entire engineering stack. You will ensure our research environments, proprietary model weights, software infrastructure, and customer integrations remain secure, all while maintaining the rapid iteration and engineering velocity our researchers need.

Responsibilities

  • Enterprise Infrastructure & Cloud Isolation: Architect secure network perimeters, private data transmission channels (e.g., PrivateLink, VPNs), and isolated single/multi-tenant storage environments. Implement access controls and customer-managed encryption (KMS/BYOK) across petabyte-scale data stores.
  • Model IP & Weight Protection: Design zero-trust boundaries, encrypted storage, and secure execution environments to protect proprietary foundation model weights and checkpoints against exfiltration during storage, distributed multi-node training, and serving.
  • Pipeline Integrity & AI Threat Defense: Secure our data ingestion pipelines against tampering and data poisoning. Threat-model and defend against AI-specific vulnerabilities, including adversarial inputs, model extraction attacks, and data memorization/regurgitation risks using output guardrails and privacy-preserving techniques.
  • Enterprise Auth & Governance: Own enterprise identity federation (SAML 2.0/OIDC with Okta, Entra ID) and machine-to-machine authentication (mTLS). Implement immutable audit logging, cryptographic erasure, and compliance controls required for enterprise CISOs and SOC 2 / FedRAMP environments.
  • Security Engineering & SDLC: Partner with Infrastructure, Research, and Forward Deployed teams to build automated security testing, threat detection, and vulnerability scanning directly into our deployment workflows, orchestrators (Kubernetes, Slurm), and customer-facing APIs.

What we're looking for

  • Demonstrated Hands-on Security Engineering: Proven track record building and securing production systems in cloud environments (AWS, GCP, or Azure) or large-scale distributed systems. Practical mastery of core primitives: IAM, network perimeters, KMS/encryption, and secrets management.
  • Strong Systems & Software Background: Hands-on experience with Linux systems, networking, container security (Docker, Kubernetes), Infrastructure-as-Code (Terraform or Pulumi), and proficiency in languages like Python, Go, or Rust.
  • Understanding of ML Platform Security: Practical grasp of the security challenges unique to ML platforms—protecting high-value model weights, securing distributed training pipelines, data lineage/poisoning, and AI-specific threat vectors.
  • Adaptable & High Agency: Comfort conducting architectural security reviews, digging into complex distributed systems, and adapting fast to new technical constraints or bespoke enterprise customer environments.
  • Bias Toward Real-World Impact: Pragmatic mindset—delivering security solutions that actually work for users under pressure, balancing rigor with engineering velocity.
  • End-to-End Ownership: Ability to take deliverables autonomously from initial threat modeling and requirements all the way through execution, deployment, and monitoring.

Something wrong with this posting?