Jobs · OTHR · New York

Product Owner (Advanced Analytics) - Hybrid

Mindex · Rochester, NY · 1 mo ago
HybridOTHR$90k–$140k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. The posting includes: description (role), responsibilities (What You'll Accomplish), requirements (Requirements), maybe qualifications (Education & Experience, Licenses & Certifications), benefits (Benefits), Pay (Compensation), maybe Schedule (not present). Also location info (open to occasional in-person, within 35 miles of Rochester). That could be part of About the role or maybe a separate section like Location? But we only have allowed headings list; we can put location info under About the role or maybe under Responsibilities? Probably include in About the role. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to preserve all substantive info. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to decide sections: About the role (intro paragraph), Responsibilities (What You'll Accomplish bullet list), Requirements (maybe combine Requirements and Education & Experience and Licenses & Certifications). Could have Qualifications section for education/experience/licenses. Benefits section. Pay section. Possibly Skills? Not explicit separate; but we could include skills within Requirements. But we can have a Skills section if we have list of skills. The posting includes many skill-like items: communication, organizational, prioritization, ability to assess users, define data quality, define success criteria, work with customers, judgment ethical AI, identify AI opportunities. Those could be under Requirements or Skills. We'll put them under Requirements as bullet list. Qualifications: Education & Experience, Licenses & Certifications. Benefits: list. Pay: compensation range. Schedule: not present, so omit. We must not create sections with filler like "commensurate with experience". Not present. We need to ensure we don't invent or summarize away detail. Keep all details. Let's extract content. Intro paragraph: "As a Product Owner, you'll be directly aligned with one of our agile engineering teams, articulating and prioritizing customer challenges and opportunities for the team to solve in collaboration with the User Experience team. The ideal candidate will have excellent business acumen, experience in SaaS product management, and a passion for working in K-12 education technology, specifically in driving efficiencies in back-office systems and processes for K-12 school districts. In this role, data and analytics are the product, not a feature of one. As the Product Owner for our Advanced Analytics offering, you will work with school districts and education service agencies to build and maintain a platform that enables them to create their own data products while also developing ours. The foundation of this offering includes our data lakehouse, reports, dashboards, and the advanced capabilities that sit on top of the data. You will also partner with other Product Owners across the organization to support their analytics and reporting needs. This is a great opportunity for a highly organized, data-driven, and customer-focused individual with experience working with data platforms at scale. We welcome candidates from a variety of locations; however, all candidates should be open to occasional in-person participation for business meetings, team events, or collaboration opportunities. Candidates located within approximately 35 miles of Rochester, NY may be asked to work from the office more frequently based on business or team needs." That's About the role. Responsibilities: "What You'll Accomplish" bullet list: - Works with the Product Director to translate high-level company vision and strategy into actionable product plans. - Partners with Customers to identify and prioritize needs, documents them as epics with requirements and acceptance criteria, and works with Engineering and UX to break them into plannable features and stories while serving as the Customer advocate throughout development. - Validates that solutions deliver meaningful impact against Epics and strategic goals, and coordinates with documentation, training, support, and marketing to prepare for release. - Where appropriate, facilitates user acceptance testing and/or feedback demonstrations of work prior to release, collates and assesses feedback, and reshapes team priorities as needed to maximize value for the customer. - Serves as a product SME for service, sales, and marketing, and represents SchoolTool externally at User Groups and Conferences to present features and gather customer feedback. - Actively facilitates and participates in team retrospectives and the continuous improvements of our organizational structure, processes, and tooling to drive greater operational efficiency and value for our customers. - Applies an AI-first mindset by effectively leveraging AI-assisted tools and technologies to enhance productivity, accelerate problem-solving, improve quality, automate routine tasks, and drive innovation in the delivery of solutions and services. We'll put each as

  • . Requirements: list of bullet points from "Strong written and verbal communication skills..." through "Identifies opportunities to use AI to streamline workflows, reduce manual effort, improve efficiency, and increase business value." Let's extract each line: - Strong written and verbal communication skills over complex topics with both internal technical team members and non-technical stakeholders - Strong organizational / prioritization skills with the ability to prioritize incoming requests from multiple channels, manage concurrent projects, course correct for changing priorities via Support and APM tools - Ability to assess how different users consume and act on data and to define solutions appropriate to the user's context (e.g., compliance reporting vs. operational decision-making vs. self-service exploration). - Ability to define data quality, timeliness, and accuracy as product requirements, understanding that these are customer-facing decisions, not just engineering concerns. - Ability to define measurable success criteria for analytics features beyond delivery, including adoption, accuracy, and impact on user decision-making or operational efficiency. - Ability to work with customers to understand their data and reporting needs at the outcome level, focusing on what decisions they need to make rather than taking requests at face value. - Demonstrates sound judgment in the ethical, secure, and compliant use of AI technologies while protecting confidential, customer, and company information. - Identifies opportunities to use AI to streamline workflows, reduce manual effort, improve efficiency, and increase business value. We'll put as
    • . Qualifications: Education & Experience and Licenses & Certifications. Education & Experience: - BA in Information Technology, Computer Science or related technical fields preferred, or an equivalent combination of education and experience. - 4+ years of experience as a Product Owner, owning a data platform strategy, including how data is structured, accessed, and used to drive decisions through reporting and analytics solutions (canned reports, dashboards, self-service tools, alerts, data exports) and to drive more advanced product features is strongly preferred. - 4+ years of experience in PK-12, strong familiarity with PK-12 data domains, ideally Ed-Fi (SIS, Assessment, SPED, MTSS, Instruction, HR, and Finance), and how they are used to drive decisions for school districts is preferred. Licenses & Certifications: - CSPO (Certified Scrum Product Owner) or equivalent certification and/or experience a plus. We'll put as
      • under Qualifications. Benefits: list: - Flexible Time Off - Medical, Dental, and Vision Insurance - 401(k) with Company Match - Company-Paid Life and Disability Insurance - Professional Development Opportunities We'll put as
        • . Pay: compensation range: "Compensation $90,000 - $140,000". We'll put as

          maybe under Pay heading. Schedule: not present, omit. We must not include any filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown. We'll structure:

          About the role

          ...intro paragraph...

          Responsibilities

          • ...
          • ...

          Requirements

          • ...
          • ...

          Qualifications

          • ...
          • ...

          Benefits

          • ...
          • ...

          Pay

          Compensation $90,000 - $140,000

          Make sure to preserve all details exactly. Ensure no extra spaces? It's fine. Check for any duplicated lines: none. Check for any boilerplate: none. Check for any mention of "Physical Requirements/Conditions:" etc. That's at end: "Physical Requirements/Conditions: Prolonged periods sitting at a desk and working on a computerNo heavy lifting is expected. Exertion of up to 10 lbs". This is substantive info about physical requirements. Should we include? The allowed headings don't include Physical Requirements, but we could put under About the role or maybe a separate section? The instruction: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. But we should prefer those headings. However, we could include a section like "Physical Requirements" if we want, but they said prefer a few substantive sections over many thin ones. Physical Requirements is a small detail; we could fold into About the role as a paragraph. That seems reasonable: add a sentence about physical requirements at end of About the role. Thus About the role paragraph will include the physical requirements sentence. Let's incorporate: after location sentence, add: "Physical requirements include prolonged periods sitting at a desk and working on a computer; no heavy lifting is expected, with exertion of up to 10 lbs." Make sure to keep original wording: "Physical Requirements/Conditions: Prolonged periods sitting at a desk and working on a computerNo heavy lifting is expected. Exertion of up to 10 lbs". There's missing space after computer. We'll format nicely. We'll preserve meaning. Now produce HTML. Check for any other info: "Additional Information Applicants must be authorized to work for any employer in the United States. Mindex is unable to sponsor employment visas at this time." That's also substantive. Could fold into About the role or maybe a separate section like "Eligibility". But we can add to About the role as a sentence. Thus About the role will be long but okay. Let's craft About the role paragraph: "As a Product Owner, you'll be directly aligned with one of our agile engineering teams, articulating and prioritizing customer challenges and opportunities for the team to solve in collaboration with the User Experience team. The ideal candidate will have excellent business acumen, experience in SaaS product management, and a passion for working in K-12 education technology, specifically in driving efficiencies in back-office systems and processes for K-12 school districts. In this role, data and analytics are the product, not a feature of one. As the Product Owner for our Advanced Analytics offering, you will work with school districts and education service agencies to build and maintain a platform that enables them to create their own data products while also developing ours. The foundation of this offering includes our data lakehouse, reports, dashboards, and the advanced capabilities that sit on top of the data. You will also partner with other Product Owners across the organization to support their analytics and reporting needs. This is a great opportunity for a highly organized, data-driven, and customer-focused individual with experience working with data platforms at scale. We welcome candidates from a variety of locations; however, all candidates should be open to occasional in-person participation for business meetings, team events, or collaboration opportunities. Candidates located within approximately 35 miles of Rochester, NY may be asked to work from the office more frequently based on business or team needs. Physical requirements include prolonged periods sitting at a desk and working on a computer; no heavy lifting is expected, with exertion of up to 10 lbs. Applicants must be authorized to work for any employer in the United States. Mindex is unable to sponsor employment visas at this time." That covers all. Now produce HTML. Be careful to escape any

Similar jobs