Principal Data Visualization Engineer (Qlik)

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 content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: clearance, citizenship, etc? The clearance line is part of job posting; is it substantive? It says "Clearance: U.S. Citizenship is required. Active Public Trust in DHS or a component of DHS highly preferred". That is a requirement (citizenship). Should be included under Requirements or Qualifications. We'll include it. We need to preserve all substantive info. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Equal Opportunity Employer..." etc. Remove that. Also "Dev Technology Group operates in the following states: ..." maybe considered location info; could be part of Benefits? Not exactly. Might be considered location eligibility; could be included under Requirements? Might be considered "Work Locations". Not a defined heading; we could put under "About the role" maybe. But we have no heading for location. Could include under "About the role" as a paragraph. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay: there is salary range: "Our estimated salary range for this position is $140,000 - $170,000". So we should include Pay section. Schedule: not mentioned explicitly. There's "Flexible work schedules and telework options" under benefits. That's schedule info but it's under benefits. Could still include Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does mention flexible work schedules, so we could include Schedule section with that info. However they also mention flexible work schedules under benefits. Might be better to put under Benefits. But we can include Schedule if we have content. The posting says "Flexible work schedules and telework options, including remote work availability for eligible projects". That's schedule info. So we can include Schedule section. Benefits: they list many benefits: generous time-off policy, flexible work schedules, career development opportunities, industry-leading benefits including health plans, 401K matching, social events, community engagement. So we include Benefits. Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. About the role: maybe a brief description: "You will be working with an established team to create meaningful dashboards that support our customer's mission-critical decision-making. The environment is complex, with large datasets both in depth and breadth. Your role will always include learning something new, whether a tool or a new data domain." Responsibilities: could be the bullet list of duties: "You will be working with an established team to create meaningful dashboards..." but that's more description. Could list responsibilities: create dashboards, work with team, learn new tools, etc. Might be overlapping. We'll extract from "What You'll Be Doing:" which is basically responsibilities. So we can put that as Responsibilities. Requirements: Required Education, Experience, and Skills: Bachelor's degree plus 7+ years overall technical experience, including analysis or development roles with databases, data integration, data mining, big data, data visualization; at least three years developing dashboards using PowerBI, Qlik Sense, or Tableau; experience in data modeling, scripting, and ETL development within Qlik environments; strong SQL experience; good communication skills; ability to learn new tools quickly; ability and desire to work with other program staff and customers; excellent diplomacy and communication skills; also citizenship requirement. Qualifications: Preferred Education, Experience, and Skills: Demonstrated project experience in data visualization and analysis using Qlik Sense specifically; competence in Python, Spark, PySpark; experience working with federal government clients; experience with AWS cloud services. Skills: Could combine both required and preferred? But we already have Requirements and Qualifications sections. Skills maybe separate list of technical skills: PowerBI, Qlik Sense, Tableau, data modeling, scripting, ETL, SQL, communication, Python, Spark, PySpark, AWS, etc. However we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one "Requirements" section with subpoints? But headings are fixed; we must use those headings if we have content. We could put required under Requirements, preferred under Qualifications. Skills maybe not needed if covered. But we need to decide if we have enough content for Skills separate. Could list technical skills: PowerBI, Qlik Sense, Tableau, SQL, data modeling, scripting, ETL, Python, Spark, PySpark, AWS. That is substantive. We'll include Skills. Benefits: as described. Pay: salary range. Schedule: flexible work schedules and telework options. Now we need to output HTML fragment only, no /. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to ensure we don't include placeholders like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract details. From posting: - Clearance: U.S. Citizenship required. Active Public Trust in DHS or component highly preferred. - What You'll Be Doing: You will be working with an established team to create meaningful dashboards that support our customer's mission-critical decision-making. The environment is complex, with large datasets both in depth and breadth. Your role will always include learning something new, whether a tool or a new data domain. - Required Education, Experience, and Skills: * Bachelor's degree plus 7+ years of overall technical experience, including analysis or development roles with databases, data integration, data mining, big data, data visualization * At least three years developing dashboards using data visualization technologies, such as PowerBI, Qlik Sense, or Tableau * Experience in data modeling, scripting, and ETL development within Qlik environments * Strong SQL experience working with relational databases and large datasets * Good communication skills, particularly in requirements definition and documentation of visualization artifacts * Ability to learn new tools quickly as needed to provide new ideas for solving problems * Ability and desire to work with other program staff and customers to reach design decisions within given constraints * Excellent diplomacy and communication skills with both clients and technical staff - Preferred Education, Experience, and Skills: * Demonstrated project experience in data visualization and analysis using Qlik Sense specifically, highly preferred * Competence in Python, Spark, and PySpark * Experience working with federal government clients * Experience with AWS cloud services - Salary: "Our estimated salary range for this position is $140,000 - $170,000, this presented salary range is not a guarantee of compensation or salary. Offered salary is based on experience, geographic location, and possibly contractual requirements as appropriate to the role. *Salary could fall outside of this range." - Who We Are: description of Dev Technology, benefits list: * Generous and flexible time-off policy * Flexible work schedules and telework options, including remote work availability for eligible projects * Career development opportunities including a mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, and paid training opportunities * Industry-leading benefits including a choice of two health plans that include dental and vision, flexible spending account, commuter benefits, life insurance, and more * 401K matching with a 5% matching contribution * Regular team and company social events including our annual party, happy hours, fitness challenges, and more * A focus on community engagement including company wide support activities, employer match for donations, and time off for volunteer efforts - Locations: list of states where Dev Technology operates. We need to include location? Not a defined heading. Could be part of About the role or Benefits? Might be considered "Work Locations". Not in headings list. Could be omitted? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must include location info somewhere. We could add a paragraph under About the role or maybe under Benefits as "Work Locations". Since we have no heading for location, we could add a

  under About the role that includes location info. Or we could create a section "About the role" and include location as part of that paragraph. We must not create new headings not in list. So we will embed location info in a paragraph under About the role. Now we need to avoid duplication: The "Flexible work schedules and telework options" appears both in Benefits and could be used for Schedule section. We'll keep it in Benefits and also maybe mention in Schedule? To avoid duplication, we could put schedule info only in Schedule section and not duplicate in Benefits. But Benefits also includes many other items; we could keep schedule info in Schedule and remove from Benefits to avoid duplication. However the Benefits list includes that as a bullet; if we remove it, we lose that benefit detail. But we could keep it in Benefits and also have Schedule section referencing it? That would be duplication. Better to keep schedule info under Schedule and not duplicate in Benefits; we can still mention other benefits. Thus Benefits section will exclude flexible work schedules (since moved to Schedule). We'll keep other benefits. Now we need to decide what goes into Responsibilities vs About the role. The "What You'll Be Doing:" is responsibilities. About the role could be a brief overview of the team and mission? The posting doesn't have a separate "About the role" besides that. We could treat the "What You'll Be Doing:" as Responsibilities, and maybe About the role could be a short description of the team and mission: "You will be working with an established team to create meaningful dashboards that support our customer's mission-critical decision-making. The environment is complex, with large datasets both in depth and breadth. Your role will always include learning something new, whether a tool or a new data domain." That's actually the same as responsibilities. Might be okay to have both sections with similar content? Might be considered duplication. Perhaps we can put the descriptive paragraph under About the role, and then Responsibilities as a bullet list of duties derived from that paragraph. But the paragraph already covers duties. Could split: About the role: overview of team and mission; Responsibilities: bullet list of specific duties (create dashboards, work with team, learn new tools, etc). However the paragraph already includes those. We could still create bullet list: - Work with established team to create meaningful dashboards supporting mission-critical decision-making. - Operate in complex environment with large datasets. - Continuously learn new tools or data domains. That is essentially same but bulletized. We need to avoid filler. It's okay. Now Requirements: list of required items as bullet list. Qualifications: list of preferred items as bullet list. Skills: list of technical skills: PowerBI, Qlik Sense, Tableau, data modeling, scripting, ETL, SQL, communication, Python, Spark, PySpark, AWS. Could also include "data visualization technologies". We'll bullet. Benefits: bullet list of benefits excluding flexible work schedules (since moved to Schedule). Include: generous and flexible time-off policy; career development opportunities (mentorship program, technical and management training through Dev University, hands-on learning through DevLab, tuition reimbursement, paid training opportunities); industry-leading benefits (choice of two health plans with dental and vision, flexible spending account, commuter benefits, life insurance, etc); 401K matching with 5% contribution; regular team and company social events (annual party, happy hours, fitness challenges); focus on community engagement (company wide support activities, employer match for donations, time off for volunteer efforts). Also maybe mention "Dev Technology is a growing IT company..." but that's more about company; could be in About the role. Schedule: bullet list: flexible work schedules and telework options,