The role

You'll join a new team built around a strategic initiative the executive team follows closely. You own a problem space outright: go find what is actually broken, decide what we build, get it shipped, then say out loud whether it worked. Assume the scope moves at least once.

We work fast and we'll expect you to keep up. Experience building product on top of AI, or using it to compress your own discovery and delivery cycle, counts for a lot here, though it isn't really what we're screening for. Product work comes down to judgment. The tooling can be learned, and it's the judgment we'll spend the interviews on.

What you'll own

• Finding the problem, including the ones nobody has asked for. Part of this is going deeper on pain we already know our customers have. The harder part is spotting what they've stopped complaining about because they assume nobody can fix it. You'll live in customer conversations, usage data, support tickets, and what competitors are shipping, and you'll be the one who noticed first. What counts at the end of it is a company metric moving. Shipping a lot is not the same thing.

• Deciding what we build. A roadmap somebody can actually work from: what is happening now, what waits, what we have chosen not to do and why. You'll get some of these wrong. Say so early and change the plan.

• Being honest before engineering starts. What problem, for whom, which number moves, what we are knowingly not solving, and what it costs us if we're wrong. Write it up however you like. Just don't hand a team a brief that quietly leaves the risky part undefined.

• Arming everyone else. Sales, CS, Marketing and Support all have to sell, explain and defend what you ship, so you'll work with PMM on positioning and make sure documentation, enablement and instrumentation land with the release. Then the uncomfortable conversation a few weeks later, with evidence: double down, leave it alone, or kill it.

Who we're looking for

• Five to eight years shipping product, ideally B2B SaaS, owning the outcome rather than the sprint. Long enough to have watched something you built go wrong in year two. Not so long that an empty page has stopped being fun.

• You reason from first principles and can show your working. When you make a call the rest of the company wasn't expecting, you know how to bring them with you.

• You want this kind of job: the visibility, the pressure, and a scope that isn't settled yet. If your best work happens on a mature product with a clean backlog, you'd be unhappy here, and we'd both know it by month three.

• You've used AI to do real product work and you have opinions about where it helps and where it hands you confident nonsense.

• Engineering, Design and PMM move in the same direction when you're in the room, and not because your title obliges them to.

• Italian and English, both fluent. The squads you'll work with daily are in Milan, and your writing will end up in front of customers, analysts and the board.

Extra credit: Microsoft 365, IT administration, security or governance tooling; running continuous discovery for real rather than as a ritual; having been somewhere the strategy shifted under your feet and helping steer instead of waiting.