Business Intelligence Architect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes: description (intro), "IMPORTANT DETAILS" about compensation (market-based approach, bi-annual market reviews). Also "Why the job exists", "What Must Get Done", "What you know and have done", "How You Show Up", "When you know you're successful", "Benefits". Also location info (Boston, MA Office, Hudson, NH Office). Also mention "We use a market-based approach to compensation and have replaced annual salary reviews with bi-annual market reviews". No explicit salary numbers, so Pay section should not be included because no specific pay. Schedule not mentioned. Benefits are listed. So we can have sections: About the role (maybe intro), Responsibilities (What Must Get Done), Requirements (What you know and have done), Qualifications (maybe combine with Requirements? but we need separate headings only if content). Could have "Qualifications" for education/certifications. "Skills" for tools etc. "Benefits". Also maybe "Location". But location not in list of allowed headings; we could put location in a

under About the role or separate? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings only. We can include About the role (intro), Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "About the role" includes the introductory paragraphs and mission. Then Responsibilities: "What Must Get Done". Requirements: maybe "What you know and have done" (experience). Qualifications: education/degree/certifications. Skills: tools (Power BI, Snowflake, etc). Benefits: list. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO statements, navigation, cookie, etc. Also remove duplicated lines (EEO appears twice). Remove application instructions (the "IMPORTANT DETAILS We ask some important questions...") maybe that's not a section but could be part of About the role? It's about application process; we should remove application instructions. The instruction says remove application instructions. So we should drop that paragraph about "IMPORTANT DETAILS We ask some important questions..." and "Please don't miss that part..." etc. Also remove "Ready to learn more?" etc. We need to preserve all substantive information. So we need to keep the compensation detail: "We use a market-based approach to compensation and have replaced annual salary reviews with bi-annual market reviews". That's substantive; we could put it under Benefits? Or maybe under About the role? Since there is no Pay section, we can include it in About the role or Benefits. Probably About the role. We need to keep location info (Boston, MA Office, Hudson, NH Office). That's substantive; could be in About the role. We need to keep "Through your work, you'll contribute to growing our social mission: The Playmaker Project". That's substantive. We need to keep "Life is Good is an equal opportunity employer..." but that's boilerplate EEO; we should remove it per instruction: remove EEO/equal-opportunity boilerplate. So drop those lines. We need to keep "We save the robots for our operations team." maybe not needed; it's fluff but maybe considered boilerplate? It's not EEO but could be considered fluff; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line is not boilerplate; it's part of culture. Might keep? It's not essential but could be kept as part of About the role. Safer to keep. Now construct HTML. Structure:

About the role

... intro paragraphs ... include compensation detail, location, mission, etc.

Responsibilities

• ... each bullet from "What Must Get Done" ...

Requirements

• ... from "What you know and have done" (experience) ... maybe also include "You have a BS..."? Actually that's qualification. We'll split. Better: Requirements: experience (7+ years, hands-on, etc). Qualifications: education, certifications. Skills: tools. Let's parse. From "What you know and have done": - BS in Information Systems, Computer Science, Data Analytics, or related field - Known as go-to resource for defining BI strategy and building it, you ship it - Solid hands-on experience with Power BI (required) and Snowflake (required) - Experience with Tableau or similar BI tools is a welcome plus - Worked directly with ETL/ELT tools like Rivery and Fivetran, connecting sources, building pipelines, troubleshooting - Doer: write SQL, build models, wire up pipelines yourself; hands-on-keyboard role - Pulled data from SAP, ECC or S/4HANA (S/4 experience strong plus); know quirks - Experience with Shopify or marketing and social platforms is a plus - 7+ years of experience using BI tools to turn raw data into decisions, can describe specific results - Certification in Snowflake or Power BI is a plus We can split: Requirements: experience (7+ years, hands-on, etc). Qualifications: education/degree, certifications. Skills: tools (Power BI, Snowflake, Tableau, Rivery, Fivetran, SAP, Shopify, etc). Might also include "SQL, modeling". But we can include in Skills. Now "How You Show Up" and "When you know you're successful" could be part of Responsibilities or maybe a separate section like "Expectations". But not in allowed headings. Could incorporate into Responsibilities or About the role. Probably better to add to Responsibilities as soft skills. But we must not create sections with filler. We can include those points under Responsibilities as bullet points. Let's extract responsibilities from "What Must Get Done": - Design the data foundation. Pipelines (Rivery, Fivetran), models, and sources fit together cleanly so the business can ask new questions without rebuilding the plumbing every time - Connect SAP, Shopify, and other SaaS tools so the data tells one consistent story - Turn raw data into decisions. Reports, dashboards, and analyses are accurate, fast, and built around the question someone is actually trying to answer - Keep the lights on. Troubleshooting broken reports, answering data questions, and fixing issues in production, across both our current and future reporting environments - Make self-service real. The business can answer its own questions, with the right data, guardrails, and trust in the numbers - Hold the bar on data quality and security. Sensitive data is protected, lineage is documented, and the numbers reconcile to the system of record - Partner with leaders to set the BI roadmap, bringing informed recommendations on tools, patterns, and investments, not just opinions - Use AI as a standard part of your work to accelerate SQL, modeling, and exploration, verifying the logic carefully before anything reaches an executive - Spot patterns in data, usage, and reporting requests to get ahead of the questions the business is about to ask, and turn analysis into stories that help leaders act with confidence Also from "How You Show Up": - Start with the decision, not the dataset. "What will change because of this report?" comes before "what columns do we need?" - Design for trust. If users can't explain where a number came from, the work isn't done - Write SQL and models someone else will read tomorrow, because they will - Treat data security and privacy as part of the design, not an afterthought - Communicate clearly with people who don't live in BI. You translate business vision into technical decisions, and technical decisions back into terms the business understands - Add to the culture. You bring curiosity, optimism, and a real interest in the questions the business is actually trying to answer - Know and understand the impact of our mission and the Life is Good Superpowers - Skilled and comfortable working independently and as part of a team - Give and receive feedback thoughtfully and constructively - Known for having a positive impact on those around you And "When you know you're successful": - Business leaders make decisions with the data you provide, and they trust the numbers - New questions get good answers in days, not weeks, because the foundation is solid - The data tells one story across teams. Finance, ops, and sales numbers reconcile and stay reconciled - Raise the bar on how Life is Good uses data. Better tools, better patterns, fewer manual reports - Make the IT team stronger. People learn from you, lean on you, and want to work with you again on the next thing We can merge these into Responsibilities bullets. Now Benefits list: "We offer top quality Medical, Dental, Vision, Flexible Spending Accounts, Life, AD&D, Short and Long-Term Disability, 401(k) plan with a match, Paid Time Off (PTO), 10 paid holidays, Good Vibes Time (we pay you to volunteer for the non-profit cause of your choice) and Family Time. And we have dogs. Through your work, you'll contribute to growing our social mission: The Playmaker Project" Also compensation detail: "We use a market-based approach to compensation and have replaced annual salary reviews with bi-annual market reviews". Could be in About the role. Now location: Boston, MA Office and Hudson, NH Office details. Could be in About the role. Now craft HTML. We need to ensure no markdown fences, just raw HTML. Let's write:

  About the role

  Life is Good is investing in state-of-the-art software to empower decision‑making across the organization. As a Business Intelligence Architect you will design, build, and implement data‑driven solutions that turn raw data into actionable insights for sales, operations, finance, design, and other teams. You will work in our Boston, MA office (Fort Point) or our Hudson, NH office, contributing to the Playmaker Project social mission. We use a market‑based approach to compensation and have replaced annual salary reviews with bi‑annual market reviews.

  Responsibilities

  • Design the data foundation: build pipelines (Rivery, Fivetran), models, and source integrations so the business can ask new questions without rebuilding plumbing.
  • Connect SAP, Shopify, and other SaaS tools to provide a single, consistent data story.
  • Turn raw data into decisions: create accurate, fast reports, dashboards, and analyses aligned with the actual business question.
  • Keep the lights on: troubleshoot broken reports, answer data questions, and fix issues in production across current and future reporting environments.
  • Enable self‑service analytics: give the business the right data, guardrails, and trust to answer its own questions.
  • Uphold data quality and security: protect sensitive data, document lineage, and ensure numbers reconcile to the system of record.
  • Partner with leaders to set the BI roadmap, offering informed recommendations on tools, patterns, and investments.
  • Leverage AI to accelerate SQL, modeling, and exploration, verifying logic before anything reaches executives.
  • Spot patterns in data, usage, and reporting requests to anticipate future questions and turn analysis into confident‑action stories.
  • Start with the decision, not the dataset: ask “What will change because of this report?” before deciding on columns.
  • Design for trust: ensure users can explain where a number comes from.
  • Write SQL and models that are readable and maintainable for teammates.
  • Treat data security and privacy as a design priority, not an afterthought.