teya - Go to Market Systems Admin (HubSpot)

• Investigate root causes, not symptoms. When something in HubSpot fails, you own it. You dig into what actually went wrong, validate the real root cause, and drive it to a fix. You are the single point of contact when the CRM misbehaves, and nothing gets dropped on your watch. • Prevent the next bug before it happens. You do not just close errors, you learn from them. You spot the patterns, harden the implementations that keep breaking, and put guardrails in place so a whole class of problems disappears. Every automation and implementation, local or global, follows our guidelines because you make sure it does, before and after it goes live. • Measure the health of the CRM. You build the dashboards that show, at a glance, whether what we ship actually works and keeps working. You track error rates, adoption, and data quality over time, so CRM health stops being a feeling and becomes a number we can watch and improve. • Turn data into action. You are as comfortable reading the numbers as fixing the system. You globalise and clean up our reporting once the requirements from Commercial Excellence are aligned, retire the dashboards no one needs, and use data to find the problems no one has noticed yet. • Build and improve, hands on. You create new automations and refine the ones we have, you read the logic of a workflow well enough to debug it, and you keep the instance clean, governed, and scalable across every market in Europe. • Your goal is to maximise the value and the trust in the CRM our salespeople rely on. Your success is measured in the health of the platform: fewer recurring failures, faster time to a real fix, cleaner data, and leaders who believe the numbers again because someone is watching them every day. • WHAT IS YOUR STORY? • You need to be eager to learn and improve every day. Some qualities you must have: • A detective's instinct: you are not satisfied with a symptom, you want the root cause, and you enjoy the hunt • An owner's mindset: you do not wait to be told, you know the instance and you act on it • Reactive when it counts and proactive by default: when something breaks you are on it and you meet the SLA, and when you see a risk you raise it before it spreads • Data-driven and analytical: you read data, understand the problem, and propose the fix • The confidence to challenge a request rather than just take it, because requests will not only come from us, and the right thing to build is your job to protect • Experience with a CRM (HubSpot ideal, Salesforce or similar is welcome), with ticketing and SLAs, and comfort building automations and reading the logic behind them • This is not a deep-specialist or heavy-code role. Understanding custom code is a plus, but the heart of the job is investigation, prevention, reporting, and governance. If you get satisfaction from taking something messy and making it trustworthy, this is your role.