RevOps Engineer

Most companies we meet have a CRM that nobody fully trusts: duplicate records, stages that mean different things to different people, routing rules that were true two years ago, and reporting built on all of it.

You fix that, then build the automation that keeps it fixed. This is the least glamorous layer of the work and often the one that changes the most.

What you will own

• HubSpot architecture: objects, properties, lifecycle stages, pipelines and permissions
• Data hygiene: deduplication, normalisation, enrichment on write, and the rules that stop decay
• Routing and assignment, including the edge cases nobody documented
• Reporting that a leadership team can act on without a caveat
• CRM migrations when a client arrives with two systems and no single source of truth

What we are looking for

• Deep HubSpot. Salesforce experience is welcome but HubSpot is where our clients live
• You have run a real migration and know where the bodies are buried
• You are opinionated about data models and can explain one to a non-technical exec
• Comfortable with APIs and automation tooling, not only the native UI
• You care that a report is correct more than that it is pretty

What this is not

• Not a CRM admin role. You are designing the system, not maintaining tickets.
• Not purely internal. Some engagements are client-facing, some are not, and that varies by project.
• Not a place where reporting is somebody else's problem.

How to apply

Send your CV or profile and a few lines on what you have built to contact@kinetyca.com, with "RevOps Engineer" in the subject line. One of the founders reads every message. There is no recruiter or application form.