Data System Administrator

We need to output HTML fragment with sections: About the role? The posting includes intro about benefits, mission, then description of role. We need headings for sections that have real content: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must include only sections with real specific content. Let's parse content: - Benefits: "Great benefits. Competitive pay." then bullet list: "A flexible hybrid work schedule (three days in the office, two days’ work from home) Full medical, dental, and vision coverage for both teammates AND family members Competitive pay and performance incentives A fun, mission-focused, and collaborative team environment". So we have benefits: flexible hybrid schedule, medical/dental/vision, competitive pay and performance incentives, fun mission-focused collaborative team environment. Also "Great benefits. Competitive pay." is generic but we have specifics. - Pay: "Competitive pay and performance incentives" is mentioned under benefits. Could be separate Pay section? The instruction: include Pay section only if posting actually states them. It does state competitive pay and performance incentives. So we can have Pay section with that detail. - Schedule: "A flexible hybrid work schedule (three days in the office, two days’ work from home)" is schedule detail. So Schedule section. - Responsibilities: DUTIES & RESPONSIBILITIES list many items. So we can have Responsibilities section with ul. - Requirements: There's EXPERIENCE Requirements, EDUCATION Requirements, CERTIFICATIONS & LICENSURE Requirements. Also KNOWLEDGE, SKILLS, & ABILITIES (skills). So we can have Requirements (maybe combine experience and education) and Skills (knowledge, skills, abilities). Qualifications maybe similar to requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to use. We have "About the role": we have a paragraph describing role: "The Wounded Warrior Project (WWP) Data Systems Administrator supports the administration, security, and operational management of WWP's Enterprise Data Warehouse (EDW) environment. This role is responsible for user provisioning, access management, system configuration, and day-to-day administration of data and analytics platforms to ensure secure, reliable, and efficient access to enterprise data resources. The Data Systems Administrator works closely with the Data Engineer, Analytics, and Data Governance teams as well as business stakeholders to support data platform operations, maintain system integrity, and promote effective data access and utilization across the organization." That's good for About the role. Responsibilities: DUTIES & RESPONSIBILITIES list. Requirements: Could combine EXPERIENCE Requirements and EDUCATION Requirements. Also CERTIFICATIONS & LICENSURE Requirements (none). So we can have Requirements section with experience and education. Skills: KNOWLEDGE, SKILLS, & ABILITIES list. Benefits: list as above. Pay: "Competitive pay and performance incentives". Could be separate. Schedule: "A flexible hybrid work schedule (three days in the office, two days’ work from home)". Could be separate. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam-warning, etc. Also remove navigation/cookie/legal. At end there is EEO statement and note about search firms. Remove those. We must preserve all substantive information. So we need to include all duties, responsibilities, knowledge, skills, abilities, experience, education, benefits, pay, schedule. We must not invent or summarize away detail. Must preserve all specifics. We need to format as HTML fragment: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which content goes in

  vs

  . For prose paragraphs like About the role, we can use

  . For lists like duties, responsibilities, requirements, skills, benefits, we use

  • . For Pay and Schedule maybe just a

    (since it's a single line). But could also be

    with single li; but instruction: use
    • for any list of duties/requirements/benefits. Pay and Schedule are not lists but single items; we can use

      . We must not emit a heading followed by filler/placeholder text. All sections have real content. Let's extract details precisely. **About the role** paragraph: The two sentences: "The Wounded Warrior Project (WWP) Data Systems Administrator supports the administration, security, and operational management of WWP's Enterprise Data Warehouse (EDW) environment. This role is responsible for user provisioning, access management, system configuration, and day-to-day administration of data and analytics platforms to ensure secure, reliable, and efficient access to enterprise data resources. The Data Systems Administrator works closely with the Data Engineer, Analytics, and Data Governance teams as well as business stakeholders to support data platform operations, maintain system integrity, and promote effective data access and utilization across the organization." That's three sentences. We'll put in

      . **Responsibilities**: The list after "DUTIES & RESPONSIBILITIES". Let's extract each bullet (they are separated by periods but not bullet). We need to create

    • for each duty. The text: "Create, configure, modify, and manage user accounts, security roles, and permissions across enterprise data platforms. Provision and deprovision access to Enterprise Data Warehouse (EDW) resources in accordance with established security and governance policies. Monitor user access and permissions to ensure compliance with organizational standards and governance requirements. Assist with platform configuration, environment management, and administrative functions that support data platform operations. Support the day-to-day administration and operations of the EDW environment. Monitor system health, platform performance, and data-processing activities to identify and address operational issues. Troubleshoot user access issues, data availability concerns, and platform-related incidents. Support platform maintenance, upgrades, patches, and enhancement activities. Support data ingestion, integration, and data-processing activities across enterprise platforms. Assist with ETL/ELT testing, monitoring, validation, and operational support activities. Monitor and maintain data pipeline workflows and orchestration schedules. Administer security groups, roles, and access controls in accordance with governance and security standards. Support access reviews, audits, and compliance-related activities. Maintain documentation related to user provisioning, security administration, and operational procedures. Adhere to established data governance, privacy, and compliance requirements. Document system configurations, procedures, operational processes, and support activities. Collaborate with data engineers, business analysts, data governance teams, and business stakeholders to support effective platform operations. Attend and actively participate in required training and/or meetings, including but not limited to New Teammate Orientation, WWP Cares, ASIST Suicide Prevention training, Leadership training, culture/team based training, or departmental huddles. Other related duties as assigned." We'll make each a
    • . **Requirements**: Combine experience and education. Experience Requirements: "Two years of experience supporting or administering enterprise databases, data platforms, analytics systems, or Enterprise Data Warehouse environments. Experience troubleshooting system access, data availability, platform performance, or other technical issues." Preferences: "Experience supporting cloud-based data platforms, preferably Snowflake. Experience monitoring or supporting ETL/ELT processes, data pipelines, or workflow orchestration tools. Experience supporting user provisioning, access management, security administration, or operational support activities." Education Requirements: "Bachelor’s degree in computer science, information systems, or related field. Equivalent combination of applicable education, training, certification, and experience may be considered in lieu of degree." Preferences: None. Certifications & Licensure: Requirements None. Preferences None. So we can omit as no content. Thus Requirements section will have experience and education (maybe separate subheadings? But we only allowed headings list; we could just put all in a
      with items. Might be okay to separate with

      headings inside? But instruction: Use

      for section headings only. Inside we can use

      for prose. Could separate experience and education with

      headings? Not required. We'll just list items. We need to preserve all specifics: include both required and preferred experience. Should we differentiate? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include both required and preferred experience. We could label them within

      like "Required: Two years of experience..." and "Preferred: Experience supporting cloud-based data platforms, preferably Snowflake." That's okay. Similarly for education: required Bachelor's degree...; preferred none. We'll include as list items. **Skills**: KNOWLEDGE, SKILLS, & ABILITIES list. Let's extract each item: "Fundamental knowledge of database technologies, SQL, and relational database concepts. Understanding of EDW concepts, data architecture, and data lifecycle management. Familiarity with cloud-based data platforms, preferably Snowflake. Understanding of data integration, ETL/ELT processes, orchestration concepts, and data pipeline operations. Familiarity with dimensional data modeling concepts, including fact and dimension tables, star schema design, and data warehousing best practices. Understanding of user provisioning, access controls, security roles, and governance practices within enterprise data platforms. Strong analytical and problem-solving skills with the ability to identify, troubleshoot, and resolve technical issues. Attention to detail and commitment to data accuracy, quality, and security. Ability to learn new technologies, platforms, and processes quickly. Strong written and verbal communication skills. Ability to create and maintain technical documentation, procedures, and operational records. Strong customer service orientation with a focus on supporting internal users and stakeholders. Ability to collaborate effectively across technical and business teams. Commitment to security, compliance, governance, and operational excellence. Unequivocal commitment to the highest standards of personal and business ethics and conduct. Mission-driven, guided by core values, and a pleasure to work with." We'll make each a

      . **Benefits**: list: "A flexible hybrid work schedule (three days in the office, two days’ work from home) Full medical, dental, and vision coverage for both teammates AND family members Competitive pay and performance incentives A fun, mission-focused, and collaborative team environment" Also earlier "Great benefits. Competitive pay." but that's generic; we already have specifics. We'll make each a

      . **Pay**: "Competitive pay and performance incentives". Could be a

      . But note we already included that in benefits; but we can still have Pay section with that detail. However we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However the benefits already includes that line; if we also have Pay section repeating same line, it's duplication but still preserving info. Might be okay but could be considered redundant. The instruction: Prefer a few substantive sections over many thin ones. Having both Benefits and Pay may be thin. But we have schedule separate as well. Could combine Pay and Schedule into Benefits? But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It does not forbid having overlapping content. However to avoid thin sections, maybe we should not create separate Pay and Schedule sections if they are already covered under Benefits. But the instruction list includes Pay and Schedule as possible headings; we should include them only if posting has real specific content for them. It does have specific content: "Competitive pay and performance incentives" and "A flexible hybrid work schedule (three days in the office, two days’ work from home)". Those are specific. So we should include them. Even if they also appear in benefits list, it's okay to have them both; but we could avoid duplication by not including them in Benefits list. However the benefits list explicitly includes those items; if we remove them from Benefits, we would be omitting substantive information