Federico Aliprandi Setup IT/EN

Head of Dev · NOOO · Padua

Federico Aliprandi

From lens to code. I ship e-commerce and complex integrations to production, leading the development team.

02

The path

From light to code, in four shots.

  1. 01 Light

    2017 — 2023

    Camera operator

    Gran Teatro Geox, Padua

    Live shows and events, then editing. That's where I learned teamwork and strict timing: the show starts when it's scheduled to.

  2. 02 Pixel

    2019 — 2022

    Education

    Digitally · ITS Academy LAST

    A master's in digital marketing, then two years of higher technical training as a web developer: front end and back end with Vue.js and Laravel. Before that, electronics and Arduino at ITIS Severi.

  3. 03 Code

    2022 — 2025

    Web Developer

    NOOO, Padua

    E-commerce and CMS from analysis to go-live: custom themes and plugins, integrations with payments, shipping and ERPs, releases and maintenance.

  4. 04 System

    Sep 2025 — today

    Head of Dev

    NOOO, Padua

    Since September 2025 I've led a team of 8 developers and the delivery: estimates, Gantt charts, code review, quality standards, releases. I'm still hands-on: on the trickiest projects I still write the code.

03

Work

Eight projects with code names: the clients stay off screen, the work doesn't.

  1. 03.1

    Reverse Shot

    Beauty and fragrance, multi-brand retail · 2024 — 2026

    • Magento 2
    • Hyvä
    • SAP Business One
    Open the case →

    The problem. Over 4,000 products whose prices and stock live in SAP and must reach the shop without errors, every day.

    The technical choice. The shop on Magento and Hyvä built in six weeks, then a pipeline from the SAP Service Layer with one job each for items, prices, quantities and new products, from every 5 minutes to daily. Plus pickup in 7 stores.

    My role. Front end and SAP sync

  2. 03.2

    Day for Night

    Paints, insulation and tools for trade professionals · 2025 — 2026

    • WordPress
    • PHP
    • WPML
    • Cron
    Open the case →

    The problem. The ERP is the source of truth: about 5,000 items, customers, orders and invoices have to reach the site, in Italian and German.

    The technical choice. Nightly imports from the ERP's export files, in batches and by difference, with automatic download of images, technical and safety data sheets. Orders and invoices land in the customer area.

    My role. ERP synchronisation

  3. 03.3

    Long Shot

    Kitchens and home furniture · 2024 — 2026

    • WordPress
    • PHP
    • WPML
    Open the case →

    The problem. A huge catalogue of systems, finishes and accessories to present in seven languages and lead all the way to the stores.

    The technical choice. A custom theme built by the team in three months; my part: store locator with geolocation, navigation, landing pages for fairs, technical SEO and the first Gutenberg blocks.

    My role. Store locator, navigation, technical SEO

  4. 03.4

    Dissolve

    Herbal teas and infusions · 2024 — 2026

    • WordPress
    • PHP
    • Lenis
    Open the case →

    The problem. A herbal tea brand with eight very different lines, to be presented one by one and found in stores.

    The technical choice. A theme built from scratch: 21 templates, a page for every line, smooth scrolling and measured motion, store locator and modular landing pages.

    My role. Almost the whole theme

  5. 03.5

    Voice Over

    Design furniture · 2026

    • WordPress
    • Voiceflow
    • REST API
    Open the case →

    The problem. Helping visitors find the right product in a very large catalogue.

    The technical choice. An AI assistant behind a WordPress REST proxy, so the key never reaches the browser. Structured answers become real product cards, with instant skeletons. On a site I've looked after since 2022.

    My role. Design and development

  6. 03.6

    One Take

    Catering equipment, B2B · 2025 — 2026

    • PrestaShop
    • Smarty
    • 6 languages
    Open the case →

    The problem. A live store of technical products that also sell through quotes: about 10 requests and 50 orders a day.

    The technical choice. A piece-by-piece redesign without stopping sales: mega menu, built-in quotes, product page and step-by-step checkout rebuilt in 2026, with order insurance.

    My role. Theme, product page, checkout and quotes

  7. 03.7

    Archive

    Design seating and furniture · 2026

    • WordPress
    • Custom plugin
    • PDF
    Open the case →

    The problem. About 70 families and 300 products, with designers, awards, finishes and downloads, to be managed as an archive rather than plain pages.

    The technical choice. The catalogue leaves the theme and becomes its own plugin, with 26 importers run from WP-CLI and PDF sheets generated in a few seconds.

    My role. Catalogue plugin and importers

  8. 03.8

    Behind the Scenes

    Internal tools, NOOO · 2026

    • Next.js
    • MySQL
    • Python
    • MCP
    Open the case →

    The problem. An external tool for the team's hours, and too many dashboards to open for client reports.

    The technical choice. Two separate tools: NOOO Time, the in-house time tracker that replaced Clockify for 30 people, and an MCP server that brings clients' GA4 and Google Ads data into Claude.

    My role. Concept and development

04

Direction

A software project is shot like a film: same phases, same discipline.

  1. 01

    Pre-production

    Analysis, estimates, planning

    Understand the real workflow before writing code. Clear priorities, honest estimates, a stack chosen for the project.

    • Workflow analysis
    • Estimates and priorities
    • Architecture

  2. 02

    Shooting

    Development, code review

    Readable code and shared standards: every take goes through review.

    • WordPress
    • Magento 2
    • PrestaShop
    • Vue
    • Laravel
    • Astro
    • Next.js

  3. 03

    Editing

    Integration, QA

    The moment the pieces have to talk: ERPs, payments, shipping, data.

    • SAP Business One
    • ERPs
    • REST APIs
    • Import and export
    • End-to-end tests

  4. 04

    Distribution

    Release, maintenance, evolution

    Go-live is the beginning, not the end: performance, measurement and continuous improvement.

    • Deploy and servers
    • Performance
    • Technical SEO
    • GA4 and tracking

05

End credits

Director
Federico Aliprandi
Production
NOOO, Padua
Set design
Three.js, GLSL
Editing
Astro, Lenis
Typefaces
Instrument Serif, Geist
Shot in
Padua, Italy
Note
No mascots were harmed in the making of this site

Rolling?

A project to ship to production, or a team to grow: write to me.

LinkedIn ↗