Deutsch

Path From MOps Manager to Director of MOps: The Move Most Stall On

A few weeks ago I got a Slack message from a friend running MOps at a Series C company. Eight years in, Senior Manager title, owns Marketo and the SFDC sync, runs a team of two contractors. The message: "Hey can you pull a quick list for the webinar tomorrow? It's a small ask, the AE is panicking, sales-op is out."

She did the pull. Took her 18 minutes. The webinar was fine. Her one-on-one with the CMO was the next morning, and she walked in without the architecture memo she'd been meaning to write for six weeks. Got passed over for Director that cycle. Again.

Every time you say yes to that Slack message, you delay your Director promotion by a quarter. That's not a guilt trip. That's the actual mechanism.

The Campaign-Launcher Trap

Most MOps managers stall at the same place, for the same reason: they got really good at being the campaign launcher. The person ops asks when an email won't send, when attribution looks weird, when the SFDC sync drops 800 leads overnight. The work is endlessly available, always urgent, and totally invisible at the leadership table.

Here's the trap. The campaign queue is infinite. There is always one more list pull, one more QA pass, one more "can you just check this real quick." And because you're fast, and because nobody else can do it, and because saying no feels rude or political, you stay in the queue. Your calendar fills with 25-minute fire drills. Your week looks productive. Your year looks the same as last year.

Leadership rewards fire-fighting in the moment. Promotions go to architects.

Tenure stops mattering after year four or five. I've watched Senior Managers with seven years of Marketo experience get passed over for someone with three years who shipped a stack consolidation and saved $180K. What matters at the Director cycle is whether you've owned a system decision, not how many emails you've QA'd.

Quick self-test: in the last six months, have you built anything that wasn't asked of you? Not a campaign, not a list, not a workflow fix. A memo, an architecture doc, a vendor evaluation, a hiring plan. Something that exists because you decided it should. If the answer is no, you're in the trap.

What Actually Changes at Director

The role flip is sharper than most JDs admit. Director of Marketing Operations isn't "Senior Manager, Marketing Operations" with more reports. It's a different job that happens to share an org chart with the one you have.

You own the martech strategy. That means defending the stack to the CMO and the CFO, including the kills and consolidations. You walk into a board-prep meeting with a slide on cost-per-MQL by tool. When the CFO asks why the company spends $420K a year on six platforms, you have an answer that isn't "because we always have." You're the person who recommends ripping out 6sense or keeping it. Big-platform decisions live with you, not with the CMO and not with procurement.

You manage 2-4 ICs. You hire them, ramp them, run their reviews, and fire them when needed. Half your week becomes one-on-ones, hiring loops, and unblocking the team. The good news: a ramped IC can do the campaign QA you used to do. The bad news: you're now responsible for whether they ramp, and that's a skill nobody taught you in your last role.

You defend stack ROI. You justify the $400K-a-year martech bill to a CFO who has never opened Marketo and doesn't want to. You build the renewal calendar. You write the consolidation memo. You run the "do we really need this" review every Q4 before budget lockdown. When sales ops wants to add Gong, you're the person who says yes or no based on what it does to your data model.

Net it out: less than 20% of your week is in the tools. If you still want to be in Marketo every day building flows, Director is the wrong role. The right role is Senior IC at a top company, sometimes called Principal Marketing Operations or Staff MOps Engineer, and at the senior end it pays similarly without the management load. That's a real and respectable path. But it's not Director.

The 4 Capabilities to Build Now

These are the four capabilities every Director hire I've seen in the last three years could demonstrate before the promotion. Pick one and run a project this quarter. Don't try to do all four at once.

Architecture vision

Can you draw the lead-to-revenue data flow on a whiteboard from memory? Form fill, MAP capture, lead scoring, SFDC sync, routing rules, MQL trigger, SDR queue, opportunity creation, attribution model, revenue close. Not just the boxes, but the field-level handoffs, the dedupe logic, the timezone gotchas, the places the data lies.

Can you name the three places your stack will break at 5x scale? Most stacks have a Marketo program limit, an SFDC API call ceiling, and a sync latency cliff that nobody notices until volume doubles. If you can't name yours, you're an operator, not an architect.

Practice this in your current role: write a one-page "current state vs. 18-month state" memo for your manager, unprompted. Two columns. Where the stack is now, where it should be in 18 months, what blocks the move. Send it without being asked. The act of writing it is half the rep. The memo getting circulated is the other half.

Hiring and coaching

Can you write a JD that filters out 80% of applicants on the first read? Most MOps JDs are checklist mush ("experience with Marketo or HubSpot, strong attention to detail, collaborative team player"). A good JD has a specific architectural problem in it: "you'll lead the consolidation of our 11-platform stack down to 7 in your first 12 months." That JD repels the wrong candidates and pulls the right ones.

Can you give an IC feedback that makes them better, not defensive? This is the actual skill nobody hands you. Most first-time managers either avoid hard feedback (and the IC plateaus) or deliver it wrong (and the IC quits). The middle path is a learnable craft. Read Kim Scott if you haven't.

Practice: ask to run the next contractor hire end-to-end. Sourcing, screening, scoping, the work test, the offer. Run weekly skip-level coffees with one IC on another team to get coaching reps without the org politics. You're not their manager so the stakes are low and the feedback honest.

Vendor management

Can you negotiate a renewal? Not "ask for a 10% discount." Actually run the negotiation, with a walk-away point, a competitive bid, and a usage analysis the rep hasn't seen. Vendors give 15-25% off renewals to anyone who does the work. Most MOps managers don't, and their company eats the auto-renewal.

Can you run a vendor evaluation that doesn't take six months? The classic mistake is a 40-criteria scorecard that paralyzes the team. The good evaluation is three to five criteria that map to actual business outcomes, two to three vendors, two-week scoping, decision in 30 days.

Can you kill a tool without breaking four workflows? This is the real test. Every tool in your stack has a long tail of dependencies: a workflow, a view, a Slack channel, three reports somebody on demand gen relies on. Sunsetting a tool cleanly is a skill.

Practice: own the next renewal cycle for one mid-tier tool, $30-80K range. Build the comparison matrix yourself. If your manager pushes back, ask to shadow them on the bigger renewal. Either way, you get the rep.

Exec narrative

Can you walk into a CMO one-on-one with three slides and leave with a decision? Not 30 slides, not a 12-page doc. Three slides: problem, options, recommendation. Most MOps managers either skip the meeting because they're "too operational" or show up with a 47-tab spreadsheet that gets nodded at and ignored.

Can you translate "the SFDC sync is flaky" into "we're losing $X in pipeline attribution per quarter"? Every operational fact has a dollar number behind it. The Director-track move is finding that number and leading with it. "Our sync drops 3% of leads" is a ticket. "Our sync drops 3% of leads, which is roughly $1.4M in misattributed pipeline last year" is a board slide.

Practice: volunteer to present MOps health to the marketing leadership team once a quarter. Get the reps in front of execs while the stakes are low. The first one will be rough. The fourth one will get you noticed.

Comp Reality Check (US, 2026)

Real numbers. Sourced from running the Director-of-MOps hiring loop at three companies in the last 18 months and comparing notes with a dozen peers. These are 50th to 75th percentile bands at Series B through pre-IPO SaaS companies, US.

Role Base salary Total comp (base + bonus + equity vest/yr) Scope
Marketing Ops Manager $105K – $140K $115K – $160K Owns 1-2 platforms, maybe 1 contractor
Senior MOps Manager $130K – $165K $150K – $200K Owns the full stack, 1-2 ICs, partial budget authority
Director of MOps $160K – $210K $200K – $280K Owns martech P&L, 2-4 ICs, sits on marketing leadership

Notes on the bands:

  • Title patterns matter at the offer stage. "Senior Manager, Marketing Operations" and "Director, Marketing Operations" are the title pivot points companies use to anchor offer letters. If you're being recruited and they slot you as Senior Manager when you've been doing Director work, the gap is real money. Negotiate the level, not the salary number.
  • Non-US adjustments: roughly 30% discount in EMEA, 40% in APAC. London and Singapore run hotter than the regional average. Equity is the swing factor at Director and above. A $200K total comp at a flat-equity company can be a $280K total comp at a fast-growing one.
  • Equity ramps faster than base. A Director offer at a Series C will usually have $40-80K of annual equity vest baked in. A Manager offer rarely clears $20K. That delta compounds across a 4-year vest.

The gap from MOps Manager to Director is roughly $70-100K in total comp. That's a real lifestyle delta. And it compounds: once you're at Director, the next jump (VP Marketing Operations, Head of Revenue Ops) opens up. Stay a Senior Manager for four more years and the next jump narrows, because companies stop seeing you as a Director candidate around year nine without a director-level project to point to.

The 18-Month Plan

Starting Monday. Not "Q3 next year." Monday.

Months 1-3. Pick one capability (architecture or vendor are the two with the cleanest one-quarter projects) and run a contained project. Architecture: a stack-state memo and a 5x-scale break analysis. Vendor: own a renewal, build the comparison matrix, run the negotiation.

Months 4-9. Take a hiring or management rep. Even a contractor hire counts. If your company won't let you, find a peer manager and offer to co-run their next loop. The skill rep is what counts; the formal headcount comes later.

Months 10-15. Present to execs. Own one renewal. Write the consolidation memo. By month 12 you should have one tangible artifact in each capability bucket: a memo, a hire, a renewal outcome, an exec presentation.

Months 16-18. Have the promotion conversation with receipts. The architecture doc, the hiring outcome, the vendor savings number, the exec presentation. The conversation isn't "I think I'm ready." It's "here are the four projects I ran, here's what they returned, here's what I'd do as Director." If the company says no, you have a portfolio that gets you a Director title at the next company in 60 days. I've watched this exact playbook work three times in two years.

Closing

The path is real but it's not automatic. The campaign queue will fight you for it. Every urgent Slack message is a vote against your promotion, and the people sending those messages don't know they're casting it. They just need a list pulled.

Pick one capability this quarter. Block four hours a week for it on your calendar. Title the block something boring like "ops review." Defend that block like it's a meeting with the CEO, because functionally it is. That's the time you spend becoming the person who gets the next title. Decline the list-pull, the urgent QA, the "real quick" Slack ask, during that block. Rude is fine. Promoted is better.

Learn More