You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Ashby

Senior DevSecOps Engineer

  • Remote
  • 6+ years

Salary

$178,000 - 250,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

You report to the Head of Security. The security team is a single team with several specialisms that oversees security across the business, and it reports to the Co-Founder and VP of Engineering.

The company is past seed stage but still moves like one: you pick useful projects, make practical calls, and spend little time in meetings. Tens of thousands of people use its software daily, and customers depend on it. The company has tens of millions in ARR, growth above 100% year over year, over 2500 customers, very low churn and many years of runway. Notable customers include Notion, Linear, Shopify and Snowflake. More details are shared after the first conversation.

The team is exploring how software can support Talent Acquisition and has started building products beyond it.

The mission is to make the delivery pipeline secure by default across application code, infrastructure, dependencies, containers and product configuration. You own the technical build and running of delivery security tooling and controls, including integration, configuration, tuning, reliability and coverage.

Product Engineering triages and fixes issues in the features it maintains. Application Security supplies specialist analysis and sets product security test requirements. Infrastructure owns the cloud platform. You work with all three so agreed checks and policies run reliably in delivery.

The same position is also advertised as Senior Security Platform Engineer - Secure Delivery. Apply once, under whichever title fits your experience.

First three months: early changes widen in scope and ambiguity as you learn the codebase, infrastructure and practices, and you pair program with your onboarding peer. Initial goals are to map production delivery paths and gaps across code, infrastructure, prompts, configuration and evals with clear check ownership; deliver a bounded scanning integration, such as secret push protection or report-only static analysis, with a usable finding workflow; set initial warn, block and self-service exception rules with partners, making Product Engineering ownership visible; and baseline coverage, integration failures, false blocks and build delay. Success means engineers can use the chosen checks, act on findings and handle routine exceptions. Wider rollout follows the agreed risk policy and what the first integration shows.

Responsibilities

  • Deploy, configure, integrate and tune static analysis, dependency, secret, container and Infrastructure as Code scanning in CI/CD workflows.
  • Inventory production repositories and delivery paths, including prompts and model configuration. Keep scanner coverage separate from application tests of AI behaviour, which AppSec defines while you run the agreed delivery checks.
  • Start new checks in report-only mode where it fits, then apply agreed warn and block policies based on exploitability, exposure and compensating controls.
  • Offer engineers self-service exceptions within documented rules, each with an owner, justification, expiry and audit trail. Pass decisions outside those rules to Security leadership with the relevant specialist analysis.
  • Build automation and AI-assisted workflows that enrich findings, suggest fixes and support Product Engineering triage under documented criteria. Keep required checks, review and rollback in place for automated patch changes.
  • Make coverage, integration failures, finding age by risk, time to triage and fix, false blocks, build delay and bypasses visible. Log mitigations separately from completed fixes and link useful telemetry to GRC evidence.
  • Work with Infrastructure on cloud posture monitoring, alerts for critical misconfigurations, and bounded remediation automation.
  • Later, extend into shared image hardening and artifact provenance as the delivery foundations mature.
  • For example: roll out secret scanning with push protection and make a blocked push clear and actionable for the engineer; turn a repeated scanner exception request into a PR workflow with a reason, expiry and evidence for review; reproduce a dependency issue in the application, add a regression check, and build a workflow that proposes a patch with useful evidence; show which delivery paths are covered, where checks fail, and whether enforcement reduces risk without adding unreasonable build delay.

Requirements

  • You have built and run CI/CD, developer tooling or infrastructure automation that other engineers use.
  • You write maintainable code, can explain how what you shipped fails, and use security evidence to make practical rollout decisions.
  • You have applied AI in engineering and can explain how you check its outputs and permissions.
  • You like treating engineers as users, weighing build versus buy, and improving adoption and reliability after launch.
  • Supply-chain and scanner experience is useful. You can learn individual tools as part of the job.
  • You can write production automation in TypeScript, Python, Go or a comparable language.
  • GitHub Actions or similar systems, Terraform, containers and cloud controls are relevant. Tool choice and individual scanner integrations are part of the work, and scanner familiarity matters less than CI/CD and infrastructure automation experience.
  • You may not suit the role if you prefer to build a prototype and hand off its operation, since reliability, tuning and existing integrations are part of the work.
  • You may not suit the role if you prefer a fixed backlog to investigating unclear problems, writing proposals and bringing partners in.
  • You may not suit the role if your main aim is standalone assessments, since the role centres on working delivery capabilities and their adoption.

Conditions

The role is a senior position reporting to the Head of Security.

The interview process is: recruiter screen (30 mins); hiring manager intro call (20 mins); past projects deep dive (45 mins); founder screening (45 mins); take-home assessment plus practical assessment review (1 hr, with 2-3 spent on the take-home assignment); cross-functional stakeholder interview (45 mins).

Applications are reviewed and answered within 3-4 days, often sooner. Candidates who advance can expect a response within 2-3 days.

The company may use AI-driven tools to help the recruitment team screen, assess and select candidates.

This is an active, existing vacancy.

Benefits

  • Competitive salary and equity.
  • 10-year exercise window for stock options. You need not buy options when you leave; you can do it when you are financially comfortable.
  • Unlimited PTO, which the company encourages you to use.
  • At least 12 weeks of fully paid parental leave, covered by the company. The length may increase to meet local requirements.
  • Equipment, software and office furniture budget.
  • $100/month education budget. Larger items such as conferences are covered with manager approval.
  • In the US: top-tier health insurance for you and your dependents, with 100% of premiums covered. Elsewhere: high-quality supplemental health insurance for you and your dependents, also fully covered.

Where you’d work

Fully remote

You can work from

  • United States
  • Canada

About the company

Ashby

  • Industry: SaaS

18 of their 18 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 21 checks run
  • 1 red flag

Still hiring?

14 checks

No red flags

How crowded?

7 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Company
Tech stack
  • TypeScript
  • Python
  • Go
  • Terraform
  • CI/CD
  • GitHub Actions
Seniority
Senior
Type
Full-time
Equity
Equity offered
Industry
SaaS
Specialty
DevOps
Show 7 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
DevOps
Seniority
Senior
Experience
6+ years
Tech stack
  • TypeScript
  • Python
  • Go
  • Terraform
  • CI/CD
  • GitHub Actions

Location

Work model
Remote
Region
United States
Remote from
  • United States
  • Canada

Compensation

Salary
$178,000 - 250,000 / year
Pay period
Annual
Equity
Equity offered

Employment

Type
Full-time

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason