Director, Operations Business Partner - Enterprise

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - Position Overview: description of role. Could be "About the role". Use

About the role

then

with overview. - Responsibilities: list of responsibilities under headings: Field Partnership & Problem Solving, Operations Execution & Alignment, Business Planning & Insight. We can combine into a

• each bullet. - Minimum Qualifications: list of qualifications. Could be under Requirements or Qualifications. Use

  Qualifications

  maybe. Provide list. - Skills: maybe not explicit separate; but we have "Strong communicator", "Proficiency with Salesforce", etc. Could be part of qualifications. We'll treat as Skills section if we have explicit skill list. The posting mentions: "Proficiency with Salesforce and sales and operational tooling; comfortable enough with data to know what questions to ask and when the numbers do not add up", "Gets things done without direct authority across a wide functional surface", "Strong communicator — translates operational complexity into clear recommendations". These could be skills. We'll create a Skills section. - Benefits: there is a Benefits paragraph: "From health and financial benefits to time away and everyday wellness, we give Autodeskers the best, so they can do their best work. Learn more about our benefits in the U.S. by visiting https://benefits.autodesk.com/". That's specific enough to include Benefits section. - Pay: Salary transparency: "Salary is one part of Autodesk’s competitive compensation package. For U.S.-based roles, we expect a starting base salary between $162,500 and $262,790. Offers are based on the candidate’s experience and geographic location, and may exceed this range. In addition to base salaries, our compensation package may include annual cash bonuses, commissions for sales roles, stock grants, and a comprehensive benefits package." That's specific pay info. So include Pay section. - Schedule: Not mentioned. No schedule info. So omit Schedule. - Also there is "Learn More About Autodesk" etc. That's boilerplate? It's marketing but maybe not needed. We can omit as it's not substantive about role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More About Autodesk" is marketing but maybe considered boilerplate? It's not required. We'll omit. - Also "Equal Employment Opportunity", "Belonging", "In-Person Onboarding and Identity Verification" are boilerplate/legal; omit. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We need to preserve all substantive information; not invent or summarize away detail. Must not omit details like specific responsibilities bullet points. Let's extract details. About the role: The Position Overview paragraph(s). Let's copy: "As Director, Operations Business Partner, you are the dedicated operations partner for Autodesk's Enterprise Customer Sales business. You are embedded with senior Enterprise Sales and CS leadership, serving as their primary point of accountability for the business’s operations. You are responsible for diagnosing and resolving the Enterprise team's highest-impact operational and business challenges, especially those that cut across systems, functions, and organizational boundaries, and you are the direct interface back into Autodesk's Revenue Operations team and other supporting organizations. This is not a coordination or facilitation role. You are accountable for outcomes — doing the work yourself where you can and driving teams to deliver where you can't. What you never do is hand off accountability. The problems are real, the stakeholders are senior, and the work directly affects how a multi-billion-dollar software business operates and executes in the field. When this role is working well, Enterprise leadership moves faster, operational gaps close before they become business issues, and the connection between the field and the broader organization is stronger. That outcome is yours to drive." We can keep that as

  . What Success Looks Like: Could be part of About the role or separate? It's more about success metrics. Could be included in About the role or maybe as part of Responsibilities? But we can incorporate into About the role as additional paragraph. However we need to preserve all substantive info. Let's include it as part of About the role (maybe separate

  ). We'll keep. Responsibilities: There are three subheadings with bullet-like sentences. Field Partnership & Problem Solving: - Get into the details of how the Enterprise Sales business operates — understand the sales process, the execution gaps, and the friction points at the ground level - Diagnose operational problems yourself: talk to the field, form a clear point of view, and drive toward a solution before escalating or engaging others - Identify patterns across field conversations, business performance, and stakeholder input to isolate systemic issues — and act on them, not just report them - Reframe ambiguous or misdiagnosed problems into clear, solvable questions; get senior stakeholders aligned and moving toward resolution Operations Execution & Alignment: - Own operational issues end-to-end — do the work yourself where you can, pull in the right teams where you need to, but never hand off accountability for the outcome; your interface extends beyond the Revenue Operations team to include Marketing, Customer Success, and Finance - Build and run the operational rhythms that keep the Enterprise Sales business on track: status reviews, escalation loops, issue tracking, and field feedback channels - Build the business case for what needs to change — pressure-test the logic, align stakeholders across functions, and present a clear recommendation - Push back on field requests that are not enterprise-aligned; make the call on what to prioritize and what not to Business Planning & Insight: - Represent the Enterprise Sales field perspective directly in annual planning, segmentation design, coverage model changes, and policy development — not through a proxy - Identify and synthesize systemic patterns from the field that should reshape how Revenue Operations programs are designed and resourced - Prepare and deliver operational context for leadership reviews — own the narrative, not just the slides We'll put each as

• under a
  . Could group under one list or separate lists per subheading. The instruction: Use
  • for any list of duties/requirements/benefits. It doesn't forbid headings inside list? Probably better to keep subheadings as

    ? But only allowed headings are

    for section headings. We could keep subheadings as plain text within

    or as . Simpler: just list all responsibilities as bullet points without subheadings. But we might lose some structure but still preserve content. However we could embed subheadings as part of the bullet text. That's fine. We'll create a

    with each bullet as a sentence. Minimum Qualifications: list: - 10+ years in Revenue Operations, Sales Operations, Business Operations, or a related business partner role at an enterprise technology company - Direct experience supporting VP and SVP-level Sales leaders in an embedded, field-facing capacity - Deep understanding of at least one sales motion: enterprise sales, Enterprise Sales, expansion, or commercial/emerging business - Strong problem-solving orientation — ability to diagnose friction, define root causes, and drive cross-functional resolution; top-tier consulting (McKinsey, Bain, BCG) or equivalent in-house strategy experience is a strong signal - Proficiency with Salesforce and sales and operational tooling; comfortable enough with data to know what questions to ask and when the numbers do not add up - Gets things done without direct authority across a wide functional surface — Revenue Operations, Marketing, Customer Success, Finance — comfortable making calls, taking ownership, and moving fast in complex organizations - Strong communicator — translates operational complexity into clear recommendations for both field leaders and central operations teams We could split into Qualifications and Skills. But the instruction: Use sections for Requirements, Qualifications, Skills. We have qualifications (experience, years, etc.) and skills (proficiency, problem solving, communication). We'll create Qualifications section for the experience/education requirements, and Skills section for the abilities. Thus: Qualifications (

    Qualifications

    ) list: - 10+ years in Revenue Operations, Sales Operations, Business Operations, or a related business partner role at an enterprise technology company - Direct experience supporting VP and SVP-level Sales leaders in an embedded, field-facing capacity - Deep understanding of at least one sales motion: enterprise sales, Enterprise Sales, expansion, or commercial/emerging business Skills (

    Skills

    ) list: - Strong problem-solving orientation — ability to diagnose friction, define root causes, and drive cross-functional resolution; top-tier consulting (McKinsey, Bain, BCG) or equivalent in-house strategy experience is a strong signal - Proficiency with Salesforce and sales and operational tooling; comfortable enough with data to know what questions to ask and when the numbers do not add up - Gets things done without direct authority across a wide functional surface — Revenue Operations, Marketing, Customer Success, Finance — comfortable making calls, taking ownership, and moving fast in complex organizations - Strong communicator — translates operational complexity into clear recommendations for both field leaders and central operations teams Benefits: as given. Pay: as given. Now ensure we don't include any boilerplate like "Learn More About Autodesk", "Equal Employment Opportunity", etc. Now produce HTML fragment. We'll wrap each section in

    and then content. For About the role: maybe two paragraphs: overview and success. We'll output:

    About the role

    As Director, Operations Business Partner, you are the dedicated operations partner for Autodesk's Enterprise Customer Sales business. You are embedded with senior Enterprise Sales and CS leadership, serving as their primary point of accountability for the business’s operations. You are responsible for diagnosing and resolving the Enterprise team's highest-impact operational and business challenges, especially those that cut across systems, functions, and organizational boundaries, and you are the direct interface back into Autodesk's Revenue Operations team and other supporting organizations. This is not a coordination or facilitation role. You are accountable for outcomes — doing the work yourself where you can and driving teams to deliver where you can't. What you never do is hand off accountability. The problems are real, the stakeholders are senior, and the work directly affects how a multi-billion-dollar software business operates and executes in the field. When this role is working well, Enterprise leadership moves faster, operational gaps close before they become business issues, and the connection between the field and the broader organization is stronger. That outcome is yours to drive.

    What Success Looks Like: Sales leadership makes operational decisions faster, with fewer escalations to the central Revenue Operations team and supporting organizations. Operational gaps are identified and resolved before they affect field execution. The central Revenue Operations organization and critical stakeholders receive timely, business-contextualized input that sharpens how specialist teams prioritize.

    Note: The success text originally: "What Success Looks Like Sales leadership makes operational decisions faster, with fewer escalations to the central Revenue Operations team and supporting organizations. Operational gaps are identified and resolved before they affect field execution The central Revenue Operations organization and critical stakeholders receive timely, business-contextualized input that sharpens how specialist teams prioritize". We need to preserve punctuation. We'll add periods. Now Responsibilities:

    Responsibilities

    • Get into the details of how the Enterprise Sales business operates — understand the sales process, the execution gaps, and the friction points at the ground level
    • Diagnose operational problems yourself: talk to the field, form a clear point of view, and drive toward a solution before escalating or engaging others
    • Identify patterns across field conversations, business performance, and stakeholder input to isolate systemic issues — and act on them, not just report them
    • Reframe ambiguous or misdiagnosed problems into clear, solvable questions; get senior stakeholders aligned