GTM Engineer (HubSpot & Automation)
Archipro · Parnell, Auckland ·
- Work mode
- Hybrid
- Seniority
- Junior
- Category
- Sales
Archipro · Parnell, Auckland ·
Salary: $90,000 – $110,000 per year
ArchiPro started in Auckland in 2014, opened in Australia in 2021, and is now building out the United States. The platform connects architecture and design professionals, the brands that supply them, and the people building and renovating.
More than 400,000 people use ArchiPro every month and the platform reaches over 4.5 million a year. Brands on it include Resene, James Hardie, Blum, Cosentino, Neolith and Colorsteel.
ArchiPro knows a great deal about its market. What is being built, who is specifying what, which brands appear on which projects, and in which country. Turning that into commercial action needs systems that work properly, and right now nearly all of that build sits with one person.
This role is the second pair of hands, with real HubSpot skill. You will build and look after the systems that carry a signal from our platform through to a sales conversation. HubSpot is the centre of it. Clay and our own platform data feed it.
You will not be doing this alone or in the dark. The Head of Revenue Operations and GTM designs the commercial architecture and sets the rules. You build it with him, test it properly, and keep it working.
HubSpot build and administration
About 60 percent of your week to begin with. You will be hands-on across the portal. Objects and properties, associations, pipelines, workflows, lists, forms, sequences, tickets, users and permissions, imports, reporting, and the HubSpot side of our integrations. You will treat every change as a release. Test it, document it, ship it, watch it, and be able to roll it back.
The HubSpot rebuild
The portal has grown for ten years and now runs three markets and several business models it was never designed for. A rebuild is underway. You will map what exists, build the proposed solution against a design alongside your manager, test it against real scenarios, take it through user testing with the business owner, and release it in a controlled way.
Clay and enrichment
You will take day to day Clay operations off the Head of RevOps. Workspace and credit management, table and folder structure, naming standards, enrichment waterfalls, HubSpot lookups, duplicate and domain checks, email verification, quality checks, cost per result, and preparing clean updates for HubSpot.
ArchiPro runs Deepline and ZoomInfo alongside Clay. One of your projects is bringing those together into a single enrichment process managed through HubSpot, so we stop paying twice for the same record.
Turning a request into a clean audience
Marketing asks for the priority New Zealand lighting brands for a campaign. The answer is not an export. You define the cohort, check who is already a customer or a subscriber, check open opportunities and past sales history, confirm the market, validate the company and its domain, classify it against our ideal customer profile, find the right buyer roles, check what we already hold in HubSpot, spot the stale and bounced contacts, enrich only what is missing, quality check it, put each company in the right bucket, update HubSpot safely, and then measure what the campaign did. That whole loop is the job.
Data quality and governance
Duplicates, blank domains, fields written by more than one workflow, records drifting back after someone fixes them by hand. You will find these, work out the root cause, and fix them at the source rather than patching the symptom.
The request queue
CRM requests and tickets come in from sales, marketing, client partnerships and servicing across three markets. You will work that queue, which is also the fastest way to learn how ArchiPro really runs.
Marketing's list person. Work comes in through one queue and gets prioritised.
The HubSpot help desk, or IT support.
A data engineering role. Snowflake and the platform pipelines sit with our technology team, and you will work alongside them.
A strategy role. You will have a strong say in how things get built. The commercial architecture is owned above you.
This is not an entry level CRM job. The title says GTM Engineer because of where the role goes. The bar on day one is someone who has genuinely handled a HubSpot environment.
Two or more years hands on as a HubSpot administrator or super admin in a real business, not as a marketing or sales user of the tool.
Built workflows yourself, and fixed broken ones yourself. You can explain enrolment, suppression, branching and re-enrolment without notes.
Worked properly with objects, properties, associations and pipelines, including creating them and cleaning them up.
Been part of at least one HubSpot implementation, migration, redesign or rebuild, and can say what you personally did on it.
Dealt with real data problems. Duplicates, bad imports, records that will not stay fixed, and bulk updates you had to get right first time.
Used an enrichment or GTM data platform at volume, and built the logic yourself. Clay is what we run. Deepline, Apollo, ZoomInfo, Cognism, Lusha, Clearbit, Apify, Instantly or similar all count. What matters is that you designed the waterfall, checked the output and watched the cost, rather than running a table someone else set up.
The question we ask everyone: tell us about a HubSpot environment you personally helped build or rebuild. What was wrong with it, what you changed, how you tested the change, and what happened afterwards.
You do not need all of these. Each one adds to your case.
Clay at a deeper level. HTTP API columns, conditional runs, formulas, AI columns, and keeping cost per usable result under control.
Outbound tooling such as Instantly, Smartlead, Lemlist or HeyReach, and the deliverability side that goes with it.
Scraping and web data tools such as Apify, Firecrawl or similar.
Operations Hub or Data Hub, custom coded actions, data sync.
APIs and webhooks, JSON, basic SQL, some Python or JavaScript.
Snowflake or any data warehouse exposure.
Zapier, Make or similar.
Using AI tools to speed up your own work, with proper checks on what comes back.
Lifecycle automation, lead routing, account based marketing, or a marketplace or SaaS background.
When a workflow misbehaves, some people open it and start editing. We want the person who asks what enrolled, why, which property changed, what changed it, what else uses that property, what the business rule was meant to be, how to reproduce it, and how to test a fix without breaking anything live.
Curious, careful, and willing to say when something needs a business decision before it can be changed. You will be working across three markets and several teams, so you also need to write clearly and keep your own documentation.
We will test your HubSpot knowledge. There are three stages and the practical one carries the most weight.
A 30 minute conversation about systems you have personally worked on.
A live technical session. We give you an ArchiPro scenario, you design the solution out loud, and we push on the edge cases.
A practical exercise of 60 minutes on a test portal. You will diagnose what is broken, explain the root cause, design the safe fix, tell us what you would not change without asking first, and write the tests you would run before release.
Competitive base salary.
ArchiVersary leave, an extra day off for every year of service.
Laptop.
A beautifully designed office in Parnell, and team events.
Mentorship and coaching, and a rebuild you will be able to point at for the rest of your career.
Send your CV and a cover letter. Tell us about a HubSpot environment you helped build or rebuild, what was wrong with it, and what you did about it. That matters more to us than the CV.