Data Administrator

We need to output HTML fragment with sections: About the role? The posting includes job description, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We need to include sections only if there is real specific content. We have: - Job description: includes description of role, responsibilities. Could be "About the role" or "Responsibilities". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We need to preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "If you're currently employed by the State of Nebraska..." that's application instruction. Also remove "Equal Opportunity Statement". Also remove "Benefits We offer..." maybe keep benefits but need specific content. The benefits section says: "We offer a comprehensive package of pay, benefits, paid time off, retirement and professional development opportunities..." plus link. That's somewhat generic but still mentions specific benefits: pay, benefits, paid time off, retirement, professional development. It's not placeholder like "commensurate with experience". It's actual description. So we can include Benefits section. Pay: The posting includes "Hiring Rate $36.061". That's a specific pay rate. So we can include Pay section with that. Schedule: It says "Position is full-time/permanent located on-site in Lincoln, NE." Also "No remote work." So schedule: full-time, permanent, on-site. So we can include Schedule section. We also have location: Lincoln, NE. Could be included in About the role or maybe as metadata. But we should not repeat job title as heading. We can include location in About the role paragraph. We need to include sections: About the role (maybe summarizing description), Responsibilities (list of examples of work), Requirements/Qualifications (maybe combine), Knowledge, Skills, & Abilities (maybe Skills), Benefits, Pay, Schedule. We must not invent or summarize away detail. Must preserve all substantive information. So we need to include all details from the posting. Let's extract: - Hiring Agency: Health & Human Services - Agency 25 - Location: Lincoln, NE - Hiring Rate $36.061 - Job Posting JR2026-00029245 - Data Administrator (Open) - Applications No Longer Accepted On (If no date is displayed, job is posted as open until closed): 09-24-2026 - Job Description: Nebraska Department of Health and Human Services is seeking an experienced Data Administrator with strong expertise in Azure cloud administration and security to join our IS&T team! This role is responsible for managing enterprise data platforms, cataloging tools, and analytics environments. The ideal candidate is a seasoned engineer with hands on experience supporting complex, cloud based data ecosystems. Healthcare experience is preferred. Position is full-time/permanent located on-site in Lincoln, NE. The Nebraska Department of Health and Human Services does not sponsor STEM (form i-983) or non-immigrant work visas for this position. - Examples of Work (list): - Administer, secure, and optimize Azure cloud resources, including identity, access, networking, and data services. - Support and enhance Azure Databricks environments, ensuring stable workflows, strong governance, and adherence to engineering best practices. - Implement and maintain CI/CD pipelines and infrastructure‑as‑code (IaC) solutions to manage data platform deployments and configurations. - Monitor platform usage, troubleshoot issues, and ensure compliance with organizational and industry security standards. - Manage and maintain enterprise data cataloging platforms such as Collibra or comparable tools. - Establish and uphold data governance processes, metadata standards, and documentation across the organization. - Collaborate with analytics and engineering teams to support Power BI environments (preferred). - Work with Snowflake or other cloud data warehouse platforms as needed (preferred). - Requirements/Qualifications: Minimum Qualifications: Associate Degree in Computer Science or related field of study and three years related experience or A bachelor’s degree or equivalent in computer science, information systems, mathematics, engineering or other related field and two years of experience. Experience may include application programming, software installation and software maintenance, including systems programming, online programming, database design, analysis and programming using IFS and/or SQL/DS and database administration. Any equivalent combination of education and experience will be considered. Preferred Qualifications: Bachelor's or associate degree preferred but not required with equivalent professional experience. Professional certifications are strongly valued, particularly Azure Administrator, Azure Security, Azure Solutions Architect, or Azure Data Engineer certifications. Proven experience administering Azure cloud environments with emphasis on security, policy enforcement, and data platform management. Strong experience implementing CI/CD pipelines and infrastructure‑as‑code solutions (such as Terraform, Ansible or Azure Bicep). Practical experience with at least one enterprise data cataloging or governance tool. Hands‑on experience with Azure Databricks or similar cloud‑based data engineering platforms. Healthcare industry experience is preferred. Other: Located at the Nebraska State Office Building in Lincoln. No remote work. - Knowledge, Skills, & Abilities: Solid understanding of data governance, metadata management, and data lifecycle processes. Ability to work independently, manage multiple priorities, and collaborate effectively with data, engineering, and analytics teams. Excellent communication and documentation abilities. - Benefits: We offer a comprehensive package of pay, benefits, paid time off, retirement and professional development opportunities to help you get the most out of your career and life. Your paycheck is just part of your total compensation. Check out all that the State of Nebraska has to offer! Benefit eligibility may vary by position, agency and employment status. For more information on benefits, please visit: https://statejobs.nebraska.gov/index.html#benefits - Pay: Hiring Rate $36.061 - Schedule: Position is full-time/permanent located on-site in Lincoln, NE. No remote work. We need to remove boilerplate: EEO statement, application instructions (If you're currently employed...), maybe also the "Applications No Longer Accepted On" date? That's metadata but not boilerplate; it's a date. Should we keep? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph with metadata like Job ID, posting date, etc. But we should not make a heading for it. So we can include a

at top with that info. We must not repeat the job title as a heading. So we will not have

Data Administrator

. We'll have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide whether to split Requirements and Qualifications separate or combine. The instruction gives examples of headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections if there is content. The posting has Minimum Qualifications and Preferred Qualifications. Could treat Requirements as Minimum Qualifications, Qualifications as Preferred Qualifications. Or combine. Safer to have both. We also have Knowledge, Skills, & Abilities -> Skills section. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

Job ID: JR2026-00029245 | Posting Date: 09-24-2026 | Agency: Health & Human Services - Agency 25 | Location: Lincoln, NE

Then

About the role

with paragraph(s) describing role: Nebraska Department of Health and Human Services is seeking an experienced Data Administrator with strong expertise in Azure cloud administration and security to join our IS&T team! This role is responsible for managing enterprise data platforms, cataloging tools, and analytics environments. The ideal candidate is a seasoned engineer with hands on experience supporting complex, cloud based data ecosystems. Healthcare experience is preferred. Position is full-time/permanent located on-site in Lincoln, NE. The Nebraska Department of Health and Human Services does not sponsor STEM (form i-983) or non-immigrant work visas for this position. Then

Responsibilities

with

• each example. Then

  Requirements

  with paragraph for Minimum Qualifications. Then

  Qualifications

  with paragraph for Preferred Qualifications. Then

  Skills

  with
  • for Knowledge, Skills, & Abilities. Then

    Benefits

    with paragraph describing benefits. Then

    Pay

    with paragraph: Hiring Rate $36.061. Then

    Schedule

    with paragraph: Position is full-time/permanent located on-site in Lincoln, NE. No remote work. We must ensure we don't include any boilerplate like EEO statement, application instructions, etc. Check for duplicated lines: The posting includes "Position is full-time/permanent located on-site in Lincoln, NE." appears both in About the role and maybe elsewhere. We'll include it only once in About the role and Schedule maybe duplicate but it's okay to repeat? The instruction: remove duplicated lines. So we should avoid repeating same sentence. We can mention full-time/permanent in About the role, and Schedule can just say "On-site, no remote work." But we need to preserve schedule info: full-time/permanent, on-site, no remote work. So we can phrase Schedule: "Full-time, permanent position; on-site in Lincoln, NE; no remote work." That avoids duplication. Similarly, About the role can mention "Position is full-time/permanent located on-site in Lincoln, NE." but that duplicates schedule. To avoid duplication, we could keep About the role without schedule details, and put schedule details in Schedule section. But About the role still needs to convey role description; we can omit schedule from there. Let's see: The About the role paragraph currently includes that sentence. We can remove it to avoid duplication. The instruction: remove duplicated lines. So better to not repeat. Thus About the role: "Nebraska Department of Health and Human Services is seeking an experienced Data Administrator with strong expertise in Azure cloud administration and security to join our IS&T team! This role is responsible for managing enterprise data platforms, cataloging tools, and analytics environments. The ideal candidate is a seasoned engineer with hands on experience supporting complex, cloud based data ecosystems. Healthcare experience is preferred. The Nebraska Department of Health and Human Services does not sponsor STEM (form i-983) or non-immigrant work visas for this position." That covers role description without schedule. Now Schedule section: "Full-time, permanent position; on-site in Lincoln, NE; no remote work." Now Benefits: we keep as is. Now Pay: "Hiring Rate $36.061" Now we need to ensure we didn't miss any substantive info: The "Other: Located at the Nebraska State Office Building in Lincoln. No remote work." That's location detail; we already have location in metadata and schedule. The "Located at the Nebraska State Office Building in Lincoln." is more specific than just Lincoln, NE. Should we include that? It's substantive. We could add to About the role or Schedule. Since schedule already mentions on-site in Lincoln, NE, we could add "Located at the Nebraska State Office Building in Lincoln." to About the role or maybe a separate line. Let's add to About the role after healthcare experience sentence: "The position is located at the Nebraska State Office Building in Lincoln." That adds detail. Thus About the role: includes location. Now schedule: "Full-time, permanent position; no remote work." (since location already mentioned). Or we can keep location in schedule as well but that duplicates. Better to keep location only in About the role. Thus schedule: "Full-time, permanent position; no remote work."