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
Collinear AI

MTS - Engineering (Security)

  • Seen live on Collinear AI's site yesterday
  • Senior
  • Remote
Pay
Not stated
Location
San Francisco, CA
Open for
17+ days
First seen
Oct 18, 2026
Apply on Collinear AI's site (opens in a new tab)

Posting record

No flags

Open 17+ days

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

Last checked Nov 3, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What it asks of you

8+ years of experience
“You have 8+ years of experience in security engineering, much of it securing cloud infrastructure in production” (quoted from the posting)

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

About the role

As a Member of Technical Staff - Engineering (Security), you will own security across Collinear's infrastructure, products, and customer data. We build RL environments and training data for frontier AI labs and large enterprises. They trust us with sensitive data and access to their systems, and many of our environments run AI agents that are being trained to find and exploit vulnerabilities.

This is a senior, hands-on role. You will work alongside our researchers and engineering team to set the direction for, and implement, new security measures.

What you'll do

  • Harden the sandboxes where AI agents run untrusted code, including cyber tasks where agents are actively trying to break out
  • Own AWS security, including IAM design, least-privilege access, network boundaries, and short-lived credentials in place of long-lived keys
  • Build detection and response across our cloud and Kubernetes environments, and tune alerts so the team acts on them
  • Protect customer data from the moment it arrives to the moment we deliver, including access controls, secure delivery, and PII removal at terabyte scale
  • Lead customer security reviews and compliance work, from security questionnaires and supplier onboarding to SOC 2
  • Secure our software supply chain, including dependencies, CI/CD, secrets, and our GitHub organization
  • Set guardrails for engineers and coding agents that work directly against production infrastructure
  • Test our systems the way an attacker would, and fix what you find

About you

  • You have 8+ years of experience in security engineering, much of it securing cloud infrastructure in production
  • You have deep hands-on experience with AWS security, including IAM, CloudTrail, GuardDuty, KMS, and VPC design
  • You have an offensive security background, such as penetration testing, red teaming, or vulnerability research, and use it to decide what to defend first
  • You have isolated untrusted workloads with containers or microVMs, using tools such as gVisor, Firecracker, or Kata Containers, and know where that isolation tends to fail
  • You write production-quality code, ideally in Python, and prefer automation to manual process
  • You have built or grown a security program at a startup, and know how to prioritize when you can't fix everything at once
  • You explain risk clearly to engineers, leadership, and customers' security teams

Something wrong with this posting?