About the role
From the employer’s listing · Vestiaire Collective · posted 28 August 2026
Vestiaire Collective is the leading global platform for desirable pre-loved fashion and a pioneer in transforming how people consume fashion.
Our mission is simple: make circular fashion the norm, not the exception. Through technology, expertise, and a highly engaged global community, we enable millions of people to buy and sell fashion in a more sustainable way.
Founded in Paris in 2009, Vestiaire Collective is now a globally scaled marketplace with offices in Paris, London, Berlin, New York, Singapore, and Ho Chi Minh City, and logistics hubs across Europe, Asia, and the US. Today, we are a team of around 600 people from over 50 nationalities, united by a shared ambition: to drive meaningful change in the fashion industry.
Our values, Activism, Transparency, Dedication, Greatness, and Collective, shape how we build, collaborate, and grow every day.
About the Role
Vestiaire Collective runs a global marketplace on AWS and GCP — Kubernetes, Kafka, Terraform, Vault, Cloudflare, Datadog, a large PHP application under active modernisation, a series of microservices in different tech stacks (Goland, PHP, Node) and a fast-growing surface of AI-powered services.
As Director of Cloud Infrastructure and Security, you will lead a small team of six senior individual contributors across Cloud Infrastructure (DevOps/SRE) and Security. This is a hands-on Director role: alongside setting the strategy and roadmap, you will work directly with the team on architecture, technical decisions, incidents and delivery. You will be accountable, alongside Product Development teams, for the reliability, cost-efficiency and security posture of everything we run in production. What you will do: Leadership across two teams Directly lead, develop and retain a small team of six (6) experienced engineers across Cloud Infrastructure and Security. This is a player-coach role without multiple management layers, so you will remain close to the team’s technical work and day-to-day priorities. Define a joint roadmap for both teams, aligned to business priorities and risk appetite, and make explicit calls on what we will not do. Establish clear KPIs, SLOs and risk metrics, and report regularly to leadership on reliability, cost and security posture. Set the operating model: what product teams self-serve behind guardrails versus what your teams own centrally. Foster a culture where reliability and security are shared accountabilities, not tickets thrown over a wall, including establishing a Security Champions model across engineering.
Cloud infrastructure, reliability and platform Own our AWS and GCP footprint end to end: EKS, networking, secrets (Vault), data stores (RDS/Aurora, MSK, ElastiCache, MongoDB Atlas, OpenSearch) and the edge (Cloudflare). Establish real reliability engineering practice: SLOs and error budgets, capacity planning, and a business continuity plan. Drive infrastructure-as-code maturity: Automating Terraform change application, advancing our move to
















