Skip to main content

Operations career ladder: levels, titles, and criteria

Career levels, titles, scope, and promotion criteria for operations roles — from entry level to senior leadership.

operations career ladder — quick overview

An operations career ladder typically runs: Operations Coordinator → Operations Analyst/Associate → Operations Manager → Senior Manager / Director of Operations → VP of Operations → COO. Revenue operations (RevOps) and business operations are increasingly distinct tracks with parallel structures that converge at Director level.

Turn this ladder into a live framework for your team. Start free →

Operations IC career levels

Level Title Scope Key differentiator Typical YoE
L1 Operations Coordinator Process execution; coordination; scheduling Executes defined processes; coordinates across teams; builds ops muscle in one function 0–2
L2 Operations Analyst / Associate Process improvement; data analysis Analyzes operations data; identifies bottlenecks; builds tooling and dashboards; runs projects 2–4
L3 Operations Manager Owns a function or ops for a team Runs the operating system for a business function; manages cross-functional processes; owns tooling stack 4–7
L4 Senior Manager / Director of Operations Full ops for a business unit Designs org operating model; partners with GMs and execs; manages managers; owns operating rhythm 7–12
L5 VP of Operations Company-wide operations Owns all operational functions; drives strategic ops programs; company-level decision-making partner 12+
L6 COO Company-wide operating execution Owns execution of company strategy; reports to CEO; manages function heads; board-level responsibility 15+
Note: RevOps track (BDR Operations → Revenue Operations Analyst → RevOps Manager → Director of RevOps → VP RevOps) typically converges with general ops at Director level. BizOps is similar, often tied more tightly to strategy and CEO/leadership team work.

How the Operations career path progresses

An operations career path starts with executing a process someone else designed and ends with owning how the whole company runs. Early roles are about doing the work reliably: coordinating schedules, running a checklist, keeping a process moving. As the role grows, the work shifts from executing a process to designing one, then to deciding which processes the business needs at all. RevOps and BizOps are common specialist entry points that converge with the general operations ladder around the Director level.

  1. 1

    Execute defined processes

    As an Operations Coordinator, the job is running an existing process correctly: scheduling, coordinating across teams, handling logistics. There is little ambiguity in what to do, only in doing it well.

  2. 2

    Start improving what exists

    As an Operations Analyst or Associate, the work shifts from following a process to questioning it: analyzing operations data, finding bottlenecks, building the dashboards and tools that make the next person's job easier.

  3. 3

    Own a function's operating system

    As an Operations Manager, the scope becomes a whole function or team's operations: owning the tooling stack, running cross-functional processes end to end, and being accountable when something in that function breaks.

  4. 4

    Design the operating model, not just run it

    As Senior Manager or Director of Operations, the job becomes designing how a business unit operates, its rhythm of planning, reporting, and decision-making, in partnership with the GM or exec who owns that unit.

  5. 5

    Take on company-wide ownership

    VP of Operations owns operational functions across the whole company and becomes a regular partner in company-level strategic decisions, not just execution of them.

  6. 6

    Own execution of company strategy

    COO reports to the CEO and owns turning strategy into execution across every function, with board-level accountability for how the company actually runs day to day.

Note: RevOps (BDR Operations to Revenue Operations Analyst to RevOps Manager to Director of RevOps to VP RevOps) and BizOps are common specialist entry points into this ladder. Both typically converge with the general operations track around the Director level.

Skills and competencies by level

Each level below lists the hard skills (tools, techniques, deliverables) and soft skills (judgment, communication, stakeholder handling) that typically distinguish it.

Entry (Coordinator, Analyst/Associate)

Hard skills

  • Process tracking. Builds and maintains a tracker or checklist that others rely on.
  • Dashboard building. Answers a recurring question automatically instead of on request.
  • Process documentation. Writes it up clearly enough that someone else could run it.
  • Basic data analysis. Uses spreadsheets or simple queries to find where a process is breaking.

Soft skills

  • Cross-team coordination. Works across two teams without needing a manager to referee.
  • Upfront clarification. Asks the right question before starting a task, not after doing it wrong.
  • Early risk flagging. Raises a risk before it becomes a visible problem.
  • Workload organization. Keeps track of many small, unrelated tasks at once.

Mid (Operations Manager)

Hard skills

  • Tooling ownership. Owns a stack end to end, including evaluating and migrating to a replacement.
  • Process ownership. Runs it end to end, including the metrics that show it's working.
  • Metric diagnosis. Digs into the underlying data, not just the headline number.
  • Operating rhythm design. Sets the planning cadence and reporting cycle for a function.

Soft skills

  • Cross-team buy-in. Gets a team that doesn't report to them on board with a new process.
  • Build-versus-buy judgment. Makes the call and defends it under budget pressure.
  • Priority juggling. Handles competing asks from multiple stakeholders without dropping any of them.
  • Difficult feedback delivery. Gives it to a peer or vendor without damaging the working relationship.

Senior (Senior Manager, Director, VP)

Hard skills

  • Operating model design. Sets the planning cycle, reporting structure, and decision rights for a full business unit.
  • Budget reallocation. Moves budget or headcount across functions based on data, not politics.
  • Investment case building. Makes the case for an operational investment that a GM or exec will actually approve.
  • Department standards setting. Decides the tooling and standards a whole department's operations run on.

Soft skills

  • Executive partnering. Acts as a genuine operational counterpart to a GM or exec, not an order-taker.
  • Managing managers. Is accountable for their output, not just their own work.
  • Conflict navigation. Resolves conflicting priorities between departments without escalating everything upward.
  • Company-level representation. Speaks for operations credibly in company-level planning conversations.

Leadership (COO)

Hard skills

  • Strategy execution. Owns turning the company's strategic plan into results across every function.
  • Operating cadence setting. Decides the board reporting, planning cycles, and review rhythm the company runs on.
  • Company-wide metric reading. Knows exactly where to intervene personally from the numbers alone.
  • Org structure design. Decides how the company itself is organized.

Soft skills

  • Board accountability. Owns operational results at board level, including delivering bad news clearly.
  • Executive trust building. Earns standing with the CEO and other leaders as the person who makes strategy actually happen.
  • High-stakes intervention. Steps into the hardest cross-functional problems without taking over every team's job.
  • Operational discipline standard. Sets a bar for rigor that other leaders follow.

Common questions

Frequently asked questions

Build your Operations career framework in Harmny

Turn this career ladder into a live system — employees see their gap to the next level, and development goals connect directly to the framework.