Junior Data Engineer / Active Secret

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, etc. Must preserve all substantive info. We need to parse the posting. First, there is an "About Peraton" intro – that's company description, maybe not needed? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The "About Peraton" is not a required heading; we could include as a paragraph maybe under a generic "About the company"? But not required. The instruction says we should include sections only when posting has real specific content for it. The headings list includes "About the role". So we need an About the role section. Also Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. Let's parse: - About The Role: paragraph describing role, location, etc. Then bullet list of duties: "In this role, you will:" followed by many items. Those are responsibilities. Thus we can put About the role: maybe a short paragraph summarizing role (location, etc). Then Responsibilities: list of duties. - Qualifications: there is a "Qualifications" heading in the posting with Minimum Requirements and Preferred/Desired. Also there is a "Details" section with Target Salary Range and Benefits Statement. Thus we need sections: - About the role: include location, flexible telework, support CEDN, etc. - Responsibilities: list of duties from "In this role, you will:" items. - Requirements: maybe the minimum requirements? Could be "Minimum Requirements:" bullet list. - Qualifications: maybe the preferred/desired? Or we could combine. But we need separate sections for Requirements and Qualifications as per instruction. We'll interpret Requirements as the mandatory qualifications (minimum). Qualifications as preferred/desired. - Skills: maybe we can extract skills from the qualifications (Python, SQL, etc). Could be a separate Skills section. - Benefits: from Benefits Statement. - Pay: from Target Salary Range. - Schedule: maybe location and flexible telework? Not explicit schedule. There's no schedule info like full-time, part-time, shift. So we should not create Schedule section unless posting actually states them. It does not. So omit Schedule. We must not include placeholder text like "commensurate with experience". The salary range is given, so we can include Pay. We must not include boilerplate like EEO, application statements, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting that are substantive. Thus we need to include: - About Peraton description? Might be considered company overview; not required but could be included as a paragraph before sections? The instruction says output only HTML fragment; we can include any content as long as we follow heading rules. There's no prohibition against extra paragraphs not under headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. It doesn't forbid other paragraphs outside headings, but likely they expect sections only. Safer to put company description under a heading? Not in list. Could drop it? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep the About Peraton paragraph. Where to put it? Could be a

  before any headings. That's okay. Similarly, "Program Overview" paragraph: "Encompasses technical, engineering, data analytics, cyber security, management, operational, logistical, and administrative support for Bureau of Diplomatic Security, Cyber and Technology Security Directorate in three key offices/functional areas: Cyber Monitoring and Operations, Cyber Threat and Investigations, and Technology Innovation and Engineering State." That's substantive; we should keep it. Thus we will have:

  About Peraton ...

  Program Overview ...

  Then

  About the role

  with paragraph summarizing role: location, flexible telework, support CEDN, etc. Then

  Responsibilities

  with
  • each duty. Then

    Requirements

    with
    • minimum requirements. Then

      Qualifications

      with
      • preferred/desired. Then

        Skills

        maybe list of specific skills: Python, SQL, etc. Could also be under Qualifications. But we have separate Skills section; we can extract skills from qualifications: "Foundational experience with data engineering, data integration, ETL/ELT processes, application integration, or log-management technologies. Working knowledge of Python and SQL. Familiarity with structured and semi-structured data formats, including JSON, CSV, XML, syslog, and API-delivered data. Understanding of databases, data lakes, data pipelines, schemas, metadata, and data lifecycle concepts. Basic knowledge of cloud computing and cloud storage services. Ability to analyze technical documentation and translate system requirements into actionable data-integration tasks. Ability to document configurations, testing results, data mappings, technical procedures, and operational issues clearly. Strong analytical, troubleshooting, organizational, and communication skills. Ability to work collaboratively while managing multiple assignments and established deadlines. Ability to learn new platforms and technologies through hands-on work, formal training, and mentorship." That's a mix of skills and abilities. We could put them in Skills. But we also have "Preferred/Desired" list with many items; those could also be skills. However we already have Qualifications for preferred/desired. Might be overlapping. To avoid duplication, we could treat Qualifications as the preferred/desired list, and Skills as the core technical skills (Python, SQL, etc). But the instruction says preserve all substantive information; we must not lose any. So we need to include both minimum requirements and preferred/desired somewhere. We have Requirements (minimum) and Qualifications (preferred/desired). That covers both. Then Skills could be omitted or we could combine. But we need to decide whether to include Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So we might avoid Skills if its content overlaps with Requirements/Qualifications. However the list of skills is distinct from requirements (which are degree/experience/certifications). The skills list includes technical abilities. It's substantive and not covered elsewhere. So we should include Skills. Thus: - Requirements: Minimum Requirements (degree/experience, certifications, foundational experience, etc.) - Qualifications: Preferred/Desired items (experience with Cribl, Databricks, Azure, Splunk, etc., certifications, federal experience, etc.) - Skills: Technical skills list (Python, SQL, data formats, etc.) plus abilities (analytical, troubleshooting, etc.) maybe. But we must ensure we don't duplicate content. Let's extract exact text. Minimum Requirements paragraph: "Minimum Requirements: Bachelor's degree in computer science, information systems, data science, cybersecurity, engineering, or a related technical field and 1-2 years of experience. Four additional years of relevant experience may be substituted in lieu of a degree. Possess or obtain prior to start, and maintain one of the following certifications:CCNA Security, CEH, CISSP, CySA+, GICSP, GSEC, Security+ CE, CND, or SSCPFoundational experience with data engineering, data integration, ETL/ELT processes, application integration, or log-management technologies. Working knowledge of Python and SQL. Familiarity with structured and semi-structured data formats, including JSON, CSV, XML, syslog, and API-delivered data. Understanding of databases, data lakes, data pipelines, schemas, metadata, and data lifecycle concepts. Basic knowledge of cloud computing and cloud storage services. Ability to analyze technical documentation and translate system requirements into actionable data-integration tasks. Ability to document configurations, testing results, data mappings, technical procedures, and operational issues clearly. Strong analytical, troubleshooting, organizational, and communication skills. Ability to work collaboratively while managing multiple assignments and established deadlines. Ability to learn new platforms and technologies through hands-on work, formal training, and mentorship. U.S. citizenship required.An active Secret security clearance, with the ability to obtain a final Top Secret clearance." Note there is missing space after some certifications list: "CCNA Security, CEH, CISSP, CySA+, GICSP, GSEC, Security+ CE, CND, or SSCPFoundational". We'll keep as is. Preferred/Desired list: "Preferred/Desired: Experience or training with Cribl Stream, Cribl Edge, or a comparable log-routing and observability pipeline platform. Experience or training with Databricks, Apache Spark, Delta Lake, notebooks, or lakehouse architectures. Familiarity with Microsoft Azure, Azure Data Lake Storage, or similar clsroud data services. Exposure to Splunk, ServiceNow, Power BI, Tableau, SIEM, SOAR, or other cybersecurity analytics platforms. Familiarity with Git, CI/CD pipelines, Infrastructure as Code, or DevSecOps practices. Understanding of security telemetry from firewalls, endpoints, DNS, authentication services, cloud platforms, email, VPNs, proxies, NetFlow, or packet-capture systems. Familiarity with data normalization models, data-quality controls, and role-based access controls. Experience supporting data-source onboarding, API integrations, or high-volume event-processing environments. Databricks Certified Data Engineer Associate, Cribl Certified User, Microsoft Azure certification, or the ability to obtain a relevant certification within six months of hire. Experience supporting the Federal Government, Department of Defense, intelligence community, or another regulated environment." Now Skills: we could take the technical skills from Minimum Requirements (the part after certifications) but that's already in Requirements. To avoid duplication, maybe we put the technical skills in Skills, and keep Requirements focused on degree/experience/certifications/clearance/citizenship. Let's split: Requirements: degree/experience, certifications, US citizenship, Secret clearance ability to obtain TS. Skills: Foundational experience with data engineering, data integration, ETL/ELT processes, application integration, or log-management technologies. Working knowledge of Python and SQL. Familiarity with structured and semi-structured data formats, including JSON, CSV, XML, syslog, and API-delivered data. Understanding of databases, data lakes, data pipelines, schemas, metadata, and data lifecycle concepts. Basic knowledge of cloud computing and cloud storage services. Ability to analyze technical documentation and translate system requirements into actionable data-integration tasks. Ability to document configurations, testing results, data mappings, technical procedures, and operational issues clearly. Strong analytical, troubleshooting, organizational, and communication skills. Ability to work collaboratively while managing multiple assignments and established deadlines. Ability to learn new platforms and technologies through hands-on work, formal training, and mentorship. That seems reasonable. Now About the role paragraph: from "About The Role Peraton is seeking a Junior Data Engineer to join its Department of State (DoS) Diplomatic Security Cyber Mission (DSCM) program. Location: Beltsville, MD or Washington DC; Flexible for occasional telework; candidate must be local to the work location. This position will support the Cyber Event Data Node (CEDN), a centralized cloud-based data platform that collects, processes, enriches, normalizes, stores, and distributes cybersecurity data for operational and analytical use. Peraton's DSCM program provides technical, engineering, data analytics, cybersecurity, management, operational, logistical, and administrative support to protect the Department's global infrastructure, systems, information, and mobile devices from cyber risks and threats." We can keep that as prose. Now Responsibilities: list from "In this role, you will:" items. Let's extract each bullet: - Support onboarding