RevOps Systems Analyst
Save this job and keep your search organized
Create a free account to save jobs, create alerts and return to this listing from your dashboard.
By continuing, you agree to our Terms & Privacy Policy.
IMPORTANT: Please be aware scammers may try to impersonate Zello by reaching out regarding job opportunities. We will never ask you for bank account information checks or other sensitive information as part of our hiring process. All correspondence will come from the email domain. If youre unsure please email with questions.
About Zello
Zello is a voice-first communication platform powered by our industry-leading push-to-talk technology to improve collaboration and productivity for desk-less workers. With over 175 million users were the #1 rated push-to-talk app in the world delivering 9 billion (yes with a B) messages a month.
At Zello our company values are at the heart of what we do everyday. Were proud to serve the frontline were privileged to connect people in times of crisis across the globe and were honored to support first responders.
And this is where you come in.
Zello keeps frontline and deskless teams connected through voice-first push-to-talk communication. Behind that business sits HubSpot and today it runs on workarounds: automations patched by hand integrations that break quietly and data quality nobody owns end to end. This role exists to own the CRM as a system so that revenue decisions rest on data people trust and the AI automations we are building can actually run on it.
You would be one of two people on the Revenue Operations team reporting directly to the Chief Revenue Officer. The other seat owns forecasting and analysis. You own the systems those numbers come out of.
After a successful first year you will have
Inventoried and rebuilt the HubSpot workflows and automations the business depends on each one documented with its owner and its dependencies and retired the manual patches holding them together.
Established a CRM data quality standard that holds: required fields defined by object and stage a weekly exception report people act on and stale or incomplete records down to an agreed threshold.
Rebuilt and instrumented the integrations between HubSpot and the rest of the stack so data moves without manual reconciliation and a failed sync raises an alert instead of being discovered three weeks later.
Made the CRM solid enough to build AI on with at least two AI-driven go-to-market automations running in production against HubSpot data and no human correcting them in the loop.
Taken ownership of the RevOps intake queue with a published response standard so Sales Customer Success and Marketing get answers without escalating to leadership.
What youll do
Own HubSpot as the administrator of record: workflows objects and properties lifecycle stages list architecture permissions and sequences.
Own the data flowing in and out of the CRM including the integrations with the website Gong Aircall billing and our BI layer in Omni.
Find the root cause when data goes wrong and build the recurring audit that catches it next time rather than cleaning it up by hand again.
Build and maintain automations with APIs webhooks and light scripting where native HubSpot tooling runs out.
Partner with the AI and Data team on the data structures and field integrity that AI-driven go-to-market automations depend on.
Run the RevOps request queue for Sales Customer Success and Marketing and decide what gets fixed properly versus worked around.
Hold the data standard when a team wants an exception and explain the tradeoff in terms of what it costs downstream.
Support lead and list operations from event intake through upload so records enter the CRM clean.
Who you are
You have administered HubSpot hands-on in a revenue operations context and you can walk through a workflow architecture you built and what you would do differently now.
You bring 2 to 4 years in RevOps SalesOps or CRM operations ideally in B2B SaaS.
You fix the cause rather than the symptom and you build the check that catches the problem next time instead of doing the cleanup twice.
You have connected a CRM to ot