Technisch engineer.

1 settimana fa

Milano, Provincia di Milano; Lombardia, Italia Compri AI Tempo pieno
h3Position Overview /h3 pOur sales growth team is growing fast, and so is the amount of information it creates every day: accounts, calls, meetings, conversations. We want every rep to pull exactly what they need from our CRM in seconds, complete and ready to act on, and every number leadership needs to be one click away. At the same time, we sell to thousands of manufacturing and industrial companies, and the ones getting ready to rethink their procurement leave signals behind. Catching those signals early and putting them in front of the right rep at the right moment is one of the biggest growth levers we have. /p pWe're looking for a bGTM Engineer /b to own both and far beyond. You build and run the systems behind our commercial engine: a CRM that makes information dramatically faster to find and more complete, signals that tell sales who to call today and why, and automations that give our team more time to sell. You'll work mostly with Sales, and with Marketing wherever their systems touch the pipeline. /p pThis is an engineering role with a commercial brain. You don't need to have closed deals yourself, but you need to understand why a BDR cares about a signal and what an AE wants to see before a call. Then you build the thing, ship it, and check if it moved the numbers. /p h3What You'll Own /h3 h3CRM Foundation and Data Model /h3 pEverything else runs on this. If the data is wrong, every play built on top of it is wrong too. /p ul lipbCommercial audit: /b sit down with every Account Executive and BDR to map how they actually use the CRM today, what they need from it, and where it could do much more for them /p /li lipbA shared setup: /b turn those conversations into one common data model and pipeline structure, then build it into HubSpot /p /li lipbData quality and guardrails: /b raise the completeness and consistency of our data, streamline properties and objects, and add the validations and conditional logic that keep quality high as the team scales /p /li lipbData on demand: /b make sure pipeline, conversion and account data can be pulled in minutes, whether it's for a Monday pipeline review or a board deck /p /li /ul h3Signals and Prioritization /h3 pMost of our market isn't buying right now. Your job is to find the companies that are, before anyone else does. /p ul lipbSignal layer: /b build the system that collects buying signals (website visits, LinkedIn engagement, hiring, company news, public procurement strategies
- you name it) and plugs them to the right accounts and contacts in HubSpot /p /li lipbPrioritization: /b turn those signals into a clear daily answer for the sales team: who to call, and why now /p /li lipbFeedback loop: /b track which signals actually turn into meetings, and kill the ones that are just noise /p /li /ul h3Lead Routing, Enrichment and Outreach Systems /h3 pBuilding the proper infrastructure is critical for the actual work of growth sales team. It’s the plumbing nobody notices until it breaks. /p ul lipbInbound routing: /b own and improve the flow that enriches inbound leads, filters them against our ICP and routes them to the right rep in minutes /p /li lipbEnrichment: /b keep accounts and contacts enriched with firmographic and contact data, using Clay or whatever does the job best /p /li lipbOutreach tooling: /b own the stack the sales team uses to reach prospects (dialer, sequencing, LinkedIn tools) and be the first call when something stops working /p /li lipbAutomation: /b spot the repetitive tasks eating into selling time and automate them with n8n, agents, or whatever gets it done /p /li /ul h3Pipeline Systems for Demand Gen /h3 pNot ads, not content. The systems that connect what Marketing does to what ends up in the pipeline. /p ul lipbAccount based plays: /b build audiences and hyper personalized campaigns based on our best accounts and the patterns in the CRM /p /li lipbMarketing to Sales handoff: /b make sure every lead Marketing generates lands in Sales with the context needed to act on it /p /li lipbLifecycle sequences: /b support Marketing in building and running HubSpot lifecycle workflows that follow up with prospects through rules, delays and touchpoints across email, WhatsApp and other channels /p /li lipbAttribution basics: /b help us understand which sources and campaigns actually create or influence pipeline /p /li /ul h3Experimentation and AI Building /h3 pNothing here is sacred. If it doesn't move the numbers, it changes. /p ul lipbShip fast: /b prototype with Claude Code, Lovable, n8n and Clay, test with the team, and scale what works /p /li lipbAgents in the workflow: /b build AI agents that take over GTM work once done by hand, from account research to qualification to follow up drafting /p /li lipbNever stop exploring: /b you're compulsively checking Product Hunt, listening to GTM Engineering podcasts and getting your hands on new tools before they go mainstream, then bringing in what's worth trying and skipping what's hype /p /li /ul h