Manager, Data Operations

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: 1. Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for any list of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Company: Harley-Davidson Motor Company - Title: Manager, Data Operations - Location: JUNEAU (Onsite) - Full Time, Shift: SHIFT1 - Auto req ID: 61737 (minor metadata, fold into p or drop) - Job Summary: paragraph about the role - Job Responsibilities: list of responsibilities with sub-headings - Education Requirements: Bachelor's Degree Required, specifications - Experience Requirements: 8+ years experience, 5 years management, plus specific skills - Pay Range: $119,000 - $178,100 (stated) - Benefits: mentioned "inclusive compensation package... annual bonus programs, health insurance benefits, a 401k program, onsite fitness centers and employee stores, employee discounts on products and accessories, and more" - Travel Required: 0 - 10% - Visa Sponsorship: not eligible - Relocation: eligible for domestic relocation assistance - Direct Reports: Yes I need to structure this into sections. Possible sections: - About the role (from Job Summary) - Responsibilities (from Job Responsibilities) - Requirements (could combine Education and Experience) - Qualifications/Skills (from Experience Requirements technical skills) - Benefits (since they list specific benefits) - Pay (since pay range is given) - Additional details (travel, visa, relocation, direct reports) - maybe fold into a short p or separate section The rules say: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those headings where appropriate. I'll create: -

  About the role

  with the job summary paragraph -

  Responsibilities

  with a
  of the responsibilities (each bullet can be a main responsibility with sub-points? The posting has sub-headings like "Data Operations Management:", "Data Platform Infrastructure:", etc. I could make each a list item with the description, or make nested lists. Since they are distinct responsibilities, I'll make each a list item with the description as text.) -

  Requirements

  with education and experience requirements. Could split into Education and Experience subsections, but the rule says prefer a few substantive sections over many thin ones. I'll combine into Requirements with sub-lists. -

  Qualifications

  for the specific skills listed under Experience Requirements (Technical Skills, Data Governance Leadership, Leadership, Communication). Or maybe "Skills" heading. The example includes "Skills". I'll use "Qualifications" or "Skills". The posting says "In addition, the successful candidate will have demonstrated the following:" then lists Technical Skills, Data Governance Leadership, Leadership, Communication. I'll make a Qualifications section with a list. -

  Benefits

  with the listed benefits. -

  Pay

  with the pay range. - Maybe a

  Additional Information

  for travel, visa, relocation, direct reports. But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states pay range and benefits, so include them. Schedule not stated (only shift SHIFT1, but not details). Could include a Schedule section if there's info, but only shift mentioned. Might fold into additional info. Also, the company description at the beginning is boilerplate? It's about Harley-Davidson history. The user says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company history might be considered boilerplate, but it's part of the job posting. However, the rule says "Preserve ALL substantive information". The company description is not directly about the role, but it's part of the posting. I think I should include a brief "About the company" or fold into About the role? The example headings don't include "About the company". The job summary already includes "We are seeking a highly skilled Manager, Data Operations...". The preceding paragraph is company history. I'll include it as a short paragraph before sections, maybe as a

  intro. But the output should be only the HTML fragment. I'll start with a

  for company context, then sections. Let's structure:

  Harley-Davidson Motor Company, founded in 1903 in Milwaukee, Wisconsin, continues to define motorcycle culture from its corporate campus which includes a 4.8-acre public park.

  About the role

  We are seeking a highly skilled Manager, Data Operations to lead and manage our data operations team. In this critical role, you will ensure our data systems are efficient, reliable, and secure. You will oversee the design, development, and management of the organization’s data platform infrastructure, along with the development and enforcement of data governance strategies and policies to ensure data accuracy, security, and appropriate usage.

  Responsibilities

  • Data Operations Management: Manage the day-to-day activities of the data operations team, ensuring data availability, reliability, and security to support data integration, storage, processing, and analytics.
  • Data Platform Infrastructure: Oversee the architecture, development, and maintenance of the data platform infrastructure, ensuring high availability, performance, and scalability.
  • Data Governance: Develop, implement, and enforce data governance frameworks, policies, and standards, including data cataloging, lineage, quality, and stewardship processes.
  • Stakeholder Collaboration: Partner with analysts, data governance leads, and business stakeholders to align data platform capabilities with organizational goals and to support reporting, analytics, and machine learning initiatives.
  • Leadership in Data Governance Council: Act as a key leader within the data governance council to ensure cross-functional alignment and effective data stewardship across the organization.
  • Team Leadership & Development: Lead, mentor, and develop a team of data operations professionals, fostering a culture of excellence, collaboration, and continuous improvement.
  • Training & Development: Provide training and support to team members to enhance their skills and ensure high performance.
  • Project Management: Oversee data platform-related projects, ensuring timely delivery within scope and budget, while managing risk and addressing any issues.
  • Performance Reporting: Generate and present regular reports on data platform performance, issues, and improvements to senior management.
  • Tool Evaluation & Implementation: Evaluate, select, and implement data tools and platforms that align with the organization's data strategy.
  • Microsoft Azure: Apply knowledge of Microsoft Azure including Fabric to enhance the data platform infrastructure and optimize data processes where applicable.

  Requirements

  Education

  • Bachelor’s degree in Engineering, Computer Science, or a related technical discipline (required).

  Experience

  • Minimum 8+ years of experience in data operations, data governance, or data engineering, with at least 5 years in a management role.

  Qualifications

  • Technical Skills: Strong expertise in data infrastructure, data governance, ETL/ELT processes, and database management. Familiarity with Microsoft Fabric is desired.
  • Data Governance Leadership: Extensive experience in development and oversight of Data Governance practices across the entire organization, with a track record of building a highly functional Data Governance Council.
  • Leadership: Demonstrated ability to lead, mentor, and develop a high-performing team, and to foster a culture of continuous improvement.
  • Communication: Strong communication skills, with the ability to work effectively across technical and non-technical stakeholders.

  Benefits

  • Annual bonus programs
  • Health insurance benefits
  • 401k program
  • Onsite fitness centers and employee stores
  • Employee discounts on products and accessories
  • Additional inclusive compensation package offerings

  Pay

  Pay range: $119,000 - $178,100 (national average; actual pay dependent on geographic location and level of experience).

  Additional Information

  • Location: Juneau, AK (Onsite)
  • Full-time, Shift 1
  • Direct reports: Yes
  • Travel required: 0–10%
  • Visa sponsorship: Not eligible
  • Relocation: Eligible for domestic relocation assistance (within posted country)
  • Applicants must be currently authorized to work in the United States.
  But note: The rules say "Do NOT repeat the job title as a heading (the page already shows it)". I didn't. Also "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." I dropped the Auto req ID. Could include in Additional Information as a small note, but not necessary. Also, the rule: "use

  for section headings". I used

  for Education and Experience subheadings. That might be okay, but the rule only mentions

  for section headings. It doesn't forbid

  . But to be safe, I could make them

  as well? But they are subsections. The example headings are all

  . I'll keep

  for subsections, but maybe better to use

  for all major sections and use within list items for subheadings. Actually, the Requirements section could have two lists without subheadings, just list items with labels. I'll adjust: In Requirements, I'll have a single list with two items: "Education: Bachelor’s degree..." and "Experience: Minimum 8+ years...". That avoids extra headings. Similarly, Qualifications list already has bold labels. Let's revise:

  Requirements

  • Education: Bachelor’s degree in Engineering, Computer Science, or a related technical discipline (required).
  • Experience: Minimum 8+ years of experience in data operations, data governance, or data engineering, with at least 5 years in a