Delivery Project Manager

ppPolysense is scaling fast. We help food producers see their production lines differently. Quite literally. Our computer vision systems watch, analyze and understand what's happening in real time, turning visual data into insights that change how people work. Customers like Agristo and Lotus Biscoff are already running on it. /p pDelivery excellence is what turns a great product into a great company. To keep that up as we grow, we're hiring a bDelivery Project Manager /b. This is not a role about tracking tickets and running status meetings. It's about owning your implementations end-to-end, leading a squad of Forward Deployed Engineers and making sure every rollout lands exactly as it should. /p pbYou make sure the work lands. And you're the face of Polysense for every customer who depends on it. /b /p h3What you’ll be doing /h3 h301. End-to-end implementation ownership /h3 pTake over from Sales and translate the commercial win into a clear, executable implementation plan. Scope, timeline, milestones, risks, success criteria. All yours. /p pRun the implementation from kick-off to live production. Own pilots, rollouts, and multi-site deployments at customer locations. /p pForecast delivery risk early. Surface issues before they become problems. Drive decisions when things get hard. No waiting to be asked. /p pBe the single owner for your implementations. One clear narrative, no mixed signals. /p pMake sure every implementation lands on time, within scope, and with measurable value for the customer. /p pbKey point: /b You're not a passive PM tracking a Jira board. You're accountable for the full implementation. From the first kick-off call to the moment the customer sees value. /p h302. Squad leadership /h3 pbLead a squad of Forward Deployed Engineers: /b You don't write all the code, but you keep the team sharp, focused, and moving. /p pbProtect the team from noise: /b Translate customer requests into actionable plans, run stand-ups, clear blockers. The goal is a team that ships, not a team that firefights. /p pbCoach your engineers: /b Know when to push someone, when to step in, and when to get out of the way. You make the people around you better. /p pRun 1-on-1s, development conversations and performance reviews. You bown the growth of your squad /b, not just the implementation. /p pExecute within the delivery framework the Head of Delivery sets. When something isn't working in the field, you say so clearly and early. That feedback loop is how the framework gets better. /p pLeave every implementation better documented than you found it. What you learn should be useful for the next team. /p pbKey point: /b This is not just implementation management. It's people leadership. Your squad is mostly early-career engineers who are still finding their footing. You're the person who helps them find it faster. /p h303. Customer ownership communication /h3 pAct as the bvoice of Polysense /b for your accounts throughout delivery. /p pbOwn communication /b across all stakeholder layers: operations, IT, engineering, and leadership on the customer side. /p pbKeep stakeholders aligned /b on scope, timelines, and risks. Manage expectations actively instead of reacting to surprises. /p pStay close to the customer after go-live. Make sure they extract the full value of what Polysense delivered. /p pWork closely with Customer Success and Customer Value to support expansion and continuous improvement. /p pbKey point: /b Our customers are partners, not clients. You set the tone for that relationship during delivery. /p h3What you bring /h3 pYou’ve bworked as a Project Manager /b in a tech environment. Enough to hit the ground running and know what good delivery looks like. /p pTechnically literate: No Computer Science degree required, but you need to understand what your engineers are building and why. Enough to make good calls and spot when something's off. /p pYou’ve bled or mentored people /b before. You know the difference between managing tasks and actually developing someone. /p pYou’ve worked in environments where software meets real-world operations: factories, industrial sites, physical deployments. You know that going live involves more than a deployment script. /p h3Nice to have /h3 ul liExperience in a startup or scale-up environment where delivery processes were still being built /li liBackground in food manufacturing, industrial technology, or automation /li liFluency in Jira or similar implementation management tooling /li /ul h3Skills Mindset /h3 pbLead without ego /b /p pEngineers respect you. Not because you out-code them, but because you understand what they're doing and have their back. You know how models land in production and you make good calls because of it. /p pbAI native, not AI curious /b /p pYou use AI tools in your own work, not just talk about them. You build workflows that don't need an army to run, and you expect the same from your squad. Manual work is a last resort. /p pbStructured, not h