Job brief: Senior Corporate Security Engineer

GitLab · Remote, Canada; Remote, United States · facts as of 2026-11-08. Anyone can open this page; no account needed.

Is it still open? · Checked by JoRoute

Taken down. GitLab's own job board stopped listing it; JoRoute confirmed that on 2026-11-07. Last seen there 2026-11-06.

What JoRoute checked · Checked by JoRoute

  • Listed on GitLab's own job board. JoRoute does not take listings from job ads or recruiters.
  • First seen by JoRoute 2026-11-06 (2 days ago); last confirmed on the board 2026-11-06.
  • The apply link opens job-boards.greenhouse.io, the address GitLab's board gives for this job.
  • No other listing with this title and place on this board in the last 90 days.
  • No layoff notices (WARN) under this name in the state files JoRoute reads.

What the listing says · Employer's own words, not checked

  • Pay: $139,200 to $200,000 a year
  • Job type: Not stated
  • Where: Remote · Remote, Canada; Remote, United States · North America
  • Posted: 2026-11-05

What the job asks · Employer's own words, not checked

Level: Senior. The title says "Senior".

Must have

  • Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license.
  • many successful candidates do not meet every single requirement.

Main duties

  • Help lead the security architecture of GitLab's endpoint fleet and related infrastructure, with a primary focus on macOS.
  • Design and support automation for secure endpoint deployment, configuration, and lifecycle management using code-based workflows.
  • Manage endpoint and SaaS security configuration through Terraform, version control, merge requests, continuous integration pipelines, and automated rollouts.
  • Develop patching and software distribution approaches that align with security, compliance, and operational requirements.
  • Partner with Information Technology, Security Operations, and Detection and Response teams to improve endpoint telemetry, detections, and response models.

Lines copied from the posting, not rewritten. "Preferred" or "nice to have" items are not listed as must-haves.

How it compares · Compared by JoRoute from listings

  • Across GitLab's 125 open listings, 22% of those with a posting date were first posted more than 60 days ago. How GitLab hires

What nobody outside the employer knows · Not known

  • Whether the role is already filled or on hold: employers often leave listings up.
  • How many people applied, and who reads the applications.
  • Where in the published range an offer would land.

Ask before you apply

  1. Is the role fully remote, and from which states can I work?
  2. What are the interview steps, and when should I expect to hear back?

Share this brief

Send it to someone whose opinion you trust. They can open it without an account, and nothing about you is in the link.

Email itText it

To keep a copy, use your browser's Print or Share button.

Next steps

Full listingPractise the interview

Got a message about this job asking for money or documents? Check the message first.

Keep looking

A summary of facts and listings, not a verdict that this job or employer is safe. JoRoute is not affiliated with GitLab. How JoRoute checks listings · Original posting