COO

Ryan Mahoney

Why this role is hard · Ryan Mahoney

This role sits at a brutal intersection: close enough to the work to smell the burning wires, far enough to be accountable for the system. You need someone who can hear what engineering is not saying about technical debt while translating that into budget language the CFO actually accepts. The real test is not running a process improvement workshop; it is telling a founder their favorite vendor contract is a liability, then rebuilding that relationship without losing the tool entirely. Most candidates can do one side of this. The rare ones hold both tensions without collapsing into pure diplomat or pure enforcer. Look for evidence they killed a popular project because the math stopped working, not because someone senior asked them to.

Core Evaluation

Critical questions for this role

The competency and attitude questions below are where the hiring decision is made. They run in the live interview rounds and are calibrated to the level selected above.

21 Competency Questions

1 of 21

  1. Discipline

    Organizational & Customer Experience

  2. Job requirement

    Customer Success Operations

    Manages customer success platforms and health scoring systems; oversees support workflows and escalation processes.

  3. Expected at Mid

    Independent oversight of customer success platforms and escalation workflows is essential to prevent churn and SLA breaches. The manager must autonomously configure health scoring systems and optimize support routing, enabling proactive intervention on at-risk accounts and maintaining enterprise customer trust.

Interview round: Cross-Functional Leadership Panel

Describe how you built visibility into customer health and success that actually helped the team prioritize and intervene. What did you create, and how did it land?

Positive indicators

  • Acknowledges false positives and negatives in health scoring
  • Describes specific interventions triggered by health signals
  • Shows empathy for CSM workflow and cognitive load
  • Mentions how they handled data gaps for new or small customers

Negative indicators

  • Proposes perfect predictive model without organizational readiness
  • Ignores CSM feedback on signal quality
  • Focuses on dashboard creation without usage
  • Shows no awareness of customer segmentation needs

19 Attitude Questions

1 of 19

Active Listening

The disciplined cognitive and behavioral practice of fully concentrating on, comprehending, and responding to spoken and unspoken communication in ways that validate the speaker's perspective, surface latent meaning, and create psychological safety for complete information sharing. For COOs, this involves suspending operational solutioning temporarily to ensure all stakeholder knowledge—especially inconvenient or politically sensitive intelligence—is fully extracted before integration into decision-making.

Interview round: Recruiter Screen: Culture & Role Fit

You're in a planning session where two department heads are talking past each other, both insisting the other doesn't get it. You've been asked to help. What's your first move?

Positive indicators

  • Proposes separate conversations before joint problem-solving
  • Mentions checking for unstated goals or fears driving positions
  • Describes neutral language to reflect back what they heard
  • Considers timing and setting for productive dialogue

Negative indicators

  • Immediately proposes compromise without deeper understanding
  • Sides with one party based on title or relationship
  • Jumps to process or framework without diagnosing the gap
  • Assumes bad faith or incompetence from one party

Supporting Evaluation

How candidates earn the selection conversation

The goal is to reduce effort for everyone by collecting more useful signal before adding more interviews. Lightweight application prompts and structured screens help the panel focus live time on the candidates most likely to succeed.

Stage 1 · Application

Filter at the door

Runs the moment a candidate hits Submit. Disqualifying answers end the application; everything else is captured for review.

Video-Response Questions

1 of 3

Application Screen: Video Response

Describe a scenario where product and engineering leadership presented conflicting priorities during quarterly OKR planning. What specific communication approach would you use to synthesize these inputs, clarify decision rights, and secure buy-in without compromising team capacity?

Candidate experience

REC
0:42 / 2:00
1Record
2Review
3Submit

Response time

2 min

Format

Recorded video

Stage 2 · Resume Screening

Read the resume against fixed criteria

Reviewers score every application that clears the door against the same criteria. Stronger reviews advance to live interviews; weaker ones are archived without further screening.

Resume Review Criteria

8 criteria
Evidence of designing and maintaining lightweight operational workflows that connect product planning, engineering delivery, and go-to-market readiness without introducing approval bottlenecks.
Evidence of building or maintaining operational dashboards, CRM hygiene systems, or hiring analytics that translate activity data into actionable visibility for leadership.
Evidence of facilitating quarterly planning sessions, translating company strategy into team-level priorities, and managing alignment rituals across distributed functions.
Evidence of creating function-specific onboarding programs, training curricula, or enablement resources that accelerate time-to-productivity for new hires across engineering, sales, or operations.

Is the resume complete, well-organized, and free from formatting, spelling, and grammar mistakes?

Does the resume show relevant prior work experience?

Does the cover letter or personal statement convey clear relevance and familiarity with the job?

Does the resume indicate required academic credentials, relevant certifications, or necessary training?

Stage 3 · During Interviews

Where the hire is decided

Interview rounds use the competency and attitude questions outlined above, then add tests, work simulations, and presentations that reveal deeper evidence about how the candidate thinks and works.

Presentation Prompt

Prepare a short deck walking us through a time you redesigned an end-to-end operational workflow to reduce cross-functional friction. Discuss your approach to stakeholder alignment, process trade-offs, tool selection, and how you measured the impact on delivery velocity.

Format

deck-and-walkthrough · 20 min · ~2 hr prep

Audience

Operations leadership and functional heads.

What to prepare

  • 3-5 slides outlining the problem context, your intervention strategy, stakeholder management approach, and retrospective outcomes.

Deliverables

  • A 15-20 minute presentation followed by Q&A.

Ground rules

  • Use only work you are permitted to share.
  • Anonymize sensitive data if needed.
  • We are evaluating your process design and change management judgment, not the specific tooling.

Scoring anchors

Exceeds
Demonstrates masterful workflow architecture, anticipates adoption friction, and ties operational changes directly to measurable velocity and quality gains.
Meets
Presents a coherent redesign process, shows reasonable stakeholder management, and defines clear success metrics.
Below
Relies on rigid templates, ignores cross-functional realities, or cannot articulate how adoption was achieved or measured.

Response time

20 min

Positive indicators

  • Clearly maps upstream/downstream dependencies and failure modes
  • Demonstrates structured stakeholder engagement without over-engineering consensus
  • Selects tools based on team capacity and integration needs, not vendor hype
  • Articulates how they measured success and iterated based on feedback
  • Balances standardization with team autonomy

Negative indicators

  • Focuses heavily on tool features rather than human workflow and adoption
  • Ignores resistance points or assumes compliance without change strategy
  • Proposes solutions that create new bottlenecks or approval layers
  • Lacks clear metrics linking operational changes to business outcomes
  • Over-relies on past processes without adapting to current startup scale

Work Simulation Scenario

Scenario. You are the Operations Manager responsible for standing up a lightweight product ops function to streamline the roadmap-to-release flow. Engineering, Product, and Design are currently operating with ad-hoc handoffs, causing missed deadlines and inconsistent quality gates. Facilitate a cross-functional discussion to decide on release cadence, ownership of readiness checks, and tooling integration within a constrained budget.

Problem to solve. Align Engineering, Product, and Design on a sustainable release cadence, clear ownership for readiness gates, and lightweight tooling integration that reduces friction without adding bureaucracy.

Format

cross-functional-decision · 40 min · ~2 hr prep

Success criteria

  • Drives a structured trade-off discussion that surfaces each function's constraints and incentives
  • Negotiates clear ownership boundaries for release readiness and quality checks
  • Proposes a lightweight tooling workflow that respects budget and autonomy constraints
  • Secures explicit commitments on cadence and escalation paths

What to review beforehand

  • Basic understanding of Linear, Notion, and release management workflows
  • Familiarity with cross-functional alignment and process design principles

Ground rules

  • You are facilitating a multi-party decision, not dictating a process
  • Each stakeholder has competing priorities; you must navigate trade-offs explicitly
  • Focus on decision rights, cadence, and lightweight tooling integration

Roles in scenario

Engineering Manager (cross_functional_partner, played by cross_functional)

Motivation. Protect engineering focus time and minimize context-switching from excessive release gates or manual documentation.

Constraints

  • Team is already at capacity; cannot support heavy release checklists
  • Strong preference for automated CI/CD gates over manual reviews
  • Budget for new tooling is capped at existing Linear/Notion stack

Tensions to introduce

  • Pushes back on adding manual 'release readiness' steps
  • Argues that design QA slows down sprint velocity
  • Wants to delegate release ownership to product ops but refuses to share pipeline data

In-character guidance

  • Defend engineering autonomy and velocity concerns
  • Agree to lightweight automation if it replaces manual steps
  • Challenge vague process proposals with concrete capacity questions

Do not

  • Do not propose the final release workflow
  • Do not concede on capacity constraints without explicit trade-offs
  • Do not volunteer pipeline integration details unless asked

Product Manager (cross_functional_partner, played by peer)

Motivation. Accelerate release cadence to hit quarterly roadmap targets while maintaining predictable delivery.

Constraints

  • Quarterly OKRs depend on shipping 3 major features on time
  • Lacks visibility into engineering blockers until late in the cycle
  • Cannot add headcount to manage release coordination

Tensions to introduce

  • Wants weekly releases to match GTM calendar
  • Pushes for product-led release readiness sign-off
  • Resists sharing roadmap changes early due to competitive sensitivity

In-character guidance

  • Emphasize speed and predictability
  • Push for clear escalation paths when blockers emerge
  • Agree to shared visibility if it protects release dates

Do not

  • Do not hand over roadmap details unprompted
  • Do not solve the coordination problem
  • Do not agree to slow cadence without clear risk mitigation

Design Lead (skeptical_stakeholder, played by peer)

Motivation. Ensure user experience and accessibility standards are validated before any feature ships.

Constraints

  • Small team of 3 designers covering 5 squads
  • Current review process is reactive, catching issues post-merge
  • Requires at least 48 hours for UX validation before release

Tensions to introduce

  • Insists on mandatory design sign-off for all customer-facing changes
  • Argues that skipping UX review will increase support tickets
  • Resists async-only feedback loops for complex interactions

In-character guidance

  • Advocate for quality and user impact
  • Push for explicit UX gates in the workflow
  • Negotiate async validation only if criteria are crystal clear

Do not

  • Do not volunteer design system documentation
  • Do not concede on quality standards without risk acknowledgment
  • Do not solve the scheduling conflict

Scoring anchors

Exceeds
Orchestrates a crisp, time-bound negotiation that surfaces hidden dependencies, aligns incentives through explicit trade-offs, and delivers a lightweight, owned workflow with clear escalation paths.
Meets
Facilitates a structured discussion that captures key constraints, proposes a reasonable release cadence and ownership split, and secures basic alignment on tooling and gates.
Below
Struggles to manage competing priorities, defaults to generic process templates without addressing constraints, or leaves decision rights and escalation paths unresolved.

Response time

40 min

Positive indicators

  • Structures the conversation to explicitly map incentives, constraints, and decision rights across functions
  • Negotiates clear ownership boundaries for release readiness and quality checks
  • Proposes a lightweight, tool-agnostic workflow that respects capacity and budget limits
  • Secures explicit commitments on cadence, escalation paths, and success metrics

Negative indicators

  • Allows the discussion to devolve into functional complaints without steering toward decisions
  • Imposes a top-down process that ignores capacity or autonomy constraints
  • Fails to clarify decision rights or escalation paths, leaving ownership ambiguous
  • Overcomplicates the workflow with excessive gates or tooling requirements

Progression Framework

This table shows how competencies evolve across experience levels. Each cell shows competency at that level.

Organizational & Customer Experience

4 competencies

CompetencyJuniorMidSeniorPrincipal
Customer Success Operations

Coordinates support ticket routing and basic customer data management; assists with CS metric tracking.

Manages customer success platforms and health scoring systems; oversees support workflows and escalation processes.

Designs customer success operations and retention strategies; implements CS technology stack and predictive health models.

Architects customer experience ecosystems; establishes enterprise-wide customer data platforms and success methodologies.

Knowledge Management

Maintains documentation repositories and assists with content organization; supports knowledge base updates and user queries.

Manages knowledge management systems and documentation standards; implements information architecture and content governance.

Designs organizational knowledge strategies; establishes enterprise search, content management workflows, and learning repositories.

Architects knowledge ecosystems and organizational learning infrastructure; pioneers AI-enhanced knowledge discovery and retention systems.

Security Compliance & Governance

Assists with compliance documentation and audit evidence collection; tracks security training completion and policy acknowledgments.

Manages compliance programs and security audits; coordinates risk assessments and implements security awareness training.

Leads security and compliance strategy; designs governance frameworks and manages regulatory relationships across jurisdictions.

Establishes enterprise risk governance architecture; shapes industry security standards and manages board-level cyber risk reporting.

Talent Systems & Workforce Operations

Coordinates HR administrative tasks and data entry; supports onboarding logistics and maintains employee records.

Manages HRIS configuration and recruiting operations; oversees onboarding programs and workforce analytics reporting.

Designs talent systems architecture and organizational development programs; leads workforce planning and HR technology strategy.

Architects global talent operating models; establishes people technology ecosystems and organizational design for scale.

Strategic & Financial Operations

4 competencies

CompetencyJuniorMidSeniorPrincipal
Financial Planning & Analysis

Supports budget tracking and variance analysis; maintains financial spreadsheets and assists with basic reporting templates and data entry.

Owns departmental budgeting cycles; develops financial forecasts and coordinates with accounting on month-end close processes and budget variance explanations.

Leads annual financial planning process; designs financial operating models and advises C-suite on capital allocation, burn rate optimization, and fundraising readiness.

Architects enterprise financial strategy; manages board-level financial reporting and investor relations while establishing fiscal governance policies for multi-entity structures.

Revenue Operations & Financial Systems

Supports billing operations and revenue data entry; assists with accounts receivable tracking and basic pricing list maintenance.

Manages revenue systems configuration; owns billing workflows, pricing implementation, and coordination between sales and finance on revenue recognition.

Leads RevOps strategy and systems architecture; designs pricing models, commissions structures, and scalable billing processes for growth stages.

Architects revenue infrastructure for global scale; establishes financial systems roadmap and leads M&A integration of revenue operations.

Strategic Procurement

Researches market options for strategic suppliers; assists in RFP processes and data collection for sourcing decisions.

Manages strategic sourcing projects; evaluates enterprise vendors and coordinates cross-functional selection committees for major purchases.

Leads strategic procurement initiatives for core infrastructure; negotiates enterprise agreements and establishes preferred vendor programs.

Sets organizational procurement philosophy; architects supply chain resilience strategies and manages C-level vendor partnerships.

Vendor & Contract Lifecycle Management

Assists in vendor research, contract filing, and performance tracking; maintains vendor databases and compliance documentation.

Negotiates standard vendor contracts; manages ongoing vendor relationships, conducts cost-benefit analyses, and resolves service delivery issues.

Owns vendor portfolio strategy and complex negotiations; builds vendor governance frameworks and manages strategic supplier partnerships.

Designs ecosystem partnership strategies; establishes enterprise-wide procurement policies, vendor risk frameworks, and category management methodologies.

Technical Infrastructure & Product Delivery

4 competencies

CompetencyJuniorMidSeniorPrincipal
AI Operations & Infrastructure

Supports AI tool evaluation and basic prompt engineering; monitors AI system usage and assists with data preparation.

Implements AI workflows for operational processes; manages AI vendor relationships and integration projects with existing systems.

Leads AI transformation roadmap for operations; establishes AI governance, prompt libraries, and automation frameworks.

Pioneers AI-native organizational design; shapes industry best practices for operational AI deployment and ethical AI governance.

Data Platform Engineering

Supports data pipeline maintenance and monitoring; assists with basic ETL tasks and data quality checks under supervision.

Develops and maintains data pipelines and warehouse models; manages data integration projects and ensures data quality standards.

Architects data platform strategy and infrastructure; designs data governance frameworks and scalable analytics architectures.

Establishes organizational data strategy and platform architecture; pioneers data mesh or similar paradigms and leads data ethics governance.

Engineering Reliability & DevOps

Monitors system alerts and assists with incident response coordination; maintains runbooks and documentation.

Manages on-call rotations and incident response processes; implements monitoring solutions and reliability improvements.

Leads site reliability engineering practices; designs incident management frameworks and infrastructure automation strategies.

Establishes organizational reliability standards; architects disaster recovery and business continuity systems at enterprise scale.

Product Delivery Orchestration

Coordinates meeting logistics and tracks project tasks; assists with status reporting and documentation of delivery processes.

Manages sprint planning and release coordination; facilitates cross-functional communication and removes blockers for delivery teams.

Leads delivery operations for product divisions; implements agile frameworks, capacity planning, and delivery metrics systems.

Architects organizational delivery systems; establishes portfolio management practices and scales engineering operations across multiple teams.