Senior Operations Project and Program Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - Who We Are: description of company. Could be "About the role"? Actually "Who We Are" is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and maybe company overview. But we need to preserve all substantive info. We'll include "About the role" containing the "Who We Are" and "What We Stand For and Where You'll Come In" maybe. But we need to separate responsibilities, requirements, qualifications, skills, benefits, pay, schedule. Let's identify responsibilities: bullet points under "How You'll Make An Impact". That's a list of duties. Requirements/Qualifications/Skills: The "We're Excited About You Because" list includes qualifications: BS degree, 7+ years experience, knowledge of Lean Six Sigma, analytics skills, proficiency in data tools, communication skills, problem solving, adaptable, love dogs. Those could be qualifications/requirements/skills. We need to decide where to put them. Could have "Qualifications" and "Skills". But we should not create thin sections; prefer few substantive sections. Could combine qualifications and skills into one "Requirements" section. But we have separate headings allowed; we can include both if they have content. However we must avoid filler. We'll include "Requirements" with the list. Benefits: "A Few Of Our Best Benefits" list includes dog-friendly office, market-competitive compensation and equity packages, comprehensive healthcare, dental, vision, company supported mental health benefits, 12 week paid parental leave, competitive 401k plan with company match, flexible PTO, discounted fresh food for your pup, pet interrupting video calls is a feature. Also maybe office guidelines? Not benefit. So we can include Benefits section. Pay: The posting mentions "Market-competitive compensation and equity packages" but not specific numbers. It says "Market-competitive compensation". That's vague but still mentions compensation. However instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation (market-competitive). It's not specific like "commensurate with experience" but it's still a statement. It's not filler like "commensurate with experience" which is prohibited. The phrase "Market-competitive compensation and equity packages" is substantive. So we can include Pay section with that sentence. Schedule: Office Guidelines: "We are an in-office culture... We ask all team members to be in office 4 - 5 days a week". That's schedule info. So we can include Schedule section. We must not include boilerplate like EEO, Reasonable Accommodations, We're Here to Help, etc. Also remove duplicated lines. We need to preserve all substantive information. So we need to include the company overview, the "What We Stand For and Where You'll Come In" paragraph, the responsibilities list, the qualifications list, benefits list, pay statement, schedule statement. We must not include the "Office Guidelines" as separate heading if we put under Schedule. We'll include schedule details there. We must not include the "Our Belonging Philosophy" etc. That's boilerplate? It's about culture but maybe considered substantive? It's about belonging philosophy. Might be considered part of company culture but could be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The belonging philosophy is not legal boilerplate; it's culture description. Might be considered substantive. However we already have "Who We Are" and "What We Stand For". The belonging philosophy is somewhat similar to culture. Might be considered duplicate or filler? It's not duplicated but it's a separate section about belonging. Could be included under "About the role" or maybe we could add a "Culture" section but not in allowed headings. Since only allowed headings are those listed, we should not add extra headings. So we could incorporate that content into "About the role" or maybe omit if it's considered filler. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine culture into About the role. Thus About the role section will contain: Who We Are, What We Stand For and Where You'll Come In, Our Belonging Philosophy (maybe). We'll keep it concise but preserve all substantive info. Must not invent or summarize away detail. We need to preserve all substantive information; we cannot omit details. That's tricky: we must keep all info, but we can rephrase? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot omit any substantive info. We must keep everything that is substantive. That means we need to include all paragraphs and bullet points. However we can combine them under headings but not lose any info. Thus we need to output all the content, just formatted with headings and lists. We must not include boilerplate like EEO, Reasonable Accommodations, We're Here to Help, etc. Also remove duplicated lines. Let's identify substantive sections: - Who We Are (paragraph) - What We Stand For and Where You'll Come In (paragraphs about One Team, We Execute For Impact, We Are Focused and Work Without Assumption) Actually those are subheadings within that section. They are substantive. - How You'll Make An Impact (list of responsibilities) - We're Excited About You Because (list of qualifications/skills) - Office Guidelines (schedule) - A Few Of Our Best Benefits (benefits) - Our Belonging Philosophy (paragraphs about belonging) - maybe considered substantive. - Also there is a line about "For this role the anticipated hiring base com" cut off; incomplete. Probably ignore as incomplete. We must not include the Equal Employment Opportunity Statement, Reasonable Accommodations, We're Here to Help, etc. We also must not include duplicated lines (like maybe repeated "We are an in-office culture"). Now we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have multiple sections that could map: - About the role: could contain Who We Are, What We Stand For..., Our Belonging Philosophy (maybe). Also maybe the "One Team" etc. - Responsibilities: the "How You'll Make An Impact" list. - Requirements: maybe the "We're Excited About You Because" list (education, experience). Could also be Qualifications. - Skills: maybe the specific skills like analytics, presentation, data tools, communication, problem solving, adaptability, love dogs. But we could split. But we must not create thin sections. If we split into Requirements, Qualifications, Skills each with few items, might be thin. Better to combine into one "Requirements" section that includes education, experience, skills, etc. However the instruction allows multiple headings if they have real specific content. We could have Requirements and Skills both with content. But we need to decide. Let's see the content of "We're Excited About You Because": - BS degree in Management, Supply Chain, or related field, and 7+ years of experience in supply chain, project management, program management, or related roles, with a focus on direct-to-consumer operations. - In-depth knowledge of Lean and Six Sigma methodologies and tools, and proven experience in continuous improvement project management. - Excellent analytics and presentation skills and a proven track record of translating data-driven insight into action and consumer-facing impact. - Proficient in data analysis tools and techniques, such as Microsoft Excel, SQL, etc. - Clear, confident, and persuasive verbal and written communication skills when working with a diverse group of cross-functional stakeholders. - Owner with excellent problem-solving skills, strong attention to detail, and ability to prioritize and manage multiple deliverables across various timelines. - Proactive approach to overcoming operational challenges. - Adaptable and resilient, able to operate autonomously in a dynamic and rapidly evolving business environment. - Love dogs. These are a mix of qualifications, skills, experience. Could be split into Requirements (education + experience) and Skills (the rest). But we can also put all under "Requirements". However the instruction says use headings like Requirements, Qualifications, Skills. It doesn't forbid using only one of them. It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to include. We'll include Requirements and maybe Skills if we want to split. But we must avoid thin sections. If we put all under Requirements, that's fine. Thus we will have:

About the role

containing the company overview, what we stand for, belonging philosophy.

Responsibilities

containing the list of impact items.

Requirements

containing the "We're Excited About You Because" list.

Benefits

containing the benefits list.

Pay

containing the market-competitive compensation statement.

Schedule

containing office guidelines (in-office 4-5 days). We must not include any other headings. Now we need to format lists: Use

• for any list of duties/requirements/benefits. For prose, use

  . Thus About the role will have multiple paragraphs (prose). We'll wrap each paragraph in

  . Responsibilities: each bullet becomes

• inside
  . Requirements: each bullet becomes
  • inside
    . Benefits: each bullet becomes
    • inside
      . Pay: a short

      with the compensation sentence. Schedule: a short

      with the office guideline. Now we need to ensure we preserve all substantive information from those sections. Let's extract the exact text. Who We Are: "The Farmer’s Dog was born from a mission to change the landscape of pet health, providing dogs and their humans with honest, smart, and simple care. We’re starting by radically improving the $90 billion pet food industry, replacing bags of highly-processed pellets with a personalized subscription service that sends complete and balanced, freshly-made dog food directly to customers’ doors. Our ultimate goal is to create innovative, delightful and personalized experiences across all aspects of pet care, and we believe our direct-to-consumer business model, holistic approach to growth, and dynamic culture uniquely position us to shepherd this backwards industry into the future. To date, The Farmer’s Dog has delivered over 1 billion meals nationwide and raised over $150M in funding to help us build a company as healthy as the dogs who are eating those meals. Join us as we continue to develop ways of bringing peace of mind to customers, health to their companions, and much-needed change to the way people feed and care for their pets. #LongLiveDogs" We need to keep the hashtag? It's part of the text. Keep it. What We Stand For and Where You'll Come In: Paragraphs: "As the Senior Operations Strategy and Project Manager, you'll own the highest-priority initiatives on the Ops roadmap and drive them to completion. This is a role for someone who can do both halves of the job well: run complex, cross-functional projects with real discipline, and bring the analytical rigor to decide which projects deserve investment in the first place. You'll partner across Planning, Procurement, Fulfillment, Technical Operations, Commercialization, Nutrition, Innovation, Marketing, and FP&A to define scope, pressure-test feasibility, and hold timelines — including leading new product launches through Ops. You'll take the foundational understanding we