Paul-Emmanuel Garcia

Who they are

Paul-Emmanuel Garcia is Head of Engineering at Vestiaire Collective — co-founded Acquiro360 and spoke publicly on splitting monolithic Swift codebases into modules.

Person

Paul-Emmanuel Garcia joined Vestiaire Collective in April 2020 when the company was a late-stage growth marketplace approaching unicorn status — and has since risen from Senior Mobile Software & Platform Engineer to Engineering Manager to Head of Engineering. Before Vestiaire, he cut his teeth as an iOS Developer, then as a Scrum Master and Product Manager Consultant at Extia, with earlier stints at vente-privee (now Veepee), Hulab, and Captain Dash — a route through French e-commerce and startup engineering that gave him both hands-on mobile craft and product-side exposure. He co-founded Acquiro360 at some point alongside his employed track. The through-line is a practitioner who grew into leadership inside the same company rather than job-hopping, with roots deep enough in mobile engineering to have spoken at a Swift/mobile architecture conference on 'Splitting Monolithic Swift Code Base Into Modules' alongside Maciej Grzybowski. Possibly — the GitHub activity suggests occasional public writing or open-source contributions, though it's light.

Company

The most recent move: in May 2026 Vestiaire Collective struck a distribution deal with Zalando to put its authenticated luxury resale catalog in front of shoppers across 14 European markets — a significant reach expansion without building the demand side from scratch. That followed a dense Q4 2025 and early 2026 restructuring: co-founder Fanny Moizant departed in January 2026, and the company simultaneously named Thomas Hézard as Chief Product Officer and Rémi Bouchez as Chief Technology Officer — meaning Paul-Emmanuel now has a new CTO above him. CEO Bernard Osta, who was CFO until October 2025 when he succeeded Maximilian Bittner, announced in February 2026 that the company expects to reach its first annual profit in 2026, following positive EBITDA in the 2025 year-end shopping period. The valuation has pulled back to approximately €1.1 billion from a €1.4 billion peak in 2021, and the company raised approximately €3.5 million via Crowdcube crowdfunding in February 2024 — a signal it's managing capital carefully on the road to profitability.

Market

Vestiaire Collective sits at the top of the authenticated luxury resale market, ranking 2nd among 71 active competitors by scale and 1st in total funding — with The RealReal, Stadium Goods, and myGemma as its main rivals globally. The bigger near-term threat is Vinted, which moved into luxury clothing resale in France and Europe in 2024, bringing a mass-market audience and aggressive pricing into Vestiaire's core geography. EU transparency, traceability, and 'right to repair' regulations arriving in 2025–2026 put a compliance burden on all players but create a structural advantage for Vestiaire, whose authentication infrastructure is already built.

Network

Paul-Emmanuel's most relevant peer leaders are the newly appointed CPO Thomas Hézard and CTO Rémi Bouchez, both named in January 2026, meaning he is navigating a fresh leadership configuration at the top of the product and tech org. Above them sits CEO Bernard Osta, the former CFO who took the helm in October 2025. His public conference co-speaker was Maciej Grzybowski on Swift architecture — a signal of the engineering community he came from.

Thomas Hézard· Chief Product Officer, Vestiaire Collective
Rémi Bouchez· Chief Technology Officer, Vestiaire Collective
Bernard Osta· CEO, Vestiaire Collective
Maciej Grzybowski· Co-speaker, Swift/mobile architecture conference

How they likely show up

Rose from Senior Mobile Engineer to Engineering Manager to Head of Engineering inside the same company over roughly five years → likely earns trust incrementally and builds institutional knowledge rather than parachuting in with a change agenda.
Earlier roles spanned iOS Developer, Scrum Master, and Product Manager Consultant → comfortable crossing the engineering/product boundary; probably speaks product fluently in leadership conversations.
Gave a public conference talk on splitting a monolithic Swift codebase into modules → signals a preference for structural, architectural thinking over feature-level problem-solving, and enough confidence in a craft opinion to put it on a stage.
Co-founded Acquiro360 alongside full-time employed roles → has a founder's bias toward initiative; unlikely to wait for permission when he sees a gap.
Occasional GitHub activity noted → stays close enough to code to have views, even in a Head of Engineering role.
Joined during the COVID period (April 2020) and stayed through a leadership reset, a co-founder departure, and a new CTO appointment → comfortable operating through organizational turbulence.

Conversation tips

→ Reference the Swift architecture talk ('Splitting Monolithic Swift Code Base Into Modules') — it shows you know where he came from technically, not just his current title.
→ Ask about the engineering implications of the Zalando integration — a 14-market catalog distribution deal has real platform and API surface-area consequences he'll have direct views on.
→ Don't treat him as a pure people-manager; he has an engineering craft background and probably still engages at an architectural level.
→ Acknowledge the leadership change at the top — new CTO Rémi Bouchez and CPO Thomas Hézard joined in January 2026; asking how that's reshaping priorities is a natural and respectful opener.
→ If you know French tech (vente-privee, the Paris mobile scene), it'll land — his whole career is rooted there.

Toolbox

Openers

Open on the Zalando partnership — in May 2026, Vestiaire integrated its catalog across 14 European markets via Zalando, which is a non-trivial engineering lift involving authentication flows, catalog syndication, and data contracts at scale.
Mention the Swift architecture talk he co-presented with Maciej Grzybowski on splitting a monolithic Swift codebase into modules — it's the clearest public signal of how he thinks about engineering structure, and most people haven't seen it.
Reference Acquiro360 — he co-founded it, and bringing it up signals you did more than skim his LinkedIn; it opens the conversation about what drew him back to the operator track.

Discovery questions

When Vestiaire brought in a new CTO in January 2026, how did that change how engineering priorities get set — did the scope of your role shift?
The Zalando integration puts your authenticated catalog inside someone else's platform at scale — what were the hardest engineering constraints to work within on a deal like that?
You gave a talk on breaking apart a monolithic Swift codebase into modules — how far has that philosophy extended into how you structure teams and ownership, not just code?

Avoid

Don't pitch him on tooling or process improvement without first understanding how he's already structured the engineering org — he's been there five years and built from the inside, so generic 'best practice' framing will land flat.

Make it yours