Data Visualization Engineer, Client Delivery
About the role
. Then Responsibilities, Requirements, Benefits, Pay, Schedule. Ensure we only include sections with real content. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: About Ovative Group intro, EEO, accessibility, application details, etc. Also remove duplicated lines. We need to extract the relevant content. Let's parse: About Ovative Group: intro about company - maybe not needed? The instruction: "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 shortor drop it." The "About Ovative Group" is company overview; not a section heading we need? The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include a section for company overview. So we can drop that paragraph. About The Role: we need to include that content under About the role heading. Responsibilities: list. Requirements: list. Benefits: list. Pay: salary range. Schedule: office days/remote. We must not include sections like Qualifications or Skills unless content exists; we have Requirements covering qualifications; we can keep Requirements. We must not include placeholder text. Now extract content. About The Role paragraph: "Marketers rely on clear, trustworthy data visualization to understand complex datasets and get the most out of their marketing investment. As a Data Visualization Engineer on our Client Delivery team, you'll design, build, and roll out analytics solutions that marketers use every day — including EMRge MMM, our flagship product. You'll work hands-on with tools like SQL, Tableau, and GitHub, and bring a curiosity for modern AI tools into your daily workflow, balancing AI-assisted development with rigorous testing, documentation, and review. You'll own reporting solutions across the full lifecycle — from gathering requirements with clients and internal stakeholders to shipping a finished dashboard — and collaborate closely with both technical and business teams along the way. The right candidate has a passion for data and analytics, strong problem-solving instincts, and a design-thinking mindset. You have hands-on experience building client-facing reporting dashboards and can troubleshoot issues when something doesn't look right. Strong communication and organization skills matter here — you'll be managing multiple projects and deadlines at once on a fast-paced, growing team." We'll put that in
. Responsibilities: bullet list from "Responsibilities Of a Data Visualization Engineer, Client Delivery" then bullet points. Let's extract each bullet: - Translate client needs into reporting solutions - Work with clients and internal stakeholders to understand reporting needs, gather requirements, and define use cases for new reporting capabilities - Define and communicate precise data requirements to engineering partners, ensuring underlying datasets support outputs like year-over-year performance, segmentation, and advanced marketing KPIs - Collaborate with engineering on dataset and pipeline needs, including orchestration tools (e.g., Dagster, Airflow), to make sure the data powering client reporting is reliable and fit for purpose - Create and review proposals with key stakeholders to roll out reporting solutions quickly and meet client needs - Bridge design and development in Tableau, upholding data visualization best practices and client standards - Apply a UI/UX lens to visualizations, keeping a consistent approach across solutions so they scale - Deliver with quality and rigor - Onboard new clients onto our reporting platforms and EMRge MMM, setting them up for a smooth, successful launch - Design, develop, test, and deploy reporting and software solutions that meet business and technical requirements - Take new features from beta through general availability, and maintain existing solutions as client needs evolve - Own documentation — technical requirements, evaluation plans, test results, and recommendations - Follow established engineering best practices: code quality, documentation, deployment, and testing - Troubleshoot reporting and software issues independently, escalating and collaborating as needed, including participating in an on-call rotation to support production systems - Leverage AI-assisted development tools (e.g., GitHub Copilot, Claude, internal LLM tooling) to explore solution options, generate scaffolding, and improve velocity — while maintaining code quality and security - Grow with the team - Share technical expertise and provide guidance to teammates as needed - Participate in knowledge sharing and stay current on emerging technology and engineering practices - Explore and champion new tools and technologies that improve how the team works - Actively contribute to team culture and continue building toward your own professional development We need to format as
- . For sub-bullets, we could nest
- inside
- or just keep as separate
- with dash? Probably better to keep flat list; but we can nest.
Requirements:
- 3+ years building enterprise products in reporting, data, and/or analytics space
- Experience with writing, updating, and optimizing SQL queries to develop datasets
- Proven analytical skillset with ability to derive insights out of large datasets and present findings in an appropriately detailed manner
- Experience with data visualization tools i.e. Tableau to create client facing reporting
- Familiarity with orchestration tools i.e. Dagster, Airflow
- Foundational organization skills and ability to manage multiple projects and deadlines
- Foundational technical acumen and desire to work within a technical environment
- Familiarity working with technical and business teams – including presenting technical requirements to non-technical audiences
Preferred (maybe we could include under Requirements or separate Skills? The instruction: we can have Skills section but we don't have explicit Skills; we could put Preferred under Requirements or maybe a Skills section. But we should not create sections without real content; we have Preferred content, we could include under Requirements as additional bullet points, or create a Skills section. The allowed headings include Skills. We could create a Skills section for Preferred items. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep Requirements and include both required and preferred within that section. That's fine.
Benefits: list from "Benefits" section.
Extract:
- Access to all office spaces in MSP, NYC, and CHI
- Frequent, paid travel to our Minneapolis headquarters for company events, team events, and in-person collaboration with teams
- Generous paid vacation policy
- 401k match program
- Top-notch health insurance options, inclusive of same sex partners
- Family formation benefits including reimbursement options for fertility, pregnancy, and parenting needs
- Monthly stipend for your mobile phone and data plan
- Sabbatical program
- Charitable giving via our time and a financial match program
- Shenanigan’s Day
Pay: from Pay Transparency:
"For our Sr. Analyst positions, including the position of Data Visualization Engineer, Client Delivery, our compensation range is from $75,000 to $93,000 on an annualized basis, which is inclusive of an annual bonus opportunity of up to 15% of base salary."
We'll put that in
under Pay heading. Schedule: from Working At Ovative Group: "We offer flexibility. You'll work from our Minneapolis, Chicago, or New York office on set days each week, and an option to work remote on others." Also maybe mention open floor plan etc but that's culture; not schedule. We'll keep schedule as that. Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
- items under the same parent
- but maybe better to nest.
We'll do:
- Translate client needs into reporting solutions
- Work with clients and internal stakeholders to understand reporting needs, gather requirements, and define use cases for new reporting capabilities ...
- Deliver with quality and rigor
- Onboard new clients onto our reporting platforms and EMRge MMM, setting them up for a smooth, successful launch ...
...