Staff Security Engineer
The Opportunity
Veo's security surface is unusual. We train models on-premise on dedicated GPU infrastructure, run the product across AWS and GCP, and operate a fleet of tens of thousands of cameras deployed at clubs and venues worldwide. That is a scope most SaaS security engineers never touch: physical devices in the field, heavy on-prem compute, and multi-cloud production, all in one role.
We are forming a Security Enablement Team that makes it easier for every engineering and IT team at Veo to build, ship, and operate secure systems. As the most senior engineer on the team, you will own the technical direction of the platform security, identity, and network security slice, partnering with the teams that own these systems so security is built in from the start. As an enablement function, the team does not run these systems day to day. We build the paved roads, tooling, and patterns that let the owning teams operate securely by default.
You will join during a pivotal moment. We are standing the team up, defining what good looks like across platform security, identity, and network security, and rolling out the first paved roads for image scanning, SBOM generation, CVE response, CI/CD identity, and a unified internal network across our datacenters (GCP, AWS) and offices (Miami, Berlin, and Copenhagen). You'll have direct impact on how 100+ engineers write, review and ship secure systems.
What You Will Do
- Design and build the paved roads for image scanning, SBOM generation, and CVE response, running inside the pipelines teams already use, with findings routed to the owners who can fix them under tracked SLAs
- Lead the design, reviews, and tooling for a unified internal network and VPN across GCP, AWS, and our Miami, Berlin, and Copenhagen offices, while the team that owns the network keeps running it
- Work with the auth service maintainers on identity and access, including MFA rollouts, removal of shared accounts, and cleanup of long-lived tokens, so the patterns stay theirs to own
- Make workload identity the paved road for CI/CD, using OIDC between GitHub Actions and AWS or GCP, packaged so teams can migrate themselves
- Build audit logging as a shared capability that teams plug into rather than reinvent
- Turn GRC controls into technical implementations, with evidence pipelines that produce auditable output without manual follow-up
- Own the contracting cycle for external penetration tests and build the intake, classification, and tracking system that routes findings to named owners, while the owning teams remediate
- Hand each capability off cleanly, with a runbook, a named owner, and an escalation path, and run office hours where product and platform teams can get a security review or a paved-road question answered
- Mentor the rest of the team and raise the security bar across Builders
You will join a focused platform security team and operate as its most senior engineer. Everything below follows the same pattern. We design the paved road, prove it works, and hand it to the team that will own it. We share ownership, pair on complex work, and rotate responsibilities, and we expect this role to set the bar.
As the team matures, you will help shape our multi-environment network architecture, our identity and access patterns, and the long-term security posture of the product.
What You Could Bring
- Platform security: you have run vulnerability scanning, CVE management, and image scanning at scale, and you know the operational reality of getting CVEs fixed, beyond standing up the tooling
- Identity and auth: you have worked hands-on inside an auth codebase, rolled out MFA on live systems, and managed token lifecycles in CI/CD with OIDC and workload identity
- Network security at scale: you have designed and run a unified internal network across multiple cloud providers and offices, with a VPN approach that holds up
- Platform-as-product mindset: you have built internal security tooling that other teams chose to adopt, with guard rails built into the tools developers already use and manual review as a last resort, and you gathered feedback and measured the impact
- Infrastructure as Code: strong experience with Terraform, Crossplane, or similar
This is a deliberately merged platform security and identity role. You do not need to be world class at both. You likely have several years of production infrastructure and security experience behind you, and you are deep and credible in one of these areas and ready to grow into the other.
That depth tends to show up in several of the following:
Nice to have: GitOps tools such as Flux or ArgoCD, Cilium, Kubernetes security at scale, and experience building security into a GRC evidence pipeline.
How We Work
You'll join a Copenhagen-based Security Enablement Team of three engineers plus a manager. We operate as an enablement function: we build shared tooling and golden paths, and we step in for focused, high-leverage missions where no other team is positioned to deliver. We do not run a SOC and we do not carry a security pager.
You'll collaborate regularly with the Platform, Product, IT, Firmware, and GRC teams. We work pragmatically and iterate quickly. This role sets the technical direction for the team's quarterly missions. We document decisions, favor simple solutions where possible, and focus on tooling and platform patterns that help teams move faster with confidence.
If you read that list and matched on three or four items but not all of them, apply anyway. The "deep in one, ready to grow into the other" framing above is not a hedge, it is how we actually hire at this level. We value diversity and inclusion and welcome applicants from all backgrounds.