Careers
Now hiring on the technical team
Two seats on the technical team.
ATM is a fractional RevOps firm for B2B SaaS companies. One technical team serves every client, with no pods, and work reaches that team on two boards. The Support board is always open: client fixes, data cleanup, and “this report looks wrong.” The Initiatives board holds the planned builds behind each client’s quarterly rock (the one priority they’ve picked for the quarter).
Both seats are contract, remote in the US and Canada, and about 20 hours a week to start. Rates and scope grow as your impact does.
Four habits we hire for on every seat
The two roles below look different day to day. The people who do well in both have these in common.
- Draw the first map
When a request lands without context, you post a rough first pass and one question instead of waiting.
- Pull the thread
After the fix, you find out why it broke and whether it will break again.
- Close the loop
Half-done work bothers you. You follow up before anyone has to chase you.
- Leave the trail lit
You write things down so the next person never starts from a blank page.
RevOps Analyst
The entry seat on our Systems Specialist path
You keep the Support board moving. Think air traffic control: requests land any day, no more than four are in the air at once, and the rest hold in priority order until a runway opens. In practice, you triage each new ticket, work it from an SOP, and close it with notes the next person can use.
On the Initiatives board, you carry the tier 1 work every build stands on: the current-state inventory, imports and backfills, property setup, cleanup, and the first QA pass. The Lead RevOps Analyst reviews your work closely while you learn, and the seat comes with a written path toward RevOps Systems Specialist.
✦ You’ll thrive here if you
- Care about clean data. A duplicate record or a mislabeled property nags at you until it’s fixed.
- Like a steady flow of focused work. Ten well-closed tickets feel like a good day.
- Get faster from feedback. A QA note on your ticket is something you use on the next one.
- Write clearly. Most of our work happens in tickets and Slack.
✕ Probably not your seat if
- You want long build projects right away. This seat is smaller tickets, and you finish one before you start the next.
- You’d rather skip a step than follow the SOP.
- You want to spend most of your day on client calls. Your client contact is mostly async Slack.
What you’ll do
- Triage every new Support ticket within one working day.
- When you accept a ticket, post your plan and a by-when as the first comment.
- Work HubSpot and Salesforce hygiene: imports, dedupe, backfills, property cleanup, list and report fixes, and light workflow configuration.
- Pull the tier 1 tickets on each Initiatives build: current-state inventory, uploads and backfills, property setup, cleanup, and QA.
- Keep the Support board at four tickets in progress or fewer.
- When a ticket needs senior work, escalate it with your first pass attached: what you checked, how far you got, and your one question.
- Before you resolve a ticket, write the handoff note: what you did, where the work lives, and what someone picking it up cold needs to know.
- Answer async Slack questions for some clients.
What you bring
- 1 to 3 years of hands-on CRM admin or operations work in HubSpot, Salesforce, or both.
- Comfort with data: imports, deduplication, property logic, and reports.
- Nice to have: HubSpot Academy certifications or the Salesforce Administrator credential.
You’ll work with
- Lead RevOps Analyst: your QA reviewer, your first stop when you’re stuck, and your regular 1:1s.
- RevOps Systems Specialist: takes the tickets you escalate and walks you through the fix.
- Lead RevOps Systems Specialist: runs the delivery queue and assigns the work.
Your first 90 days
- By day 30: you’re resolving tier 1 tickets inside SLA and have the HubSpot and Salesforce basics down.
- By day 60: you’ve delivered a small build under review and you run hygiene for two clients.
- By day 90: you and your lead have written down the criteria for your next step toward Systems Specialist.
RevOps Systems Specialist
The senior builder on the team
You take the hard cases. Think ER attending: the analyst stabilizes the patient and sends up the cases that need a specialist, like a broken integration, a tangled workflow chain, or a data model problem. Each one arrives with the analyst’s first pass attached, and you find the root cause across HubSpot, Salesforce, and the tools connected to them.
You also ship the builds. Initiatives arrive sized and sequenced, with an approved design from our Solutions Specialist. You build to that design, attach your testing evidence, and anchor at least two clients as their primary or backup builder. The analyst working next to you gets better because you were there.
✦ You’ll thrive here if you
- Think like an admin. Properties, workflows, and Flows come before custom code.
- Get oriented fast. You can open an unfamiliar portal and have a working theory within the hour.
- Build to spec. When the design has a gap, you flag it instead of improvising around it.
- Teach through your work. Your notes and walkthroughs make the people around you better.
✕ Probably not your seat if
- You want greenfield architecture. Every build here starts inside a system someone else made.
- You’d rather fix it yourself every time than coach the analyst to fix the next one.
- You want to own the client relationship. Our client team holds that, so you get long focus blocks.
What you’ll do
- Escalations. Take every Support ticket the analyst escalates, diagnose the root cause, and document what you found.
- Builds. Pull tickets from the Initiatives board and ship them to the approved design, with testing evidence attached.
- Rescoping. When a fix turns out to be a build, flag it so it moves to the Initiatives board for the next sprint and the Support board keeps flowing.
- Coaching. Walk the analyst through escalations so fewer tickets need you over time.
- Handoff notes. Before you resolve a ticket: what you did, where it lives, and what the next person needs to know.
What you bring
- 4+ years in RevOps or CRM systems, with deep HubSpot experience and working Salesforce knowledge.
- Experience debugging workflows, integrations, and data models in production.
- Experience mentoring a junior teammate, or a clear interest in doing it.
- Comfort in a ticket-driven, async-first team.
- Nice to have: consulting or agency experience across multiple client stacks.
You’ll work with
- Lead RevOps Systems Specialist: runs the delivery queue, assigns your builds, and holds your 1:1s.
- RevOps Solutions Specialist: runs discovery and designs the builds you ship.
- RevOps Analyst: sends you escalations with a first pass and carries the tier 1 tickets on your builds.
Your first 90 days
- By day 30: you’re shipping Support tickets in two client orgs and know how we build.
- By day 60: you’ve delivered one full build from an approved design.
- By day 90: you anchor two clients, and your rework rate sits below the team baseline.
How we work
- One central hubOne technical team serves every client, so you’ll see a range of HubSpot and Salesforce stacks instead of living in one.
- Points for clients, hours for youClients buy bandwidth in points, so they pay for outcomes. You’re paid hourly for your time.
- Clear lanesProject Captains own client strategy and Client Experience Specialists own the day-to-day client relationship. That frees the technical team for focused design and build work.
- Small team, direct communicationDaily standup at 12pm ET, then open office hours. High trust, async-first, and questions are welcome.
Not interviewing for these today. Join the bench anyway.
When a seat opens, this list is the first place we look, before we post anything. We also look here when clients and people in our network ask us for candidate recommendations. Tell us which seat fits you and we’ll reach out when it opens.
-
Head of Technical ArchitectureJoin the bench
Owns the technical bar every solution has to clear: standards, sign-off on every design, Tier 3 escalations, and the technical interview round. No people management.
-
Head of Technical DeliveryJoin the bench
Owns who builds what, and when: the ClickUp queue, WIP limits, capacity in points, delivery timelines, and the people doing the building.
-
RevOps Solutions SpecialistJoin the bench
Runs discovery, designs the solution, and sizes it into tiered work packages with points. The seat between the sale and the build.
-
Project CaptainJoin the bench
Owns each client’s executive relationship and quarterly rock: business requirements, point-budget advice, renewal, and expansion.
-
Client Experience SpecialistJoin the bench
Owns the day-to-day: weekly cadence, intake and first triage of every request, and the Friday update. Keeps the inbox off the builders’ desks.