Senior Security Platform Engineer
2 dagen geleden
Amsterdam, Gem. Amsterdam; Noord-Holland, Nederland
Ashby, Inc.
Voltijd
Gratis via e-mail of Google
Bewaar deze vacature en houd uw zoekopdracht georganiseerd
Maak een gratis account aan om vacatures op te slaan, waarschuwingen aan te maken en vanaf uw dashboard terug te keren naar deze vermelding.
Gratis via e-mail of Google
Als u doorgaat, gaat u akkoord met onze Voorwaarden & Privacybeleid.
Hi I'm Louis, Head of Security. What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you contribute to useful projects, make practical decisions, and work in an almost-no-meeting culture. The product-market fit and scale of a growth-stage startup: tens of thousands of daily users who depend on our software, and customers whose trust your work will help us earn. You'll join our Security team, a single team with multiple specializations overseeing security across the business. I report to Abhik, our Co-Founder and VP of Engineering. We're bubbling with ideas on how to support Talent Acquisition through software, and we've started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3-4 days (often sooner).
Role Overview We're looking for a platform engineer to build the secure-delivery capabilities other engineers use every day. You'll turn security requirements into reliable integrations, useful feedback, and self-service workflows that work across our production repositories. You'll treat engineers as your users and own the operation of what you ship. You'll use existing tools where they fit and build the capabilities that materially improve our delivery workflow.
About the Role
and How We Work We're also advertising this opening as Senior DevSecOps Engineer. Your mission is to make our delivery pipeline secure by default across application code, infrastructure, dependencies, containers, and product configuration. You'll own the technical implementation and operation of delivery-security tooling and controls, including integration, configuration, tuning, reliability, and coverage. Product Engineering teams own triage and remediation for the features they maintain. Application Security provides specialist analysis and defines product-security test requirements. Infrastructure retains ownership of the underlying cloud platform. You'll work with those teams to make agreed checks and policies run reliably in the delivery workflow. In practice, you'll: Deploy, configure, integrate, and tune static analysis, dependency, secret, container, and Infrastructure as Code scanning in our CI/CD workflows. Inventory production repositories and delivery paths, including prompts and model configuration. Make scanner coverage distinct from application-specific tests of AI behavior; AppSec defines those tests, and you operate agreed delivery checks. Give engineers self-service exceptions within documented rules, with an owner, justification, expiry, and audit trail. Escalate decisions outside those rules to Security leadership with the relevant specialist analysis. Build automation and AI-assisted workflows that enrich findings, propose fixes, and support Product Engineering's triage under documented criteria. Work with Infrastructure on cloud-posture monitoring, useful critical-misconfiguration alerts, and bounded remediation automation. Extend into shared-image hardening and artifact provenance as the delivery foundations mature. To ground it with examples, you could: Roll out secret scanning with push protection and make a blocked push understandable and actionable for an engineer. Turn a repeated scanner-exception request into a PR workflow with a reason, expiry, and evidence for revisiting it. 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 is addressing risk while keeping build delays reasonable. Why You Should and Shouldn't Apply You've built and operated CI/CD, developer tooling, or infrastructure automation used by other engineers. You can write maintainable code, explain the failure modes of what you shipped, and use security evidence to make a practical rollout decision. You've applied AI in engineering and can explain how you check its outputs and permissions. You enjoy treating engineers as users, making build-versus-buy decisions, and improving adoption and reliability after launch. Interview Process We review every application and aim to get back to candidates within 2‐3 days. Recruiter Screen
- 30 mins Hiring Manager Intro Call
- 20 mins Past Projects Deep Dive
- 45 mins Founder Screening
- 45 mins Take‐Home Assessment + Practical Assessment Review
- 1 hr (2‐3 spent on take‐home assignment) Cross‐Functional Stakeholder Interview
- 45 mins Role‐Specific Technology and Tools. GitHub Actions or comparable systems, Terraform, containers, and cloud controls are relevant. You should be comfortable writing production automation in TypeScript, Python, Go, or a comparable language. You'll pair program with your onboarding peer as you learn the delivery workflows. Map production delivery paths and gaps across code, infrastructure, prompts, configuration, and evals, with c
About the Role
and How We Work We're also advertising this opening as Senior DevSecOps Engineer. Your mission is to make our delivery pipeline secure by default across application code, infrastructure, dependencies, containers, and product configuration. You'll own the technical implementation and operation of delivery-security tooling and controls, including integration, configuration, tuning, reliability, and coverage. Product Engineering teams own triage and remediation for the features they maintain. Application Security provides specialist analysis and defines product-security test requirements. Infrastructure retains ownership of the underlying cloud platform. You'll work with those teams to make agreed checks and policies run reliably in the delivery workflow. In practice, you'll: Deploy, configure, integrate, and tune static analysis, dependency, secret, container, and Infrastructure as Code scanning in our CI/CD workflows. Inventory production repositories and delivery paths, including prompts and model configuration. Make scanner coverage distinct from application-specific tests of AI behavior; AppSec defines those tests, and you operate agreed delivery checks. Give engineers self-service exceptions within documented rules, with an owner, justification, expiry, and audit trail. Escalate decisions outside those rules to Security leadership with the relevant specialist analysis. Build automation and AI-assisted workflows that enrich findings, propose fixes, and support Product Engineering's triage under documented criteria. Work with Infrastructure on cloud-posture monitoring, useful critical-misconfiguration alerts, and bounded remediation automation. Extend into shared-image hardening and artifact provenance as the delivery foundations mature. To ground it with examples, you could: Roll out secret scanning with push protection and make a blocked push understandable and actionable for an engineer. Turn a repeated scanner-exception request into a PR workflow with a reason, expiry, and evidence for revisiting it. 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 is addressing risk while keeping build delays reasonable. Why You Should and Shouldn't Apply You've built and operated CI/CD, developer tooling, or infrastructure automation used by other engineers. You can write maintainable code, explain the failure modes of what you shipped, and use security evidence to make a practical rollout decision. You've applied AI in engineering and can explain how you check its outputs and permissions. You enjoy treating engineers as users, making build-versus-buy decisions, and improving adoption and reliability after launch. Interview Process We review every application and aim to get back to candidates within 2‐3 days. Recruiter Screen
- 30 mins Hiring Manager Intro Call
- 20 mins Past Projects Deep Dive
- 45 mins Founder Screening
- 45 mins Take‐Home Assessment + Practical Assessment Review
- 1 hr (2‐3 spent on take‐home assignment) Cross‐Functional Stakeholder Interview
- 45 mins Role‐Specific Technology and Tools. GitHub Actions or comparable systems, Terraform, containers, and cloud controls are relevant. You should be comfortable writing production automation in TypeScript, Python, Go, or a comparable language. You'll pair program with your onboarding peer as you learn the delivery workflows. Map production delivery paths and gaps across code, infrastructure, prompts, configuration, and evals, with c