Analyst — Customer Performance Analytics
Upbound Group · Plano, TX · 3 wk ago
Business DevelopmentFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the job description.
Sections:
- About the role: Could be "Who We Are" and "Role Summary". That is substantive. So we can have
About the role
with paragraphs summarizing who we are and role summary. - Responsibilities: There's a "Key Responsibilities" and then subheadings: Analysis, Strategy, Day to Day Responsibilities (with subpoints). We can combine into a- list.
- Requirements: Might be "Qualifications" section includes education and experience. Could treat as Requirements.
- Qualifications: Already a heading; but we need to decide if we separate Requirements and Qualifications. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have qualifications: Bachelor’s degree in a quantitative field and/or 2+ years of analytics experience. Customer analytics experience a plus. Creative problem solver who takes initiative. Strong requirements gathering, solutions design, development, quality assurance, business acumen. Demonstrated ability to translate data into actionable insights. Demonstrated ability to create compelling visualizations and storytelling with data via PowerPoint or other deliverable mediums. 2+ years’ experience in data analytics, coding languages as well as other data wrangling tools (Snowflake experience preferred, SQL, Alteryx, AWS). Very strong SQL coding skills required. Demonstrated ability to leverage data visualization tools (PowerBI, Tableau, Sigma would be a plus). Demonstrated ability to take initiative and ownership to move projects forward. Exceptional presentation skills, both verbal and written – ability to present to senior leadership teams. Team-oriented mindset with the ability to give direction and collaborate across various internal teams. Ability to manage time effectively and balance multiple tasks.
We also have "Work Location Ability to work in the Plano, Texas or Draper, Utah office, Monday through Friday, with travel between locations as necessary based on transformation and governance activities." That's schedule/location info. Could go under Schedule (maybe also location). There's no explicit Pay or Benefits mentioned. So we should not create Pay or Benefits sections because they are not stated.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Possibly also "Work Location" under Schedule.
But we need to decide what goes into Skills vs Qualifications. Usually Qualifications includes education/experience; Skills includes technical skills like SQL, Python, etc. The posting includes many skill requirements. We can separate: Qualifications: education and experience baseline. Skills: technical skills (SQL, SAS, Python, PowerBI, Tableau, Sigma, Snowflake, Alteryx, AWS, data visualization, storytelling, presentation). Requirements maybe overlapping; but we can treat Requirements as the core responsibilities? Actually "Requirements" heading often used for mandatory qualifications. But we already have Qualifications. To avoid duplication, we could map:
- About the role: Who we are + Role Summary.
- Responsibilities: list of responsibilities (Analysis, Strategy, Day to Day, Operational Excellence, Full Funnel Analytics & Reporting Excellence, Strategic business partnership).
- Requirements: maybe the mandatory qualifications: Bachelor’s degree in a quantitative field and/or 2+ years of analytics experience; 2+ years’ experience in data analytics, coding languages; Very strong SQL coding skills required; Ability to work in Plano, Texas or Draper, Utah office, Monday through Friday, with travel; Employment eligibility (authorized to work in US, no sponsorship). But the instruction says remove boilerplate like employment eligibility? It's not exactly boilerplate but it's a requirement. Might keep.
- Qualifications: maybe the "plus" items: Customer analytics experience a plus; Creative problem solver; Strong requirements gathering; Demonstrated ability to translate data into actionable insights; Demonstrated ability to create compelling visualizations; etc. But that seems messy.
Better: Follow typical pattern: Requirements = mandatory qualifications; Qualifications = preferred qualifications; Skills = technical skills. However the instruction says we should only include sections when posting has real specific content. So we can include all three if we have content.
Let's extract:
Mandatory (Requirements):
- Bachelor’s degree in a quantitative field and/or 2+ years of analytics experience.
- 2+ years’ experience in data analytics, coding languages as well as other data wrangling tools (Snowflake experience preferred, SQL, Alteryx, AWS).
- Very strong SQL coding skills required.
- Ability to work in the Plano, Texas or Draper, Utah office, Monday through Friday, with travel between locations as necessary based on transformation and governance activities.
- Must be authorized to work in the U.S.; Upbound Group does not offer employment-based immigration sponsorship for this role, including OPT or CPT. (This is eligibility; we can keep as part of Requirements.)
Preferred/Qualifications:
- Customer analytics experience a plus.
- Creative problem solver who takes initiative.
- Strong requirements gathering, solutions design, development, quality assurance, business acumen.
- Demonstrated ability to translate data into actionable insights.
- Demonstrated ability to create compelling visualizations and storytelling with data via PowerPoint or other deliverable mediums.
- Demonstrated ability to leverage data visualization tools (PowerBI, Tableau, Sigma would be a plus).
- Demonstrated ability to take initiative and ownership to move projects forward.
- Exceptional presentation skills, both verbal and written – ability to present to senior leadership teams.
- Team-oriented mindset with the ability to give direction and collaborate across various internal teams.
- Ability to manage time effectively and balance multiple tasks.
Skills (technical):
- SQL, SAS, Python.
- Power BI/Sigma, Tableau (mentioned as plus).
- Snowflake/Snowflake Cowork.
- Alteryx, AWS.
- Data storytelling, visualization, business communication.
- PowerPoint or other deliverable mediums.
- Possibly SAS? It's mentioned: "use both tool-based analytics and coding languages, like SQL, SAS, and Python."
Thus we can list skills.
Now schedule: The work location and schedule (Monday through Friday) is schedule info. Could be under Schedule.
Benefits: none stated.
Pay: none stated.
Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule.
We must not include empty sections.
Now produce HTML:
About the role
... paragraphs ...
Responsibilities
- ... each responsibility as list item ...