Product Owner I

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the job description. Company description: "Company Farm Family Farm Family specializes in farm and ranch protection..." That's about the company. Could be "About the role"? Actually "About the role" is for description of role. Could include company overview maybe under "About the role". But we need to decide. We have sections: Job Description (description of role), Essential Functions (list of duties), Required Qualifications, Preferred Qualifications, Occupational Requirements, Benefits And Compensation, Core Values. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine: - About the role: could include company overview and brief description of role (Job Description paragraph). Use

  . - Responsibilities: list of essential functions (Essential Functions). Use

  • . - Requirements: maybe Required Qualifications (including education, experience). Use
    • . - Qualifications: maybe Preferred Qualifications? Or we could combine Required and Preferred under Qualifications? But we have both Requirements and Qualifications headings allowed. Could put Required Qualifications under Requirements, Preferred Qualifications under Qualifications. - Skills: maybe list of skills from Required/Preferred (like facilitation, communication, etc.) Could extract skills list. But we might avoid thin sections. Could combine skills into Qualifications or Requirements. However we have separate Skills heading allowed; we could include a list of skills (like communication, facilitation, decision-making, analytical, etc.) but we need to ensure we have substantive content. - Benefits: Benefits And Compensation section. Use
      • for benefits. - Pay: we have no specific pay info (just "competitive compensation package, performance-based incentives"). That's vague but maybe we can include under Benefits? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive compensation package, performance-based incentives". That's about compensation but not specific numbers. Is that considered substantive? It says "competitive compensation package, performance-based incentives". That's not placeholder like "commensurate with experience". It's somewhat vague but still mentions compensation. Could we include a Pay section with that statement? The rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation package, so we can include Pay section with that statement. However we also have Benefits section for benefits like health, dental, vision, 401(k), PTO, professional development. So we can separate. - Schedule: The posting mentions "The position requires physical presence in company office on full-time basis." That's schedule info (full-time, on-site). So we can include Schedule section with that. Now we need to avoid boilerplate: "Please Note Applicants must be legally authorized to work in the United States..." That's legal/EEO? It's about work authorization; could be considered boilerplate but it's substantive? It's a requirement. Might be considered part of Requirements? Could include under Requirements as a bullet. However it's about legal authorization; it's not EEO but it's a requirement. We'll keep. Also "At this time, we are not able to sponsor or assume sponsorship of employment visas." That's also a requirement. Also disability accommodation contact: that's EEO/boilerplate; we should remove. Also "Core Values" section: we could include under About the role or maybe as a separate section? Not in allowed headings. Could incorporate into About the role as a paragraph. We must not repeat job title as heading. The job title is "Product Owner II". Not to be used as heading. We must not include Job ID/requisition numbers. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft sections:

        About the role

        Farm Family specializes in farm and ranch protection with a wide range of products including flexible farm packages, business owner policies, commercial package, workers compensation, commercial auto and select personal auto coverage. Farm Family is a leader in serving the Northeast and Mid-Atlantic markets and is pursuing growth across the U.S. The Farm Family entities are wholly-owned subsidiaries of Clearbrook Group Holdings Inc. As a Product Owner II, you will lead the agile scrum team(s) and ensure product planning and effective prioritization, managing the product throughout its lifecycle, gathering and prioritizing product and customer requirements, and working closely with agile teams to deliver value. You will bridge the gap between product strategy and development, maintain the health and management of the product backlog, organize sprint activities, and answer questions from developers as needed. You will also work with support partners to ensure revenue, customer satisfaction goals, and other outcomes are met in alignment with the product’s overall strategy and goals.

        That covers company overview and role description.

        Responsibilities

        • Break down overall product strategy and roadmap into program increment (quarterly) and sprint level goals and priorities (in partnership with the Product Manager).
        • Connect with customers and internal stakeholders to inform the product strategy and roadmap, including relevant competitive knowledge and industry trends.
        • Maintain the content and integrity of the product team’s backlog of stories, enablers, and defects.
        • Ensure stories are well informed and represent the intent of agile release train (ART) level features.
        • Prioritize the sequence of backlog items and communicate that sequence to the product team during backlog refinement and iteration planning.
        • Model servant leadership to the product team and incorporate feedback and suggestions made during team retrospectives into future delivery activities.
        • Ensure working product demos are presented to key stakeholders for awareness, transparency, and input.
        • Collaborate with other leaders across the ART to ensure transparency of work, dependencies are understood and properly sequenced, working methods are consistent across the teams, and priorities are aligned.
        • Evaluate individual agile team members for effectiveness and contributions, ensuring teams are high performing; make recommendations to remove or add team members as needed.

        Requirements

        • Bachelor's degree in information technology, computer science, or relevant field.
        • Two to four years of experience.
        • At least three years of agile Product Owner experience in scrum and scaled agile environments.
        • Experience delivering software products using agile principles, including planning and estimating with a continuous improvement mindset.
        • Proven track record of bringing successful products to market on time, incorporating a variety of development and delivery strategies (third party, insourcing, outsourcing).
        • Proven success in leading, coaching, and motivating cross-functional empowered teams.
        • Experience with market research, competitive analysis, and technology trend analysis.
        • Ability to assess the impact of new product initiatives on the delivery team environment.
        • Demonstrated understanding and empathy for customer needs and pain points, amplifying the voice of the customer throughout product development and delivery.
        • Facilitation and collaboration skills, including ability to facilitate decision-making and broker agreements among diverse, differing, and/or conflicting perspectives/priorities.
        • Excellent verbal, written, and interpersonal communication skills, particularly with establishing and advocating for both customer and delivery team points of view.
        • Experience communicating and presenting complex information to multiple levels of the organization, translating data into understandable, actionable information and recommendations.
        • Ability to make timely and independent decisions while working in a fast-paced and results-driven environment, making adjustments, and course corrections in close partnership with delivery teams.
        • Applicants must be legally authorized to work in the United States; sponsorship of employment visas is not available at this time.

        Qualifications

        • At least six years of experience in one or more of the following: product management, product development, strategic planning, process management, change delivery, or as an agile product owner.
        • Ability to meet deadlines, achieve goals, manage risk, solve problems, and work under pressure in a dynamic and complex environment.
        • Expertise in navigating matrixed organizations and teams with proven success in leveraging the right people and resources at the right time for consistent and dependable delivery of optimal value to the customer and the business.
        • Knowledge and understanding of product management in the regulated financial services industry.
        • Ability to evaluate risks and the impact of decisions on the product line, generating creative alternatives and understanding trade-offs.
        • Excellent analytical skills and orientation in making data-driven technical decisions.
        • One or more of the following agile certifications: Certified Scrum Product Owner (CSPO), Agile Certified Practitioner (PMI-ACP), Certified Agile Product Manager (CAL-PM), SAFe Product Owner/Product Manager (SAFe POPM), or Certified LeSS Practitioner (CLP).
        • Ability to train and coach all levels of the organization.
        • Experience with software development lifecycle management and tooling (Jira Align or Azure DevOps knowledge a plus).
        We could also include Skills section but we already have many skill-like items in Requirements and Qualifications. To avoid thin sections, maybe we can omit Skills heading unless we have distinct skill list not covered. The instructions: Prefer a few substantive sections over many thin ones. We already have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Could be okay. But we might combine some. We still need Benefits, Pay, Schedule. Benefits: we have benefits description.

        Benefits

        • Competitive compensation package
        • Performance-based incentives
        • Comprehensive benefits program—including health, dental, vision
        • 401(k) with company match
        • Paid time off
        • Professional development opportunities
        Pay: we have competitive compensation package and performance-based incentives already listed; but we could still have Pay section with that statement. However we already listed competitive compensation package under Benefits; maybe we should not duplicate. Better to put Pay section with details about compensation (maybe just "competitive compensation package, performance-based incentives") and Benefits section with health, dental, vision, 401(k), PTO, professional development. But we already used competitive compensation package in Benefits; we can move it to Pay and keep Benefits for other benefits. Let's adjust: Pay section:

        Competitive compensation package with performance-based incentives.

        Benefits section: list health, dental, vision, 401(k) with company match, paid time off, professional development opportunities. Schedule: full-time, on-site presence.

        Schedule

        The position requires physical presence in the company office on a full-time basis.

        Now we need to ensure we didn't include any boilerplate like Core Values. We could incorporate Core Values into About the role as a sentence. Add at end of About the role paragraph: "Clearbrook’s Core Values are Integr