Paul-Emmanuel Garcia

Who they are

Paul-Emmanuel Garcia is Co-Founder of Acquiro360 — an EPITECH-trained engineer who climbed from iOS developer to Head of Engineering at Vestiaire Collective before co-founding his own consulting venture, and spoke at a Swift conference on splitting monolithic codebases into modules.

Person

Paul-Emmanuel studied at EPITECH (European Institute of Technology), graduating around 2016 — a Paris engineering school known for project-based, hands-on technical training. He started as an iOS Developer and Scrum Master, moved through consulting (Extia, Product Manager Consultant track), then joined vente-privee (now Veepee) before landing at Vestiaire Collective, the French luxury resale platform. At Vestiaire Collective he progressed from Senior Mobile Software & Platform Engineer to Engineering Manager and ultimately Head of Engineering — a meaningful climb inside a company that was scaling fast in the secondhand luxury market. Along the way he passed through Captain Dash and Hulab, filling in the mobile and platform engineering side of his background. He co-founded Acquiro360, a small privately held business consulting and services company, and is now running it full-time. His one documented public moment is a conference talk co-presented with Maciej Grzybowski on 'Splitting Monolithic Swift Code Base Into Modules' — a practitioner-level take on mobile architecture for growing teams. The through-line: hands-on engineer who grew into engineering leadership, then bet on himself.

Network

Paul-Emmanuel's most documented professional context is Vestiaire Collective, where he worked under CEO Bernard Osta and alongside Chief Technology Officer Rémi Bouchez and Chief Product Officer Thomas Hézard. His Swift conference talk was co-delivered with Maciej Grzybowski, suggesting a peer technical network in the Paris and French mobile engineering scene.

How they likely show up

  • Progression from iOS Developer → Scrum Master → Engineering Manager → Head of Engineering → Co-Founder → suggests someone who deliberately broadened scope at each step rather than staying in a specialist lane.
  • Scrum Master role in the middle of an engineering career → process and team coordination are not abstract to him; he has run ceremonies and owns that vocabulary.
  • Swift conference talk on modular architecture (co-presented, practitioner-level) → comfortable going deep on technical specifics in public, not just managing upward.
  • Possibly — mixed tenure shape across several employers suggests he moves when the learning curve flattens, not out of instability.
  • Co-founding Acquiro360 at 1-10 employees after Head of Engineering at a scaled company → high agency, willing to trade comfort for ownership.
  • No detectable public writing or blog presence → likely prefers direct conversation and builds influence through work and relationships, not content.

Conversation tips

  • → Reference the Vestiaire Collective scaling story — he spent meaningful time there across multiple rungs; it's where his leadership identity was formed.
  • → The modular architecture talk is a good entry point: ask about the tradeoffs he hit in practice when splitting a real codebase, not the theory.
  • → Don't assume he's purely technical — the Scrum Master and Product Manager Consultant stops signal he thinks about process and product, not just code.
  • → Ask what prompted the move to co-found Acquiro360 — it's a deliberate founder bet after a comfortable senior role, and he'll have a clear answer.

Toolbox

Openers

  • Open on the Swift modular architecture talk he co-presented with Maciej Grzybowski — splitting a monolithic codebase is a specific pain point, and it signals you know he's thought about mobile platform decisions at scale, not just feature shipping.
  • Reference the arc from iOS Developer to Head of Engineering at Vestiaire Collective — it's an uncommon path (IC → EM → HoE at a fast-growing luxury resale unicorn) and shows you've read past the title.
  • Mention that he co-founded Acquiro360 after the Vestiaire chapter — framing it as a deliberate founder bet rather than a career transition is likely to resonate with how he sees the move.

Discovery questions

  1. When you were moving Vestiaire Collective's mobile codebase toward modules, what was the hardest organisational — not just technical — problem to solve?
  2. You went from hands-on iOS engineer to Head of Engineering at a scaled company: at what point did you feel like you'd stopped being an engineer and started being a leader, and was that a moment or a slow drift?
  3. What does Acquiro360 focus on — is it mobile/platform consulting specifically, or are you taking the engineering leadership experience somewhere broader?

Avoid

Don't open with generic mobile trends or 'what do you think about the future of iOS' — his public signal is firmly in the architecture and team-productivity layer, not the product/consumer angle.

Make it yours

Tailor these openers to what you sell

These openers are generic. Sign in and tell Brief what you sell — it rewrites the hooks and questions around your pitch.

Sources

Brief on your next meeting?

Type any name. Get a structured pre-meeting brief in seconds.

Try Brief →

Generated by briefthecall.com from public web sources on July 28, 2026. Each claim is linked to its source above.

Automatically generated by AI from public sources. May be inaccurate or out of date. Remove or correct this profile →