Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
Halter in Auckland is seeking an Operations Specialist to enhance post-sale performance and support. This role focuses on operational processes, ensuring teams effectively utilize tools and achieve high performance in customer support and launches.
The ideal candidate will have a strong background in customer operations, exceptional process design skills, and the ability to drive data-driven decision-making across teams. If you’re passionate about improving customer experiences and enjoy working in dynamic environments, we'd love to hear from you.
At Halter, we’re on a mission to enable farmers and graziers to run the most productive and sustainable operations. Our customers are using Halter to break free from the time‑intensive constraints of conventional practices. Imagine watching 500 cattle stand up and walk calmly towards their next break? No quad bikes, no dogs, no fences. Just a group of cattle walking at their own pace. People say it looks like magic. Our customers are revolutionizing grazing with Halter, changing lives and transforming an industry. People join Halter to do meaningful work. By joining us you’ll be solving challenging problems within a talented team and a culture built for high performance. Our team out‑thinks, out‑works and out‑cares. We’re committed to delivering real change in the world – this isn’t easy, and in truth, we love that it’s hard.
Halter’s post‑sale engine, launch and support, is where our customer promise gets delivered. This role exists to make sure it performs.
You’ll sit within Revenue Operations & Enablement (part of GTM Operations), reporting to our Rev Ops & Enablement Lead, and based in our Auckland HQ. Your remit is global: you'll work across the NZ‑based 24/7 support team, regional support teams in the US, and launch teams in every market.
While our in‑market Rev Ops Managers (AU and US) predominantly focus on the sales cycle, you own the operational performance of everything that happens after the deal closes. How does the customer get launched? How does the support experience run? Where does it break? Where is it slow? You're expected to know, and to fix it.
You’ll own the operational processes, reporting, and the outcome and success of our tooling for launch and support. To be clear: this is an operations role, not a product role. Our Product Managers and Ecosystem teams own what our product looks like and the tools we use. You own how the teams operate around and within it. They build the tool; you drive adoption, govern usage, feedback changes, and make sure the processes around it are tight.
You’ll work in close partnership with the VP of Customer, whilst your in‑market Rev Ops colleagues in AU and the US are your intelligence layer on the ground. They spot the local patterns; you act on them globally.
You’ll do it with AI as a core tool – not experimentally. We expect you to actively look for ways to reduce manual effort and accelerate how customer teams operate.
You could come from customer operations, customer experience, onboarding/implementation, or you’ve been the operational person in a scaling company who made the post‑sale experience actually work. The background is irrelevant. What matters is how you think.
You think in processes. You can look at how a team operates, see where it breaks, and design something better. You care about consistency and scalability, but you know that a process nobody follows is worse than no process at all.
You’re data‑driven. You build reporting, define metrics, and use data to diagnose problems and track whether your changes are actually working. You don’t guess. When something looks off, you dig until you find it.
You work across boundaries with credibility. You'll be partnering with the VP of Customer, regional team leads, a Product Manager, and your Rev Ops peers in AU and US. You influence without authority, navigate competing priorities, and people bring you in because the quality of your insight makes their decisions better.
You understand the difference between operations and product. You own how teams work and how tools are used. You don’t own the product roadmap. That boundary is clear in your head and it shapes how you operate.