Senior Data Analyst
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, 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 (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to extract content.
Job Title: Senior Data Analyst (but not heading). Location: Omaha, NE (Onsite – 5 days a week). That's schedule info: Onsite 5 days a week. So we can have a Schedule section with that.
Pay: The base salary for this position is $92,250 to $125,000 plus incentives that align with individual and company performance. Actual salaries will vary based on work location, qualifications, skills, education, experience, and competencies. That's pay info. So we can have Pay section.
Benefits: Benefits available to eligible employees in this role include medical, dental, and vision insurance, comprehensive employee assistance program, 401(k) retirement plan, paid time off and holidays and paid learning days. So Benefits section.
About the role: The description includes many paragraphs about Concentrix, the team, role description. We need to put that in About the role section. Should we include the "Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week)"? That's location and schedule; schedule we already have. The role description: "We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams." That's part of About the role.
Responsibilities: The "Key Responsibilities" bullet list.
Requirements: Might be "Required Skills"? Actually "Required Skills" is a list of skills. Could be considered Skills section. But we also have "Preferred Skills". And "Qualifications" (education, years experience). The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have:
- About the role: description of company, team, role overview.
- Responsibilities: list of key responsibilities.
- Requirements: maybe "Required Skills"? But they also have "Qualifications" (education, experience). The heading "Requirements" could be for required skills? However they also have a separate "Qualifications" heading. Usually "Requirements" could be required skills, and "Qualifications" could be education/experience. But we need to decide.
Given the list of possible headings, we should include sections that have substantive content.
We have:
- Required Skills: list (SQL, visualization tools, Python/R, data warehouse, ETL/ELT, Excel, data quality frameworks). That's skills.
- Preferred Skills: list (operational/realtime reporting, railroad/logistics/transportation data, Azure data stack, event-driven systems). That's also skills but could be placed under Skills as well, maybe separate? But we have only one Skills heading allowed. Could combine required and preferred under Skills, maybe with subheadings? But we must not invent headings beyond allowed. Could put both under Skills, maybe separate lists with notes.
- Qualifications: Bachelor’s degree..., 7+ years experience, proven experience building enterprise-grade reporting solutions. That's qualifications.
- Pay: salary range.
- Benefits: list.
- Schedule: Onsite – 5 days a week.
- Responsibilities: list.
- About the role: prose.
We should not include sections like "Requirements" if we don't have distinct content besides skills? But we have Required Skills; we could treat that as Requirements. However we also have Skills heading. Might be redundant. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. We need to decide which to include based on content.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements: we have Required Skills (could be considered requirements). Also maybe "Physical And Mental Requirements" but that's boilerplate (should be removed). So we can put Required Skills under Requirements.
- Qualifications: yes (education, experience).
- Skills: we have Preferred Skills (maybe also required skills but we already used Required Skills under Requirements). Could still have Skills section for preferred skills, or we could combine required and preferred under Skills and not have Requirements. But we have both Required Skills and Preferred Skills; we could put Required Skills under Requirements and Preferred Skills under Skills. That seems logical.
- Benefits: yes.
- Pay: yes.
- Schedule: yes.
Thus we will include all eight sections.
Now we need to strip boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to remove:
- "We're Concentrix..." paragraphs about company? That's part of About the role; we keep substantive info about company, team, role. That's okay.
- "Join us and be part of this journey towards greater opportunities and brighter futures." That's fluff but maybe part of About the role; we can keep as it's substantive? It's somewhat generic but not boilerplate. Might keep.
- "Physical And Mental Requirements" section: remove.
- "Equal Employment Opportunity" etc: remove.
- "Accommodation" etc: remove.
- "Artificial Intelligence" etc: remove.
- "Work Authorization" etc: remove.
- "#Omaha #Nebraska" maybe remove as it's just tags.
- "The deadline to apply for this position is: 06/14/2026." That's application instruction? It's a deadline; maybe considered application instruction? The instruction says remove application instructions. So we should remove deadline line.
- "This position is for an existing, immediate vacancy. We are currently seeking to fill this role with an individual who can start as soon as possible." That's also application instruction? Might be considered filler but it's substantive about immediacy. Might keep? It's not a boilerplate; it's about vacancy. Could keep in About the role? Might be considered part of role description. I'd keep it.
- "As part of the hiring process, candidates may be required to undergo background screening and identity verification..." That's legal/boilerplate; remove.
- "Certain verification processes used by the Company or its service providers may involve technologies that rely on biometric identifiers..." remove.
- "If biometric identifiers..." remove.
- "#Omaha #Nebraska" remove.
Now we need to format.
We'll produce HTML fragment with headings and content.
For lists, use - .
For prose, use
.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract each section's content.
**About the role**:
We need to combine the descriptive paragraphs about Concentrix, the team, role overview.
Original text:
"We're Concentrix. The intelligent transformation partner. Solution-focused. Tech-powered. Intelligence-fueled. The global technology and services leader that powers the world’s best brands, today and into the future. We’re solution-focused, tech-powered, intelligence-fueled. With unique data and insights, deep industry expertise, and advanced technology solutions, we’re the intelligent transformation partner that powers a world that works, helping companies become refreshingly simple to work, interact, and transact with. We shape new game-changing careers in over 70 countries, attracting the best talent. The Concentrix Technical Products and Services team is the driving force behind Concentrix’s transformation, data, and technology services. We integrate world-class digital engineering, creativity, and a deep understanding of human behavior to find and unlock value through tech-powered and intelligence-fueled experiences. We combine human-centered design, powerful data, and strong tech to accelerate transformation at scale. You will be surrounded by the best in the world providing market leading technology and insights to modernize and simplify the customer experience. Within our professional services team, you will deliver strategic consulting, design, advisory services, market research, and contact center analytics that deliver insights to improve outcomes and value for our clients. Hence achieving our vision. Our gamechangers around the world have devoted their careers to ensuring every relationship is exceptional. And we’re proud to be recognized with awards such as "World's Best Workplaces,” “Best Companies for Career Growth,” and “Best Company Culture,” year after year. Join us and be part of this journey towards greater opportunities and brighter futures.
Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week) We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams."
We need to avoid repeating job title as heading, but we can include the role description prose. The "Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week)" includes location and schedule; we will extract schedule for Schedule section, location maybe not needed as heading but could be included in About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location and schedule could be minor metadata; we could put them in a short
under About the role or separate Schedule section. Since we have a Schedule section, we can put schedule there. Location could be included in About the role as a short sentence.
Thus About the role prose: all the descriptive paragraphs about company, team, role overview, plus maybe "We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams." That's part of role overview.
We should not include the deadline, etc.
Now Responsibilities: list from "Key Responsibilities". Let's extract each bullet:
- Design and build end-to-end reporting solutions, including dashboards, recurring reports, and ad-hoc analysis aligned to business needs.
- Partner with stakeholders across Operations, DQAS, OPCC, and Technology teams to define reporting requirements and KPIs.
- Develop and maintain data models and pipelines to support reliable reporting.
- Analyze large datasets to identify trends, anomalies, and opportunities for operational improvement.
- Own data quality validation and ensure accuracy across reporting outputs.
- Translate complex data into clear, actionable insights for leadership.
- Drive standardization and automation of reporting processes to reduce manual effort.
- Support incident analysis by providing data-backed root cause insights.
- Collaborate with engineering teams on data sourcing, transformations, and performance optimization.
We need to keep each as
- .
Now Requirements: we have Required Skills list:
- Strong SQL skills, including complex joins, performance tuning, and data validation.
- Experience with data visualization tools such as Power BI, Tableau, or similar platforms.
- Proficiency in data wrangling and analysis using Python or R.
- Experience working with large datasets and data warehouse platforms such as Snowflake, Azure, Hadoop, or similar technologies.
- Understanding of ETL/ELT pipelines and data modeling concepts.
- Strong Excel skills for ad-hoc analysis and validation work.
- Experience with data quality frameworks and validation techniques.
We'll put these under Requirements.
Now Qualifications:
- Bachelor’s degree in Data Science, Computer Science, Statistics, Engineering
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, 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 (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to extract content. Job Title: Senior Data Analyst (but not heading). Location: Omaha, NE (Onsite – 5 days a week). That's schedule info: Onsite 5 days a week. So we can have a Schedule section with that. Pay: The base salary for this position is $92,250 to $125,000 plus incentives that align with individual and company performance. Actual salaries will vary based on work location, qualifications, skills, education, experience, and competencies. That's pay info. So we can have Pay section. Benefits: Benefits available to eligible employees in this role include medical, dental, and vision insurance, comprehensive employee assistance program, 401(k) retirement plan, paid time off and holidays and paid learning days. So Benefits section. About the role: The description includes many paragraphs about Concentrix, the team, role description. We need to put that in About the role section. Should we include the "Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week)"? That's location and schedule; schedule we already have. The role description: "We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams." That's part of About the role. Responsibilities: The "Key Responsibilities" bullet list. Requirements: Might be "Required Skills"? Actually "Required Skills" is a list of skills. Could be considered Skills section. But we also have "Preferred Skills". And "Qualifications" (education, years experience). The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About the role: description of company, team, role overview. - Responsibilities: list of key responsibilities. - Requirements: maybe "Required Skills"? But they also have "Qualifications" (education, experience). The heading "Requirements" could be for required skills? However they also have a separate "Qualifications" heading. Usually "Requirements" could be required skills, and "Qualifications" could be education/experience. But we need to decide. Given the list of possible headings, we should include sections that have substantive content. We have: - Required Skills: list (SQL, visualization tools, Python/R, data warehouse, ETL/ELT, Excel, data quality frameworks). That's skills. - Preferred Skills: list (operational/realtime reporting, railroad/logistics/transportation data, Azure data stack, event-driven systems). That's also skills but could be placed under Skills as well, maybe separate? But we have only one Skills heading allowed. Could combine required and preferred under Skills, maybe with subheadings? But we must not invent headings beyond allowed. Could put both under Skills, maybe separate lists with notes. - Qualifications: Bachelor’s degree..., 7+ years experience, proven experience building enterprise-grade reporting solutions. That's qualifications. - Pay: salary range. - Benefits: list. - Schedule: Onsite – 5 days a week. - Responsibilities: list. - About the role: prose. We should not include sections like "Requirements" if we don't have distinct content besides skills? But we have Required Skills; we could treat that as Requirements. However we also have Skills heading. Might be redundant. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. We need to decide which to include based on content.
We have content for:
- About the role: yes.
- Responsibilities: yes.
- Requirements: we have Required Skills (could be considered requirements). Also maybe "Physical And Mental Requirements" but that's boilerplate (should be removed). So we can put Required Skills under Requirements.
- Qualifications: yes (education, experience).
- Skills: we have Preferred Skills (maybe also required skills but we already used Required Skills under Requirements). Could still have Skills section for preferred skills, or we could combine required and preferred under Skills and not have Requirements. But we have both Required Skills and Preferred Skills; we could put Required Skills under Requirements and Preferred Skills under Skills. That seems logical.
- Benefits: yes.
- Pay: yes.
- Schedule: yes.
Thus we will include all eight sections.
Now we need to strip boilerplate: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to remove:
- "We're Concentrix..." paragraphs about company? That's part of About the role; we keep substantive info about company, team, role. That's okay.
- "Join us and be part of this journey towards greater opportunities and brighter futures." That's fluff but maybe part of About the role; we can keep as it's substantive? It's somewhat generic but not boilerplate. Might keep.
- "Physical And Mental Requirements" section: remove.
- "Equal Employment Opportunity" etc: remove.
- "Accommodation" etc: remove.
- "Artificial Intelligence" etc: remove.
- "Work Authorization" etc: remove.
- "#Omaha #Nebraska" maybe remove as it's just tags.
- "The deadline to apply for this position is: 06/14/2026." That's application instruction? It's a deadline; maybe considered application instruction? The instruction says remove application instructions. So we should remove deadline line.
- "This position is for an existing, immediate vacancy. We are currently seeking to fill this role with an individual who can start as soon as possible." That's also application instruction? Might be considered filler but it's substantive about immediacy. Might keep? It's not a boilerplate; it's about vacancy. Could keep in About the role? Might be considered part of role description. I'd keep it.
- "As part of the hiring process, candidates may be required to undergo background screening and identity verification..." That's legal/boilerplate; remove.
- "Certain verification processes used by the Company or its service providers may involve technologies that rely on biometric identifiers..." remove.
- "If biometric identifiers..." remove.
- "#Omaha #Nebraska" remove.
Now we need to format.
We'll produce HTML fragment with headings and content.
For lists, use - .
For prose, use
.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract each section's content.
**About the role**:
We need to combine the descriptive paragraphs about Concentrix, the team, role overview.
Original text:
"We're Concentrix. The intelligent transformation partner. Solution-focused. Tech-powered. Intelligence-fueled. The global technology and services leader that powers the world’s best brands, today and into the future. We’re solution-focused, tech-powered, intelligence-fueled. With unique data and insights, deep industry expertise, and advanced technology solutions, we’re the intelligent transformation partner that powers a world that works, helping companies become refreshingly simple to work, interact, and transact with. We shape new game-changing careers in over 70 countries, attracting the best talent. The Concentrix Technical Products and Services team is the driving force behind Concentrix’s transformation, data, and technology services. We integrate world-class digital engineering, creativity, and a deep understanding of human behavior to find and unlock value through tech-powered and intelligence-fueled experiences. We combine human-centered design, powerful data, and strong tech to accelerate transformation at scale. You will be surrounded by the best in the world providing market leading technology and insights to modernize and simplify the customer experience. Within our professional services team, you will deliver strategic consulting, design, advisory services, market research, and contact center analytics that deliver insights to improve outcomes and value for our clients. Hence achieving our vision. Our gamechangers around the world have devoted their careers to ensuring every relationship is exceptional. And we’re proud to be recognized with awards such as "World's Best Workplaces,” “Best Companies for Career Growth,” and “Best Company Culture,” year after year. Join us and be part of this journey towards greater opportunities and brighter futures.
Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week) We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams."
We need to avoid repeating job title as heading, but we can include the role description prose. The "Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week)" includes location and schedule; we will extract schedule for Schedule section, location maybe not needed as heading but could be included in About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location and schedule could be minor metadata; we could put them in a short
under About the role or separate Schedule section. Since we have a Schedule section, we can put schedule there. Location could be included in About the role as a short sentence.
Thus About the role prose: all the descriptive paragraphs about company, team, role overview, plus maybe "We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams." That's part of role overview.
We should not include the deadline, etc.
Now Responsibilities: list from "Key Responsibilities". Let's extract each bullet:
- Design and build end-to-end reporting solutions, including dashboards, recurring reports, and ad-hoc analysis aligned to business needs.
- Partner with stakeholders across Operations, DQAS, OPCC, and Technology teams to define reporting requirements and KPIs.
- Develop and maintain data models and pipelines to support reliable reporting.
- Analyze large datasets to identify trends, anomalies, and opportunities for operational improvement.
- Own data quality validation and ensure accuracy across reporting outputs.
- Translate complex data into clear, actionable insights for leadership.
- Drive standardization and automation of reporting processes to reduce manual effort.
- Support incident analysis by providing data-backed root cause insights.
- Collaborate with engineering teams on data sourcing, transformations, and performance optimization.
We need to keep each as
- .
Now Requirements: we have Required Skills list:
- Strong SQL skills, including complex joins, performance tuning, and data validation.
- Experience with data visualization tools such as Power BI, Tableau, or similar platforms.
- Proficiency in data wrangling and analysis using Python or R.
- Experience working with large datasets and data warehouse platforms such as Snowflake, Azure, Hadoop, or similar technologies.
- Understanding of ETL/ELT pipelines and data modeling concepts.
- Strong Excel skills for ad-hoc analysis and validation work.
- Experience with data quality frameworks and validation techniques.
We'll put these under Requirements.
Now Qualifications:
- Bachelor’s degree in Data Science, Computer Science, Statistics, Engineering
- .
For prose, use
. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract each section's content. **About the role**: We need to combine the descriptive paragraphs about Concentrix, the team, role overview. Original text: "We're Concentrix. The intelligent transformation partner. Solution-focused. Tech-powered. Intelligence-fueled. The global technology and services leader that powers the world’s best brands, today and into the future. We’re solution-focused, tech-powered, intelligence-fueled. With unique data and insights, deep industry expertise, and advanced technology solutions, we’re the intelligent transformation partner that powers a world that works, helping companies become refreshingly simple to work, interact, and transact with. We shape new game-changing careers in over 70 countries, attracting the best talent. The Concentrix Technical Products and Services team is the driving force behind Concentrix’s transformation, data, and technology services. We integrate world-class digital engineering, creativity, and a deep understanding of human behavior to find and unlock value through tech-powered and intelligence-fueled experiences. We combine human-centered design, powerful data, and strong tech to accelerate transformation at scale. You will be surrounded by the best in the world providing market leading technology and insights to modernize and simplify the customer experience. Within our professional services team, you will deliver strategic consulting, design, advisory services, market research, and contact center analytics that deliver insights to improve outcomes and value for our clients. Hence achieving our vision. Our gamechangers around the world have devoted their careers to ensuring every relationship is exceptional. And we’re proud to be recognized with awards such as "World's Best Workplaces,” “Best Companies for Career Growth,” and “Best Company Culture,” year after year. Join us and be part of this journey towards greater opportunities and brighter futures. Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week) We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams." We need to avoid repeating job title as heading, but we can include the role description prose. The "Role: Sr Data Analyst Location: Omaha, NE (Onsite – 5 days a week)" includes location and schedule; we will extract schedule for Schedule section, location maybe not needed as heading but could be included in About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So location and schedule could be minor metadata; we could put them in a short
under About the role or separate Schedule section. Since we have a Schedule section, we can put schedule there. Location could be included in About the role as a short sentence. Thus About the role prose: all the descriptive paragraphs about company, team, role overview, plus maybe "We are looking for a Senior Data Analyst to lead reporting and analytics efforts across operations. This role will focus on building scalable, accurate reporting, identifying insights from operational data, and enabling data-driven decisions across business and technology teams." That's part of role overview. We should not include the deadline, etc. Now Responsibilities: list from "Key Responsibilities". Let's extract each bullet: - Design and build end-to-end reporting solutions, including dashboards, recurring reports, and ad-hoc analysis aligned to business needs. - Partner with stakeholders across Operations, DQAS, OPCC, and Technology teams to define reporting requirements and KPIs. - Develop and maintain data models and pipelines to support reliable reporting. - Analyze large datasets to identify trends, anomalies, and opportunities for operational improvement. - Own data quality validation and ensure accuracy across reporting outputs. - Translate complex data into clear, actionable insights for leadership. - Drive standardization and automation of reporting processes to reduce manual effort. - Support incident analysis by providing data-backed root cause insights. - Collaborate with engineering teams on data sourcing, transformations, and performance optimization. We need to keep each as
- . Now Requirements: we have Required Skills list: - Strong SQL skills, including complex joins, performance tuning, and data validation. - Experience with data visualization tools such as Power BI, Tableau, or similar platforms. - Proficiency in data wrangling and analysis using Python or R. - Experience working with large datasets and data warehouse platforms such as Snowflake, Azure, Hadoop, or similar technologies. - Understanding of ETL/ELT pipelines and data modeling concepts. - Strong Excel skills for ad-hoc analysis and validation work. - Experience with data quality frameworks and validation techniques. We'll put these under Requirements. Now Qualifications: - Bachelor’s degree in Data Science, Computer Science, Statistics, Engineering