Staff Business Intelligence Data Analyst

We need to output HTML fragment with sections: About the role? Actually the posting includes description about Jamf culture etc. We need to use

for section 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 as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Key parts: Intro about Jamf culture: "At Jamf, we believe in an open, flexible culture based on respect and trust..." This is about the company. Could be "About the role"? Actually "About the role" is typical heading for role description. But we have a description of what you'll do at Jamf: "What you'll do at Jamf: The Staff Business Intelligence Data Analyst is a senior individual contributor..." That's responsibilities. So we can have sections: About the role (maybe a brief summary?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could include the introductory paragraph about Jamf culture and mission? Might be considered "About the role". The posting includes "At Jamf, we believe..." and later "What does Jamf do?" That's about the company. Could be placed under About the role. - Responsibilities: The bullet list under "What you can expect to do in this role:" includes many items. Those are responsibilities. - Requirements: The "What we are looking for:" list includes required experience: 8+ years, expert-level SQL, etc. Those are requirements. - Qualifications: Education & Certifications section: Bachelor's degree, relevant certifications a plus. - Skills: Core Competencies: communication, analytical problem-solving, ownership and autonomy. - Benefits: The section "How we help you reach your best potential:" includes awards, volunteer time off, etc. Also maybe "We know that big ideas can come from anyone..." etc. That's benefits/perks. Also "Our volunteer time off allows employees to support and give back to our communities." etc. So we can include Benefits. - Pay: The "Pay Transparency" section includes national pay transparency range $115,000—$178,000 USD. That's pay info. - Schedule: No explicit schedule info (like full-time, remote, etc.) Not present. So we should not create Schedule section. We must not create sections with filler like "commensurate with experience". Pay section we have actual range, so include. We must not repeat job title as heading. So no heading for Staff Business Intelligence Data Analyst. We must not include Job ID/requisition numbers. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement and accommodation request. Remove that. Also remove duplicated lines like "Named a 2025 Best Companies to Work For by U.S. News" repeated? Actually appears multiple times with different years. We need to preserve all substantive information; but we can combine duplicates? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep each award line, even if similar but different year/category. However duplicates: there are two lines for "Named a 2024 Best Companies to Work For by U.S. News" appears twice? Actually appears: "Named a 2024 Best Companies to Work For by U.S. News" appears once earlier and later again? Let's see: In the list: "Named a 2025 Best Companies to Work For by U.S. NewsNamed a 2025 Newsweek America’s Greatest Workplaces for Mental Well-beingNamed a 2025 Newsweek America’s Greatest Workplaces for Gen ZNamed one of Forbes Most Trusted Companies in 2024Named a 2024 Best Companies to Work For by U.S. NewsNamed a 2024 Newsweek America’s Greatest Workplaces for Parents & FamiliesNamed a 2024 PEOPLE Companies That Care by PEOPLE® and Great Place To Work®Named a 2024 Best Technology Company to Work For by U.S. News". So each is distinct. No duplicate exact same line. We'll keep them as list items. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

About the role

... (intro about Jamf culture and mission)

Responsibilities

• ... each responsibility

Requirements

• ... each required item

Qualifications

• ... education and certifications

Skills

• ... core competencies

Benefits

• ... benefits/perks

Pay

... pay range

We must not include Schedule. Now we need to extract exact text. Let's copy relevant sections. About the role: The intro before "What you'll do at Jamf:" includes: "At Jamf, we believe in an open, flexible culture based on respect and trust. Our track record and thriving work environment all stem from the freedom we grant ourselves to get the job done right. We take pride in helping tens of thousands of customers around the globe succeed with Apple. The secret to our success lies in our connectivity, while operating with a high degree of flexibility. Work-life balance remains our priority while feeling connected is important to maintain our strong culture, achieve our goals, and thrive as #OneJamf." Also later there is "What does Jamf do?" paragraph describing product. Could also be included in About the role. Might be better to include that as part of About the role as it describes the company. The instruction: preserve ALL substantive information. So we should include that too. Thus About the role paragraph(s) could be two paragraphs: first culture intro, second description of what Jamf does. Let's extract "What does Jamf do?" paragraph: "What does Jamf do? Jamf extends the legendary Apple experience people enjoy in their personal lives to the workplace. We believe the experience of using a device at work or school should feel the same, and be as secure as, using a personal device. With Jamf, customers are able to confidently automate Mac, iPad, iPhone and Apple TV deployment, management, and security – anytime, anywhere – to protect the data and applications used by employees in the workplace, students learning in the classroom, and streamline communications in healthcare between patients and providers. More than 2,500 Jamf strong worldwide, we are free-thinkers, can-doers, and problems crushers who are encouraged to bring their whole selves to work each and every day. Get social with us and follow the conversation at #OneJamf" We can include that as part of About the role. Now Responsibilities: list under "What you can expect to do in this role:" includes multiple sentences each starting with a verb. We'll turn each into

. Let's list them: - Drive strategic impact by leading analytical roadmaps and initiatives that align with Jamf's long-term goals. - Identify high-impact opportunities, cut through ambiguity on critical initiatives, and represent the data function in leadership forums. - Take end-to-end ownership of complex, cross-functional analytical projects, from scoping and stakeholder alignment through to delivery. - Partner with senior leadership and functional analysts as a trusted analytical advisor across Sales, Marketing, Finance, and Operations, translating business questions into scalable data products and delivering insights that shape decisions. - Set the standard for metrics definition, data modeling, data storytelling, and analytical best practice across the team. Lead the design of scalable data infrastructure and workflows using tools such as dbt, and maintain a high bar for code quality and system design. - Lead cross-departmental initiatives that grow data literacy across Jamf, including developing enablement resources, running training sessions, and embedding data-driven thinking into how teams operate. - Contribute to roadmap and vision planning alongside Business Intelligence leadership. - Mentor analysts at all levels, accelerating their technical and business growth, and foster a culture of autonomy, constructive feedback, and continuous learning. - Own data quality and governance by driving the health, integrity, and discoverability of Jamf's data assets, leading stewardship practices, maintaining the data catalog, and ensuring data is trusted across the organization. Check if any duplicated: looks fine. Now Requirements: under "What we are looking for:" includes required items: - 8+ years in data as an analyst, engineer, or scientist, including 6+ years working with large-scale (1B+ row) cloud data warehouses and 6+ years using business intelligence tools such as Tableau, Looker, Power BI, or DOMO. (Required) - Expert-level SQL and 4+ years building data models within a modern data stack (dbt, Snowflake, or equivalent), including layered modeling, testing, performance optimization, and cost management. (Required) - Strong analytics engineering and data system design across databases, schemas, marts, aggregates, and views, including 4+ years extending and maintaining a data model system to serve multiple business use cases, with the ability to architect scalable, future-proofed solutions and set technical direction for a team. (Required) - Demonstrated ownership of large, complex, cross-functional analytics projects from scoping through delivery. (Required) - Experience with data access and security practices both within and outside of a data warehouse. (Required) Also there are Preferred items: "Preferred Experience building multi-quarter analytical roadmaps or leading organization-wide data initiatives." etc. Those could go under Requirements as preferred? But we have a separate Skills section for core competencies. Preferred experience could be placed under Requirements as well, but we might treat them as Requirements (preferred). However we have a separate Skills section for core competencies. The preferred experience items are not core competencies but experience. Could be placed under Requirements as well, but we need to decide where to put them. The instruction: Use sections only when posting has real specific content. We have preferred experience lines; we could include them under Requirements as well (maybe as separate bullet). Or we could create a separate "Preferred Qualifications" but not in allowed headings. Allowed headings are limited to those eight. So we must fit them into one of those. Could put under Requirements (mix required and preferred) or under Qualifications (education/certs) or Skills. Probably best to put under Requirements as they are experience/qualifications. We'll include them. Preferred items: - Experience building multi-quarter analytical roadmaps or leading organization-wide data initiatives. - Experience introducing a new tool, technique, or pattern to a team, with measurable productivity or quality improvements. - Familiarity with SaaS business metrics such as ARR, churn, retention, NRR, and product usage analytics. Now Qualifications: Education & Certifications: - Bachelor's degree in science, engineering, technology, mathematics, a related field, or an equivalent combination of relevant education and experience. - Relevant certifications in data, analytics, or cloud platforms (e.g., dbt, Snowflake, or a major cloud provider) a plus. (Preferred) We could also include "Relevant certifications ... a plus." as qualification. Now Skills: Core Competencies: - Excellent written and verbal communication, with the ability to influence and build consensus across functional teams, including without direct authority, from a data model review to an executive presentation. - Strong analytical and problem-solving skills paired with a strategic mindset that cuts through ambiguity and connects analytical work to broader company objectives. - Ownership and autonomy: identifies gaps, drives work to completion at a high quality bar, and grows data capability across the team through mentoring. Now Benefits: from "How we help you reach your best potential:" includes: - Named a 2025 Best