Product Owner I
for each heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove contact line? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact line "To apply: Send email resume to esgrecruiting@terex.com. Please refer to job #14259" is application instructions, so remove. Also "If you are interested in an open position but feel you may not meet all the listed qualifications, we still encourage you to apply." That's also application encouragement, maybe remove? It's not strictly instruction but could be considered boilerplate; but it's not EEO. Might keep? Safer to remove as it's encouraging application. The "About Terex:" section is company description; could be considered "About the role"? Actually "About the role" is typical heading for role description. The company description could go under "About the role" or maybe separate "About the company". But we only have allowed headings list; we could put company info under "About the role" as it's about the role? Might be okay. However we need to preserve all substantive information. The company description is substantive; we should include it somewhere. Could put under a heading "About the role" but that might be misleading. There's no heading for "About the company". The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when appropriate. It doesn't say we cannot add other headings, but likely they expect only those. However we could incorporate company description under "About the role" as a paragraph.
We need to extract duties, requirements, qualifications, skills, benefits, pay, schedule.
From posting:
Duties: list of duties (multiple sentences). We'll put under Responsibilities
with - each duty.
Requirements: The "Requirements:" section includes: Position requires a Bachelor’s degree (or foreign equivalent) in Computer Science or related field and three (3) years of experience in the job offered or in a Product Owner I-related occupation. Then list of demonstrable experience items. Those are requirements/qualifications/skills. We need to separate into Requirements, Qualifications, Skills maybe. The posting lumps them. We need to decide how to split. Could treat "Requirements" as the degree and years experience. "Qualifications" as the demonstrable experience items? Or "Skills" as the specific tools/experience. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But we have separate headings allowed. We could put degree+years under "Requirements", and the list of demonstrable experience under "Qualifications". Skills could be maybe the tools (SQL, JIRA, Confluence, Python, JavaScript, APIs, ETL/ELT, BigQuery, Snowflake, Databricks, Tableau, Power BI, Looker Studio, MS Visio, Figma, LLMs, GenAI). Could be separate but might be thin. Better to combine Qualifications and Skills into one section? But we need to follow headings only when posting has real specific content. The posting does not explicitly separate qualifications vs skills; it's all under "Requirements:" with bullet-like items. So we could create a single section "Requirements" containing both degree/experience and the demonstrable experience items. Or we could have "Requirements" for degree+years, and "Qualifications" for the demonstrable experience items. That seems reasonable.
Benefits: At the end: "The Company offers competitive salaries, advancement opportunities, and a full range of benefits, including paid vacation, 401(k), medical, dental, and vision." That's benefits info. Also maybe "competitive salaries" is pay info. Pay: we have mention of competitive salaries but no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (paid vacation, 401(k), medical, dental, vision). It also states competitive salaries (pay). So we can include Benefits section with those details. Pay section: we have "competitive salaries" but that's vague; is that considered specific content? It says "competitive salaries" - that's a statement about pay but not a specific number or range. The instruction: 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. "competitive salaries" is somewhat vague but it's a statement about pay. Is that considered filler? It's not a specific number, but it's still stating that salaries are competitive. Might be considered vague but not placeholder like "commensurate with experience". I'd lean to include Pay section with that statement, as it's actual content about pay. However the instruction says prefer few substantive sections over many thin ones. Pay section would be thin (just one line). Could combine Pay and Benefits into one section? But we have separate headings allowed. Could we put pay info inside Benefits section? The Benefits section already mentions benefits; we could add "competitive salaries" there. That would avoid a thin Pay section. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine Pay and Benefits into Benefits section, or maybe have Benefits only and mention competitive salaries there. Since Benefits heading is allowed, we can include both benefits and pay info under Benefits. That seems fine.
Schedule: The posting mentions "Domestic (U.S.) travel is required up to 25% to customer on-sites. 100% telecommuting permitted." That's schedule/telecommuting/travel. That's schedule info. So we can create Schedule section with that.
Now we need to ensure we don't repeat job title. No headings for job title.
We must not include Job ID etc. So we strip lines like "Job Code: #14259", "Job Location:", "Job Type:", etc. Also remove "CONTACT:" line and application instructions. Also remove "About Terex:"? We'll incorporate under About the role maybe.
We need to preserve all substantive information: duties, requirements (degree+years), demonstrable experience items, benefits, pay (competitive salaries), schedule (travel up to 25%, 100% telecommuting). Also maybe mention "Domestic (U.S.) travel is required up to 25% to customer on-sites. 100% telecommuting permitted." That's schedule.
Now we need to format.
We'll output:
About the role
... company description and maybe role overview?
But we have a duties section separate. About the role could contain a brief summary: "Product Owner I at The Heil Co. (dba 3rd Eye) responsible for..." but we already have duties. Could put company description there.
Let's craft:
About the role: include employer name and location? The location is substantive? It's location info. Could be included. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a short or drop it. Location is minor metadata but could be included in a short p. We'll include location in About the role paragraph.
Thus About the role paragraph: "Employer: The Heil Co. (dba 3rd Eye). Position: Product Owner I. Location: 201 W Main Street, Suite 300, Chattanooga, TN 37408. Full-time role."
But we should not repeat job title as heading, but we can mention it in paragraph.
Now Responsibilities: list duties.
We need to extract each duty sentence from the "Duties:" block.
Duties block:
- Analyze and translate business requirements for BI and data driven products into user stories, epics, and acceptance criteria.
- Document detailed Product Requirements Document (PRDs) and collaborate with cross-functional teams (Data, AI and BI Engineering, QA, DevOps, Finance, Customer and Product support) throughout product development lifecycle (PDLC) in an Agile environment.
- Manage and prioritize the product backlog by incorporating stakeholder feedback into structured product roadmap and participate in Agile/SCRUM ceremonies including sprint planning, backlog refinement, daily stand-ups, and retrospectives.
- Conduct quantitative and qualitative data analysis using SQL and cloud-based data platforms to assess product performance, identify gaps, and establish feedback loops with business stakeholders.
- Partner with engineering team to support data integration processes, including API and ETL/ELT workflows for ingesting and transforming data using data modelling techniques from multiple source systems.
- Perform gap analysis and validate data flows across data pipelines, data lakes, and data warehouse environments to ensure data accuracy and consistency.
- Collaborate with engineering team to design and deliver business intelligence reports, dashboards or visualizations to business stakeholders, highlighting key product performance and actionable insights.
- Coordinate user acceptance testing (UAT) to validate that systems meet defined business and technical requirements and define objective and key results (OKRs) aligned to KPIs and strategic priorities.
- Domestic (U.S.) travel is required up to 25% to customer on-sites.
- 100% telecommuting permitted.
Note: The last two are actually schedule/travel but we will move them to Schedule section. So we should not include them in Responsibilities. So Responsibilities will be first 8 bullet points.
Now Requirements: degree + years experience.
We'll put:
Position requires a Bachelor’s degree (or foreign equivalent) in Computer Science or related field and three (3) years of experience in the job offered or in a Product Owner I‑related occupation.
Now Qualifications: list of demonstrable experience items.
We need to capture each bullet from the "Requirements:" after the degree line.
List:
- Demonstrable experience defining, maintaining, and prioritizing product roadmaps for Business Intelligence (BI), data driven products and participating in Agile and SCRUM ceremonies such as sprint planning, backlog refinement, daily stand-ups, and retrospectives.
- Demonstrable experience authoring Product Requirement Documents (PRDs) and translating business requirements into technical user stories, epics, acceptance criteria, and definition of done across Product Development Lifecycle (PDLC), using tools including JIRA and Confluence.
- Demonstrable experience collaborating with cross-functional teams including DevOps, Data / BI / AI engineering, QA, finance, and business stakeholders to support strategic planning, backlog prioritization, roadmap tradeoffs, UAT (User Acceptance testing), and definition of KPIs and OKRs.
- Demonstrable experience reviewing and understanding technical designs and code artifacts including Python and JavaScript for the purpose of product design validation and effective collaboration with engineering.
- Demonstrable experience defining requirements and validating solutions related to data integration and transformation processes, including APIs, data modeling, ETL/ELT batch and stream processing across cloud-based data lakes or data warehouses platforms including BigQuery, Snowflake, or Databricks.
- Demonstrable experience supporting the development of reports and dashboards in collaboration with analytics or BI teams using visualization tools including Tableau, Power BI, or Google Looker Studio, and creating dashboard and report mockups or wireframes using tools such as MS Visio and Figma to facilitate stakeholder and technical
Responsibilities
with- each duty.
Requirements: The "Requirements:" section includes: Position requires a Bachelor’s degree (or foreign equivalent) in Computer Science or related field and three (3) years of experience in the job offered or in a Product Owner I-related occupation. Then list of demonstrable experience items. Those are requirements/qualifications/skills. We need to separate into Requirements, Qualifications, Skills maybe. The posting lumps them. We need to decide how to split. Could treat "Requirements" as the degree and years experience. "Qualifications" as the demonstrable experience items? Or "Skills" as the specific tools/experience. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But we have separate headings allowed. We could put degree+years under "Requirements", and the list of demonstrable experience under "Qualifications". Skills could be maybe the tools (SQL, JIRA, Confluence, Python, JavaScript, APIs, ETL/ELT, BigQuery, Snowflake, Databricks, Tableau, Power BI, Looker Studio, MS Visio, Figma, LLMs, GenAI). Could be separate but might be thin. Better to combine Qualifications and Skills into one section? But we need to follow headings only when posting has real specific content. The posting does not explicitly separate qualifications vs skills; it's all under "Requirements:" with bullet-like items. So we could create a single section "Requirements" containing both degree/experience and the demonstrable experience items. Or we could have "Requirements" for degree+years, and "Qualifications" for the demonstrable experience items. That seems reasonable.
Benefits: At the end: "The Company offers competitive salaries, advancement opportunities, and a full range of benefits, including paid vacation, 401(k), medical, dental, and vision." That's benefits info. Also maybe "competitive salaries" is pay info. Pay: we have mention of competitive salaries but no specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (paid vacation, 401(k), medical, dental, vision). It also states competitive salaries (pay). So we can include Benefits section with those details. Pay section: we have "competitive salaries" but that's vague; is that considered specific content? It says "competitive salaries" - that's a statement about pay but not a specific number or range. The instruction: 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. "competitive salaries" is somewhat vague but it's a statement about pay. Is that considered filler? It's not a specific number, but it's still stating that salaries are competitive. Might be considered vague but not placeholder like "commensurate with experience". I'd lean to include Pay section with that statement, as it's actual content about pay. However the instruction says prefer few substantive sections over many thin ones. Pay section would be thin (just one line). Could combine Pay and Benefits into one section? But we have separate headings allowed. Could we put pay info inside Benefits section? The Benefits section already mentions benefits; we could add "competitive salaries" there. That would avoid a thin Pay section. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine Pay and Benefits into Benefits section, or maybe have Benefits only and mention competitive salaries there. Since Benefits heading is allowed, we can include both benefits and pay info under Benefits. That seems fine.
Schedule: The posting mentions "Domestic (U.S.) travel is required up to 25% to customer on-sites. 100% telecommuting permitted." That's schedule/telecommuting/travel. That's schedule info. So we can create Schedule section with that.
Now we need to ensure we don't repeat job title. No headings for job title.
We must not include Job ID etc. So we strip lines like "Job Code: #14259", "Job Location:", "Job Type:", etc. Also remove "CONTACT:" line and application instructions. Also remove "About Terex:"? We'll incorporate under About the role maybe.
We need to preserve all substantive information: duties, requirements (degree+years), demonstrable experience items, benefits, pay (competitive salaries), schedule (travel up to 25%, 100% telecommuting). Also maybe mention "Domestic (U.S.) travel is required up to 25% to customer on-sites. 100% telecommuting permitted." That's schedule.
Now we need to format.
We'll output:
About the role
... company description and maybe role overview?
But we have a duties section separate. About the role could contain a brief summary: "Product Owner I at The Heil Co. (dba 3rd Eye) responsible for..." but we already have duties. Could put company description there. Let's craft: About the role: include employer name and location? The location is substantive? It's location info. Could be included. The instruction: do not put Job ID/requisition numbers as headings — fold minor metadata into a shortor drop it. Location is minor metadata but could be included in a short p. We'll include location in About the role paragraph. Thus About the role paragraph: "Employer: The Heil Co. (dba 3rd Eye). Position: Product Owner I. Location: 201 W Main Street, Suite 300, Chattanooga, TN 37408. Full-time role." But we should not repeat job title as heading, but we can mention it in paragraph. Now Responsibilities: list duties. We need to extract each duty sentence from the "Duties:" block. Duties block: - Analyze and translate business requirements for BI and data driven products into user stories, epics, and acceptance criteria. - Document detailed Product Requirements Document (PRDs) and collaborate with cross-functional teams (Data, AI and BI Engineering, QA, DevOps, Finance, Customer and Product support) throughout product development lifecycle (PDLC) in an Agile environment. - Manage and prioritize the product backlog by incorporating stakeholder feedback into structured product roadmap and participate in Agile/SCRUM ceremonies including sprint planning, backlog refinement, daily stand-ups, and retrospectives. - Conduct quantitative and qualitative data analysis using SQL and cloud-based data platforms to assess product performance, identify gaps, and establish feedback loops with business stakeholders. - Partner with engineering team to support data integration processes, including API and ETL/ELT workflows for ingesting and transforming data using data modelling techniques from multiple source systems. - Perform gap analysis and validate data flows across data pipelines, data lakes, and data warehouse environments to ensure data accuracy and consistency. - Collaborate with engineering team to design and deliver business intelligence reports, dashboards or visualizations to business stakeholders, highlighting key product performance and actionable insights. - Coordinate user acceptance testing (UAT) to validate that systems meet defined business and technical requirements and define objective and key results (OKRs) aligned to KPIs and strategic priorities. - Domestic (U.S.) travel is required up to 25% to customer on-sites. - 100% telecommuting permitted. Note: The last two are actually schedule/travel but we will move them to Schedule section. So we should not include them in Responsibilities. So Responsibilities will be first 8 bullet points. Now Requirements: degree + years experience. We'll put:
Position requires a Bachelor’s degree (or foreign equivalent) in Computer Science or related field and three (3) years of experience in the job offered or in a Product Owner I‑related occupation.
Now Qualifications: list of demonstrable experience items. We need to capture each bullet from the "Requirements:" after the degree line. List: - Demonstrable experience defining, maintaining, and prioritizing product roadmaps for Business Intelligence (BI), data driven products and participating in Agile and SCRUM ceremonies such as sprint planning, backlog refinement, daily stand-ups, and retrospectives. - Demonstrable experience authoring Product Requirement Documents (PRDs) and translating business requirements into technical user stories, epics, acceptance criteria, and definition of done across Product Development Lifecycle (PDLC), using tools including JIRA and Confluence. - Demonstrable experience collaborating with cross-functional teams including DevOps, Data / BI / AI engineering, QA, finance, and business stakeholders to support strategic planning, backlog prioritization, roadmap tradeoffs, UAT (User Acceptance testing), and definition of KPIs and OKRs. - Demonstrable experience reviewing and understanding technical designs and code artifacts including Python and JavaScript for the purpose of product design validation and effective collaboration with engineering. - Demonstrable experience defining requirements and validating solutions related to data integration and transformation processes, including APIs, data modeling, ETL/ELT batch and stream processing across cloud-based data lakes or data warehouses platforms including BigQuery, Snowflake, or Databricks. - Demonstrable experience supporting the development of reports and dashboards in collaboration with analytics or BI teams using visualization tools including Tableau, Power BI, or Google Looker Studio, and creating dashboard and report mockups or wireframes using tools such as MS Visio and Figma to facilitate stakeholder and technical