Business Operations Manager - Data & Analytics
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate like EEO, equal opportunity, navigation, legal, scam warning, duplicated lines, application instructions. Also remove "HERE is an equal opportunity employer..." etc. Also remove "Who are we?" maybe not needed unless it's substantive? It's about company description; could be considered substantive but not required sections. The instruction: include a section ONLY when posting has real, specific content for it. We have content for About the role (the paragraph at end). Responsibilities: we have bullet-like paragraphs. Requirements: we have required qualifications. Qualifications: maybe same as required? The posting includes "Who are you?" with required and preferred. Could split into Requirements (required) and Qualifications (preferred) or Skills. We need to decide.
We have sections: About the role (we have). Responsibilities (we have). Requirements (required education/experience). Qualifications (maybe preferred). Skills (maybe Tableau, SQL, etc). Benefits, Pay, Schedule: not present, so omit.
We must not create empty sections.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information. So we need to capture responsibilities bullet points, required qualifications, preferred qualifications, skills (maybe list). Also maybe include "About the role" prose.
We must not repeat job title as heading. The job title appears earlier: "Business Operations Manager - Data & Analytics". We must not put that as heading.
We must not include Job ID/requisition numbers.
We must remove duplicated lines: there is some repetition: earlier part "What's the role? The role will play a key part..." and later "About The Role We are looking for...". We need to combine but preserve all info, not duplicate. So we need to synthesize but not lose info. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details, but we can avoid duplication by not repeating same sentence twice. We need to include each distinct piece of info once.
Let's extract distinct pieces:
From the initial description:
- The role will play a key part in the organization's reporting transformation journey and may support future reporting platform initiatives, including the evaluation of emerging analytics and visualization technologies.
Responsibilities (list):
Reporting & Analytics:
- Own and maintain CCO reporting and analytics solutions for Sales Leadership, Regional Sales Operations, and other business stakeholders.
- Design, develop, automate, and enhance dashboards and reporting solutions supporting pipeline, revenue, bookings, forecasting, and operational performance.
- Translate business requirements into actionable analytics and reporting solutions.
- Deliver insights and recommendations to support business decision-making.
- Partner with Sales, Sales Finance, Support & Services, and Sales Operations teams to understand reporting needs and priorities.
Data Management & Governance:
- Serve as the primary point of contact for CCO data, reporting, and analytics topics.
- Partner with TMO, Central Analytics, and business stakeholders to improve data quality and governance.
- Lead data cleansing initiatives and support data warehouse-related projects.
- Ensure reporting data is accurate, consistent, and aligned with business requirements.
Analytics Platforms & Security:
- Lead development, maintenance, and optimization of Tableau dashboards and reporting assets.
- Support reporting transformation initiatives and evaluate emerging analytics and visualization technologies.
- Manage dashboard security, user access permissions, and reporting governance.
- Collaborate with IT and Security teams to ensure compliance with company data governance and security standards.
Stakeholder Management:
- Act as the primary liaison between CCO and TMO on reporting, analytics, and data initiatives.
- Communicate insights and recommendations to both business and technical stakeholders.
- Drive alignment between business priorities and reporting solutions.
Who are you? Required:
- Bachelor's degree in Business, Information Systems, Computer Science, Engineering, Statistics, Data Analytics, or a related field.
- 7+ years of experience in Business Operations, Sales Operations, Business Intelligence, Analytics, or related functions.
- Advanced Tableau development experience, including dashboard design, data modeling, performance optimization, and access management.
- Strong SQL skills and experience working with large enterprise datasets.
- Experience working with data warehouses, reporting platforms, and data governance frameworks.
- Experience managing reporting access controls and security permissions.
- Strong analytical, problem-solving, and stakeholder management skills.
- Excellent communication and presentation skills.
Preferred:
- Experience with AWS QuickSight.
- Experience with Microsoft Power BI.
- Experience supporting sales, revenue, pipeline, forecast, bookings, or operational reporting environments.
- Knowledge of Salesforce reporting and analytics.
- Experience supporting analytics transformation or reporting modernization initiatives.
About The Role (later):
- We are looking for an experienced Business Operations Manager - Data & Analytics to lead reporting, analytics, and data management initiatives for the Chief Customer Office (CCO) organization.
- This role will own and enhance CCO reporting solutions, serve as the primary point of contact for data-related topics, and partner closely with the Transformation Management Office (TMO) to improve data quality, support data warehouse initiatives, and drive the evolution of our analytics platform.
Also there is "Who are we?" description about HERE Technologies. Might be considered substantive but not required sections. Could we include as a
under maybe "About the company"? Not a defined heading. Since we only allowed headings from list, we could omit it. But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the company description, we are losing substantive info. However maybe it's considered boilerplate? It's not navigation/legal/EEO. It's a description of the company. Might be considered substantive. But we have no heading for it; we could include as a
before sections? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra paragraphs outside headings. So we could include a
with company description before the sections. That would preserve info.
But we must not create sections like "About the company" unless heading matches allowed list. We could just put it as a
without heading.
Similarly "Learn more about us on our YouTube Channel." could be considered boilerplate? Might be considered navigation? It's a call to action; maybe we can drop as it's like application instruction? Not exactly. Safer to drop.
Also "HERE Technologies is a location data and technology platform company..." is substantive.
Let's include that as a
before sections.
Now we need to avoid duplication: The "About The Role" paragraph overlaps with earlier description about role playing key part etc. We need to combine but not duplicate. Let's list unique statements:
- The role will play a key part in the organization's reporting transformation journey and may support future reporting platform initiatives, including the evaluation of emerging analytics and visualization technologies. (from first paragraph)
- We are looking for an experienced Business Operations Manager - Data & Analytics to lead reporting, analytics, and data management initiatives for the Chief Customer Office (CCO) organization.
- This role will own and enhance CCO reporting solutions, serve as the primary point of contact for data-related topics, and partner closely with the Transformation Management Office (TMO) to improve data quality, support data warehouse initiatives, and drive the evolution of our analytics platform.
These are distinct enough; we can keep all three.
Now responsibilities: we have bullet points; we can group under
Responsibilities
with a - each.
Requirements: we can have
Requirements
with - for required qualifications.
Qualifications: maybe
Qualifications
for preferred qualifications.
Skills: Could be separate but we already have Tableau, SQL etc in requirements; maybe we can put skills under Requirements. But we have a separate "Skills" heading allowed. Could we split? The posting includes "Advanced Tableau development experience..." etc under required; also "Strong SQL skills". Those are skills. Could we put them under Skills heading? But then we would duplicate if also under Requirements. Better to follow the posting: Required qualifications include education, experience, Tableau, SQL, data warehouses, access controls, analytical skills, communication. Preferred includes QuickSight, Power BI, sales reporting experience, Salesforce knowledge, analytics transformation experience.
We could make Requirements for education + years experience, and Skills for technical skills (Tableau, SQL, etc). But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But we have headings list; we can choose to include Requirements and Qualifications both if they have content. That's okay.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output only HTML fragment.
Let's craft:
HERE Technologies is a location data and technology platform company. We empower our customers to achieve better outcomes – from helping a city manage its infrastructure or a business optimize its assets to guiding drivers to their destination safely. At HERE we take it upon ourselves to be the change we wish to see. We create solutions that fuel innovation, provide opportunity and foster inclusion to improve people’s lives. If you are inspired by an open world and driven to create positive change, join us.
About the role
The role will play a key part in the organization's reporting transformation journey and may support future reporting platform initiatives, including the evaluation of emerging analytics and visualization technologies.
We are looking for an experienced Business Operations Manager - Data & Analytics to lead reporting, analytics, and data management initiatives for the Chief Customer Office (CCO) organization.
This role will own and enhance CCO reporting solutions, serve as the primary point of contact for data-related topics, and partner closely with the Transformation Management Office (TMO) to improve data quality, support data warehouse initiatives, and drive the evolution of our analytics platform.
Responsibilities
- Own and maintain CCO reporting and analytics solutions for Sales Leadership, Regional Sales Operations, and other business stakeholders.
- Design, develop, automate, and enhance dashboards and reporting solutions supporting pipeline, revenue, bookings, forecasting, and operational performance.
- Translate business requirements into actionable analytics and reporting solutions.
- Deliver insights and recommendations to support business decision-making.
- Partner with Sales, Sales Finance, Support & Services, and Sales Operations teams to understand reporting needs and priorities.
- Serve as the primary point of contact for CCO data, reporting, and analytics topics.
- Partner with TMO, Central Analytics, and business stakeholders to improve data quality and governance.
- Lead data cleansing initiatives and support data warehouse-related projects.
- Ensure reporting data is accurate, consistent, and aligned with business requirements.
- Lead development, maintenance, and optimization of Tableau dashboards and reporting assets.
- Support reporting transformation initiatives and evaluate emerging analytics and visualization technologies.
- Manage dashboard security, user access permissions, and reporting governance.
- Collaborate with IT and Security teams to ensure compliance with company data governance and security standards.
- Act as the primary liaison between CCO and TMO on reporting, analytics, and data initiatives.
- Communicate insights and recommendations to both business and technical stakeholders.
- Drive alignment between business priorities and reporting solutions.
Requirements
- Bachelor's degree in Business, Information Systems, Computer Science, Engineering, Statistics, Data Analytics, or a related field.
- 7+ years of experience in Business Operations, Sales Operations, Business Intelligence, Analytics, or related functions.
Skills
- Advanced Tableau development experience, including dashboard design, data modeling, performance optimization, and access management.
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information. So we need to capture responsibilities bullet points, required qualifications, preferred qualifications, skills (maybe list). Also maybe include "About the role" prose. We must not repeat job title as heading. The job title appears earlier: "Business Operations Manager - Data & Analytics". We must not put that as heading. We must not include Job ID/requisition numbers. We must remove duplicated lines: there is some repetition: earlier part "What's the role? The role will play a key part..." and later "About The Role We are looking for...". We need to combine but preserve all info, not duplicate. So we need to synthesize but not lose info. However instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details, but we can avoid duplication by not repeating same sentence twice. We need to include each distinct piece of info once. Let's extract distinct pieces: From the initial description: - The role will play a key part in the organization's reporting transformation journey and may support future reporting platform initiatives, including the evaluation of emerging analytics and visualization technologies. Responsibilities (list): Reporting & Analytics: - Own and maintain CCO reporting and analytics solutions for Sales Leadership, Regional Sales Operations, and other business stakeholders. - Design, develop, automate, and enhance dashboards and reporting solutions supporting pipeline, revenue, bookings, forecasting, and operational performance. - Translate business requirements into actionable analytics and reporting solutions. - Deliver insights and recommendations to support business decision-making. - Partner with Sales, Sales Finance, Support & Services, and Sales Operations teams to understand reporting needs and priorities. Data Management & Governance: - Serve as the primary point of contact for CCO data, reporting, and analytics topics. - Partner with TMO, Central Analytics, and business stakeholders to improve data quality and governance. - Lead data cleansing initiatives and support data warehouse-related projects. - Ensure reporting data is accurate, consistent, and aligned with business requirements. Analytics Platforms & Security: - Lead development, maintenance, and optimization of Tableau dashboards and reporting assets. - Support reporting transformation initiatives and evaluate emerging analytics and visualization technologies. - Manage dashboard security, user access permissions, and reporting governance. - Collaborate with IT and Security teams to ensure compliance with company data governance and security standards. Stakeholder Management: - Act as the primary liaison between CCO and TMO on reporting, analytics, and data initiatives. - Communicate insights and recommendations to both business and technical stakeholders. - Drive alignment between business priorities and reporting solutions. Who are you? Required: - Bachelor's degree in Business, Information Systems, Computer Science, Engineering, Statistics, Data Analytics, or a related field. - 7+ years of experience in Business Operations, Sales Operations, Business Intelligence, Analytics, or related functions. - Advanced Tableau development experience, including dashboard design, data modeling, performance optimization, and access management. - Strong SQL skills and experience working with large enterprise datasets. - Experience working with data warehouses, reporting platforms, and data governance frameworks. - Experience managing reporting access controls and security permissions. - Strong analytical, problem-solving, and stakeholder management skills. - Excellent communication and presentation skills. Preferred: - Experience with AWS QuickSight. - Experience with Microsoft Power BI. - Experience supporting sales, revenue, pipeline, forecast, bookings, or operational reporting environments. - Knowledge of Salesforce reporting and analytics. - Experience supporting analytics transformation or reporting modernization initiatives. About The Role (later): - We are looking for an experienced Business Operations Manager - Data & Analytics to lead reporting, analytics, and data management initiatives for the Chief Customer Office (CCO) organization. - This role will own and enhance CCO reporting solutions, serve as the primary point of contact for data-related topics, and partner closely with the Transformation Management Office (TMO) to improve data quality, support data warehouse initiatives, and drive the evolution of our analytics platform. Also there is "Who are we?" description about HERE Technologies. Might be considered substantive but not required sections. Could we include as a
under maybe "About the company"? Not a defined heading. Since we only allowed headings from list, we could omit it. But instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we omit the company description, we are losing substantive info. However maybe it's considered boilerplate? It's not navigation/legal/EEO. It's a description of the company. Might be considered substantive. But we have no heading for it; we could include as a
before sections? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra paragraphs outside headings. So we could include a
with company description before the sections. That would preserve info. But we must not create sections like "About the company" unless heading matches allowed list. We could just put it as a
without heading. Similarly "Learn more about us on our YouTube Channel." could be considered boilerplate? Might be considered navigation? It's a call to action; maybe we can drop as it's like application instruction? Not exactly. Safer to drop. Also "HERE Technologies is a location data and technology platform company..." is substantive. Let's include that as a
before sections. Now we need to avoid duplication: The "About The Role" paragraph overlaps with earlier description about role playing key part etc. We need to combine but not duplicate. Let's list unique statements: - The role will play a key part in the organization's reporting transformation journey and may support future reporting platform initiatives, including the evaluation of emerging analytics and visualization technologies. (from first paragraph) - We are looking for an experienced Business Operations Manager - Data & Analytics to lead reporting, analytics, and data management initiatives for the Chief Customer Office (CCO) organization. - This role will own and enhance CCO reporting solutions, serve as the primary point of contact for data-related topics, and partner closely with the Transformation Management Office (TMO) to improve data quality, support data warehouse initiatives, and drive the evolution of our analytics platform. These are distinct enough; we can keep all three. Now responsibilities: we have bullet points; we can group under
Responsibilities
with a- each.
Requirements: we can have
Requirements
with- for required qualifications.
Qualifications: maybe
Qualifications
for preferred qualifications. Skills: Could be separate but we already have Tableau, SQL etc in requirements; maybe we can put skills under Requirements. But we have a separate "Skills" heading allowed. Could we split? The posting includes "Advanced Tableau development experience..." etc under required; also "Strong SQL skills". Those are skills. Could we put them under Skills heading? But then we would duplicate if also under Requirements. Better to follow the posting: Required qualifications include education, experience, Tableau, SQL, data warehouses, access controls, analytical skills, communication. Preferred includes QuickSight, Power BI, sales reporting experience, Salesforce knowledge, analytics transformation experience. We could make Requirements for education + years experience, and Skills for technical skills (Tableau, SQL, etc). But the instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But we have headings list; we can choose to include Requirements and Qualifications both if they have content. That's okay. We need to avoid filler like "commensurate with experience". Not present. Now we need to output only HTML fragment. Let's craft:HERE Technologies is a location data and technology platform company. We empower our customers to achieve better outcomes – from helping a city manage its infrastructure or a business optimize its assets to guiding drivers to their destination safely. At HERE we take it upon ourselves to be the change we wish to see. We create solutions that fuel innovation, provide opportunity and foster inclusion to improve people’s lives. If you are inspired by an open world and driven to create positive change, join us.
About the role
The role will play a key part in the organization's reporting transformation journey and may support future reporting platform initiatives, including the evaluation of emerging analytics and visualization technologies.
We are looking for an experienced Business Operations Manager - Data & Analytics to lead reporting, analytics, and data management initiatives for the Chief Customer Office (CCO) organization.
This role will own and enhance CCO reporting solutions, serve as the primary point of contact for data-related topics, and partner closely with the Transformation Management Office (TMO) to improve data quality, support data warehouse initiatives, and drive the evolution of our analytics platform.
Responsibilities
- Own and maintain CCO reporting and analytics solutions for Sales Leadership, Regional Sales Operations, and other business stakeholders.
- Design, develop, automate, and enhance dashboards and reporting solutions supporting pipeline, revenue, bookings, forecasting, and operational performance.
- Translate business requirements into actionable analytics and reporting solutions.
- Deliver insights and recommendations to support business decision-making.
- Partner with Sales, Sales Finance, Support & Services, and Sales Operations teams to understand reporting needs and priorities.
- Serve as the primary point of contact for CCO data, reporting, and analytics topics.
- Partner with TMO, Central Analytics, and business stakeholders to improve data quality and governance.
- Lead data cleansing initiatives and support data warehouse-related projects.
- Ensure reporting data is accurate, consistent, and aligned with business requirements.
- Lead development, maintenance, and optimization of Tableau dashboards and reporting assets.
- Support reporting transformation initiatives and evaluate emerging analytics and visualization technologies.
- Manage dashboard security, user access permissions, and reporting governance.
- Collaborate with IT and Security teams to ensure compliance with company data governance and security standards.
- Act as the primary liaison between CCO and TMO on reporting, analytics, and data initiatives.
- Communicate insights and recommendations to both business and technical stakeholders.
- Drive alignment between business priorities and reporting solutions.
Requirements
- Bachelor's degree in Business, Information Systems, Computer Science, Engineering, Statistics, Data Analytics, or a related field.
- 7+ years of experience in Business Operations, Sales Operations, Business Intelligence, Analytics, or related functions.
Skills
- Advanced Tableau development experience, including dashboard design, data modeling, performance optimization, and access management.
- for required qualifications.
Qualifications: maybe
- each.
Requirements: we can have