Senior BI Data Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting: It includes "Who We Are" description, then "Senior BI Data Engineer" title, then description, then "Job Description:", "Basic Requirements:", "Key Skills & Qualifications:", "Key Responsibilities:", "Preferred Qualifications:", "Certifications:", "Public Trust Clearance", "Work Location:", "EEO Statement", "Why Tria?", "California Consumer Privacy Act (CCPA)". Also mention hybrid schedule, onsite days. We need to decide sections: About the role (maybe from "Who We Are" and description?), Responsibilities (Key Responsibilities), Requirements (Basic Requirements), Qualifications (maybe combine Key Skills & Qualifications and Preferred Qualifications?), Skills (maybe part of qualifications), Benefits (they mention top-tier benefits package, but no specifics; they say "top-tier benefits package" but no detail; we should not create Benefits section unless posting actually states them. It says "We offer a top-tier benefits package to invest in your physical, mental, and financial health and wellness". That's a statement but not specific benefits. The rule: never emit a 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 the posting actually states them. Does "top-tier benefits package" count as stating benefits? It's vague but it's a statement that they offer benefits. However it's not specific. The rule says we should not create Benefits section unless posting actually states them. It does state they offer a top-tier benefits package, but not details. Might be considered stating benefits, albeit vague. Safer to include Benefits section with that statement? The rule says "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". "top-tier benefits package" is not exactly filler but still vague. Might be okay. However they also mention "We invest in its employees with a top-tier benefits package to support their physical, mental, and financial well-being." That's a statement of benefits. I'd include Benefits section with that sentence. Pay: Not mentioned. So no Pay section. Schedule: They mention hybrid work schedule, onsite 1-2 days per week in Windsor Mill, Maryland office. That's schedule info. So we can include Schedule section with that detail. We need to avoid duplication. Also need to include About the role: maybe combine "Who We Are" and job description summary. Use

About the role

then

with combined prose. Responsibilities:

Key Responsibilities

then

• each bullet. Requirements: Basic Requirements: list items. Qualifications/Skills: Could combine Key Skills & Qualifications and Preferred Qualifications? But we need separate sections maybe Skills and Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications and Skills separate. We need to decide what goes where. Qualifications could be education, experience, certifications. Skills could be technical skills. Let's extract. Basic Requirements includes: Ability to obtain US Federal Position of Trust clearance, reside in US, lived in US 3 of last 5 years, hybrid schedule, Bachelor's degree, 10+ years experience, experience with large-scale enterprise databases, hands-on experience with BI tool, strong SQL, Python, Agile/Jira/GitHub, analytical troubleshooting, ability to learn multiple BI etc. Key Skills & Qualifications includes many skill bullets similar to requirements but more skill-focused. Preferred Qualifications includes additional. Certifications: Relevant technical certifications preferred but not required. Thus we can have: - Requirements: Basic Requirements (clearance, residency, education, experience, schedule maybe? but schedule is separate). We'll include education, experience, clearance, residency. - Skills: Key Skills & Qualifications (technical skills). - Qualifications: maybe Preferred Qualifications + Certifications? Or we could treat Qualifications as education/experience/certifications. But we already used Requirements for education/experience. Might be overlapping. Let's think: The instruction list includes both Qualifications and Skills as possible sections. We can put Qualifications for education, certifications, clearance, etc. Skills for technical skills. Thus: Qualifications: Bachelor's degree, 10+ years experience, ability to obtain clearance, residency, etc. Skills: Strong SQL, Python, experience with BI tools, etc. We also need to include Preferred Qualifications maybe as part of Qualifications or Skills? Could add another subsection but we should avoid thin sections. Could incorporate Preferred Qualifications into Qualifications as additional preferred qualifications. We'll create:

  About the role

  ... combine Who We Are and job description summary.

  Responsibilities

  ... list from Key Responsibilities.

  Qualifications

  ... list education, experience, clearance, residency, preferred qualifications, certifications.

  Skills

  ... list technical skills from Key Skills & Qualifications.

  Benefits

  ... top-tier benefits package statement.

  Schedule

  ... hybrid schedule details.

  We must not repeat job title as heading. Ensure no boilerplate like EEO, CCPA, etc. We need to preserve all substantive information: That includes the "Who We Are" paragraphs, the job description, responsibilities, basic requirements, key skills, preferred qualifications, certifications, public trust clearance details, work location, why Tria? maybe not needed? It's somewhat fluff but still substantive? It's about company culture; could be considered part of About the role. We'll incorporate relevant parts. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove EEO Statement, CCPA, etc. Also remove "Why Tria?" maybe not needed but it's about culture; could be considered part of About the role. We'll include some of it if not boilerplate. It's not legal boilerplate; it's cultural description. We'll include. We must not include duplicated lines. Ensure we don't repeat same bullet. Let's extract content. Who We Are (first paragraph): "Tria Federal delivers digital services and technology solutions that support the health and safety of veterans, service members and civilians. For two decades, federal agencies have relied on Tria companies to advance their critical missions and modernize their systems, so that they can uphold their commitment to the American people. Today, we are pushing the boundaries of possibility through partnerships and investments in artificial intelligence and emerging technologies, developing solutions for the biggest challenges that government will face tomorrow. We are proud to employ and support military veterans who bring mission-first mindset, technical expertise, and leadership qualities that strengthen our work. Veterans, transitioning service members, and military spouses are strongly encouraged to apply." Then after title: "Tria Federal prides itself in leading the charge for innovation and transformation in the federal government space. We offer technological implementations and build customer-centric services that are simple, intuitive, and usable across multiple industries. By partnering with federal agencies, our specialized digital services are reimagining and reshaping the digital landscape to bring positive change for millions of Americans. Tria Federal (Tria) delivers mission-critical technical expertise and digital services informed by deep customer expertise to Health and Public Safety agencies across the federal sector. At Tria, we are a dynamic professional community driven by a mission rooted in service to colleagues, customers, and the community. Tria invests in its employees with a top-tier benefits package to support their physical, mental, and financial well-being." Then "Job Description: We are seeking a motivated and technically skilled BI Data Engineer to support the development, integration, analysis, and delivery of enterprise data and business intelligence solutions. This Senior-level role will work across data engineering, data analysis, and business intelligence functions to transform complex data into reliable, accessible, and actionable information. The ideal candidate will have strong SQL and Python skills, experience working with large-scale enterprise databases and data platforms, and hands-on experience with one or more major Business Intelligence (BI) tools such as Tableau, Amazon QuickSight, or Power BI. The candidate should be comfortable learning and working across different BI technologies based on evolving program and business needs. This role will collaborate with technical teams, analysts, and business stakeholders to understand data and reporting requirements, develop and optimize datasets and queries, support dashboards and reporting solutions, troubleshoot data issues, and help ensure the accuracy, quality, and performance of enterprise data solutions." Then "Basic Requirements:" list. Let's extract Basic Requirements bullet points: - Ability to obtain a U.S. Federal Position of Trust clearance designation. - Must reside in and be able to perform work in the United States. - Must have lived in the United States for three (3) of the last five (5) years. - This position follows a hybrid work schedule. The selected candidate must be able to work onsite in the Windsor Mill, Maryland office one (1) to two (2) days per week, with additional onsite attendance as required for customer meetings, workshops, planning sessions, and other program activities. - Bachelor’s degree in Computer Science, Information Systems, Engineering, Data Science, Analytics, Mathematics, Statistics, or a related technical/quantitative field, or equivalent relevant professional experience. - 10+ years of relevant professional experience in data engineering, business intelligence, data analytics, database development, or a related technical field. - Experience working with large-scale enterprise databases or data platforms such as Snowflake, Teradata, or similar technologies. - Hands-on experience with at least one major BI/reporting and visualization platform, such as MicroStrategy, Tableau, Amazon QuickSight, Power BI, or a comparable tool. - Strong SQL development experience, including querying, transforming, validating, and analyzing complex datasets. - Experience using Python for data analysis, transformation, scripting, or automation. - Experience working within Agile development environments and using tools such as Jira and GitHub. - Strong analytical, troubleshooting, and problem-solving skills. - Ability and willingness to learn and work across multiple BI, data, and reporting technologies based on program needs. Then "Key Skills & Qualifications:" list: - Strong SQL development and data analysis skills. - Experience working with large and complex enterprise datasets. - Experience with enterprise database and data warehouse platforms such as Snowflake, Teradata, or similar technologies. - Hands-on experience developing or supporting BI dashboards, reports, datasets, and analytics solutions using Tableau, Amazon QuickSight, Power BI, or similar platforms. - Proficiency with Python for data manipulation, analysis, transformation, scripting, and automation. - Understanding of data warehousing, relational databases, and data modeling concepts. - Familiarity with ETL/ELT processes, data integration, and data transformation. - Ability to analyze source data, identify data quality issues, and support data validation and reconciliation. - Experience with version control and collaborative development practices using Git/GitHub. - Experience tracking and managing technical work through Jira or similar Agile work management tools. - Ability to translate business and reporting requirements into technical data and BI solutions. - Strong written and verbal communication skills with the ability to collaborate effectively across technical and non-technical teams. - Ability to manage multiple priorities and adapt to evolving technologies and program requirements. - Demonstrated ability to work independently, take ownership of assigned responsibilities, and proactively identify and address issues without requiring continuous direction. Then "Preferred Qualifications:" list: - Experience with additional BI and data visualization tools, particularly Power BI. - Experience with Informatica or similar ETL/data integration platforms. - Experience with Hadoop, Hive, or similar big-data