What the role is about

A Forward Deployed Engineer works inside the customer’s stack. You go where the product data actually lives, the PIM nobody has migrated, the ERP export that arrives as a fixed-width file, the marketplace feed whose rules exist in an email from 2019, and you make our agents work against it.

This is the engineering half of a deployment. The Retail Engineer owns the account and the method. You own the code at the edge: the integrations, the transformations, the pipelines, the parts that decide whether an agent reads clean input or garbage.

Deployed forward means the customer’s problem is your problem, and that you are in the room while it is being described rather than reading a ticket about it a week later. You work on accounts in Italy.

What you would do

• Build the integrations that connect our agents to customer systems: PIM, ERP, ecommerce platforms, marketplaces, data warehouses, and whatever else holds the catalog.
• Write the transformations that turn a customer’s export into something an agent can reason about, and the agent’s output into something their systems accept.
• Stand up pipelines that run at volume, with retries, with observability, and with somebody woken up when they fail.
• Debug in production, on their data, with them watching. Then make that class of bug impossible.
• Ship the change that unblocks the deployment today, then decide with the platform team whether it belongs in the product.
• Leave a runbook behind, so the account does not depend on your memory.

Who you are

Essential

• Three or more years writing production code, and you have owned something on call.
• Strong Python or TypeScript, and willing to work in whatever the customer’s stack forces on you.
• You are good with other people’s data: broken encodings, silent truncation, three sources of truth that disagree.
• SQL you reach for without thinking, and comfort with the shape of a data warehouse.
• APIs, queues, batch jobs, retries, idempotency. You know why the second run is the hard one.
• You are calm in front of a customer when something is broken, and you say what you know and what you do not.
• You use AI coding assistants as a matter of course, and you can tell where they help and where they do not.
• Willing to travel to customer sites.
• Fluent Italian and English.

Preferred

• You have been a forward deployed engineer, a solutions engineer or an implementation engineer at an enterprise software company.
• Retail or ecommerce data: catalogs, feeds, attributes, marketplace rules.
• Workflow orchestration: n8n, Airflow, Temporal or similar.
• LLM work in production, and an opinion about evals.

The team you would join

Our founders have spent their careers building and operating retail at scale. They have founded retail companies generating tens of millions in revenue, launched and scaled Amazon’s operations in Italy and Spain, led operations at Everli across more than 2,000 employees, and shaped product direction at Shopify and Zalando. Operator, founder, product leader. Every seat that defined modern European commerce.

Why join us

The hardest part of putting agents inside an enterprise is never the model. It is everything the model has to touch. That is the part you own, and it is the part that decides whether any of it works.

What we offer

• Meaningful early-stage equity.
• Competitive salary.
• The shortest distance there is between a line of code and a retailer’s catalog.
• A new craft. You learn to build and ship with agents and AI coding assistants, and it compounds.
• Flexible hybrid. The Milan hub, three days a week minimum, plus four remote weeks a year.