— 16 roles, newest first.
stack:
TypeScriptNode.jsJavaScriptReactVue.jsNext.jsNuxt.jsPHPSymfonyLaravelPostgreSQLMySQLRedisDDDVitestViteAWSVercelJSNADJSNSDNespresso's e-commerce platform, Next Alpha Project.
• Front-End development (Typescript, VueJS)
• Work in agile setting (Scrum)
• Development of dynamic and reusable UI.
• Code refactoring.
• Unit Testing and E2E.
• SEO improvement.
• Accessibility.
• Analytics (Google Analytics)
Technical Environment:
VueJS, Typescript, Sonar, Gitlab, Jira/Confluence, Bitbacket, Jest, Nightwatch, ESLint, Css/Sass, PostCss, Tailwind, CI/CD, RESTFUL API, GTM, …
Carrefour Links Project
Category Management Collaboration to provide 360° view on their category (performance + projects)
Provide access to useful & quality CRF performance data
Architecting TypeScript/Node services and Next.js + Nuxt frontends for product teams. Own the boundary between design system and app code, push for DDD-flavored modules and high test coverage on anything that touches money or auth.
That a well-drawn module boundary saves more time in review than any lint rule — once the domain layer stopped importing framework code, onboarding new contractors got a lot faster.
Tarkett's e-commerce website B2B/B2c
Technical Environment:
Javascript, Nuxt/VueJS, React/Next, Css/Sass, Jest, Cypress, ESLint, StoryBook, SSR
PHP Symfony, Drupal, Git/Github, CI/CD, PHPUnit, PHPCS, PHPStan, WC3 Accessibility, RESTFUL API, SOAP, API Platform, AWS, ElasticSearch, Mysql, PgSQL...
Architecting TypeScript/Node services and Next.js + Nuxt frontends for product teams. Own the boundary between design system and app code, push for DDD-flavored modules and high test coverage on anything that touches money or auth.
That a well-drawn module boundary saves more time in review than any lint rule — once the domain layer stopped importing framework code, onboarding new contractors got a lot faster.
Nespresso's e-commerce platform, Next Alpha Project.
• Front-End development (Typescript, VueJS)
• Work in agile setting (Scrum)
• Development of dynamic and reusable UI.
• Code refactoring.
• Unit Testing and E2E.
• SEO improvement.
• Accessibility.
• Analytics (Google Analytics)
Technical Environment:
VueJS, Typescript, Sonar, Gitlab, Jira/Confluence, Bitbacket, Jest, Nightwatch, ESLint, Css/Sass, PostCss, Tailwind, CI/CD, RESTFUL API, GTM, …
Rebuilt a checkout service migrating from a monolith to isolated Node workers behind a message queue, with idempotency keys and reconciliation jobs to keep ledgers honest.
Idempotency is not a nice-to-have on payment endpoints — it is the difference between a retried request and a customer charged twice.
Rebuilt a checkout service migrating from a monolith to isolated Node workers behind a message queue, with idempotency keys and reconciliation jobs to keep ledgers honest.
Idempotency is not a nice-to-have on payment endpoints — it is the difference between a retried request and a customer charged twice.
Nespresso's e-commerce platform (Next).
• Back side development (PHP, DRUPAL)
• Work in agile setting
Technical Environment:
Acquia BLT, Drupal, PHP, Solar, Vue, GitLab, Jira/Confluence, Bibacket, Sonar, PHPUnit, PHPCS, Akamai, CI/CD, E-commerce REST API…
• SIAM Migration & Theming.
• Live video management.
• Social Network binding.
Technical Environment:
- PHP, Drupal 8, HTML, SASS, Twig, JQuery, React, Docker, Git, Gitlab, YouTube API, Graph Facebook API, Twitter feeds API.
Built and scaled Symfony + Vue apps on Postgres & Redis for a dozen client products. Owned CI pipelines, caching layers and API design, and mentored two junior devs through their first production incidents.
Cache invalidation is a people problem before it is a code problem — most of the stale-data bugs traced back to two teams disagreeing on what a cache key should represent.
Built and scaled Symfony + Vue apps on Postgres & Redis for a dozen client products. Owned CI pipelines, caching layers and API design, and mentored two junior devs through their first production incidents.
Cache invalidation is a people problem before it is a code problem — most of the stale-data bugs traced back to two teams disagreeing on what a cache key should represent.
Shipped Laravel/MySQL backends and my first React frontends for an early-stage SaaS. Learned to move fast without breaking the important things, under a founder who reviewed every PR personally.
Ship the boring version first. The feature that took two days to "do right" almost always got redesigned within a month anyway once real users touched it.
Shipped Laravel/MySQL backends and my first React frontends for an early-stage SaaS. Learned to move fast without breaking the important things, under a founder who reviewed every PR personally.
Ship the boring version first. The feature that took two days to "do right" almost always got redesigned within a month anyway once real users touched it.
Started out fixing bugs in a legacy PHP admin panel, then graduated to small features. Learned Git, code review etiquette, and how to read a stack trace without panicking.
Asking "why" about an existing pattern before changing it saved me from breaking things I didn't know were load-bearing more than once.