Senior Data Analyst

for prose. We need to preserve all substantive info: include clearance requirement, US Citizenship, hybrid location, description of role, responsibilities bullet list, required qualifications bullet list, preferred qualifications bullet list, education, salary range, benefits list, company description maybe as About the role? The "About the role" could be the introductory paragraph(s) after job details. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Application Deadline: October 31, 2026" maybe considered application instruction? It's a deadline, but maybe considered application instruction; we should drop it. Also remove "See below, to name a few:" maybe part of benefits list; we can keep benefits list. We need to preserve benefits list: 15 days PTO..., Eleven (11) paid Federal holidays..., Health and Dental Insurance..., Life Insurance..., 401(k) plan..., FSA/DFSA/HSA..., Annual Tuition & Professional Development Reimbursement benefit. We need to preserve company description maybe as part of "About the role" or separate "About the company"? Not listed as allowed heading; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under About the role or maybe under Qualifications? Better to put under About the role (intro). Also include "Clearance Required: Public Trust – Federal Client requires US Citizenship" and location. Thus structure:

About the role

Senior Data Analyst position supporting the 287(g) program. Hybrid role based in Washington, DC. Requires Public Trust clearance and US Citizenship. The incumbent will own the end-to-end data lifecycle for the 287(g) program, managing automated data pipelines, clearance and credentialing tracking, and cross-functional reporting to ensure data integrity and seamless coordination between operational stakeholders and federal security units.

• for any list of duties/requirements/benefits. It didn't forbid subheadings inside list? Probably better to just list each duty as
• . Could also keep subheadings as

  but that might be extra. Safer to just list each duty as

• . We'll need to capture all duties. Let's extract duties: Automated Data Engineering & Intake: - Pipeline Management: Oversee and maintain Power Automate workflows for inbox monitoring, PDF staging, and automated record creation. - Data Transformation: Utilize Python-based extraction processes to convert raw PDF forms into standardized JSON records. Ensure normalized field mapping for ingestion. - Quality Assurance: Perform daily data quality audits to reconcile discrepancies between system records, troubleshoot JSON ingestion failures, and ensure source of truth consistency. Clearance & Credentialing Operations: - Security Processing: Manage the initiation and submission of background investigation packets for 287(g) programs. Verify all documents for completeness and signature validity. - Compliance Protocol: Manage strict PII/CUI security standards, including password-protected file handling and secure transmission of initiation packets. - Lifecycle Tracking: Maintain process visibility via Tableau and tracking tools; proactively flag stale cases or clearance blockers to federal leads. Training & Certification Support: - Training Readiness: Monitor training mailboxes, validate course eligibility, and execute “Pass/Fail” updates in SharePoint. - Credentialing Fulfillment: Execute manual and automated shipping batches. Oversee the generation, attachment, and distribution of G-570/G-504 documents; track receipt/verification status to close out credentialing loops. Stakeholder Communication: - Serve as the primary point of contact for external agencies regarding training access, login errors, and enrollment status, following standardized escalation/response SOPs. PMO Operational Governance: - Reporting: Generate recurring and ad-hoc reports using Excel-based data sets and cross-functional trackers. - Documentation: Maintain SOPs, tracking tables, and SharePoint repository structures. Ensure all programmatic communications and work products are logged for transition continuity and institutional knowledge retention. Now Required Qualifications: It lists "Required Experience/Skills:" with bullet-like paragraphs: - Project Oversight Experience: 3-5 years of experience overseeing aspects of a project, leading a team on large projects or a significant segment of large and complex projects; ability to analyze new and complex project-related problems and create innovative solutions involving schedule, technology, methodology, tools, solution components, and financial management of the project. - Systems & Applications Planning: Experience providing application systems analysis and developing long- and short-range plans for application selection, systems development, systems maintenance, and production activities for necessary support resources (e.g., the data pipelines, Power Automate workflows, and Tableau/SharePoint tracking systems used in this role). - Functional Area Experience: 3-5 years of experience in the relevant functional area — data analytics, data management, or reporting/records processing. We could treat these as list items under Requirements or Qualifications. The allowed headings include Requirements and Qualifications. We need to decide which to use. Probably combine required qualifications under "Requirements" and preferred qualifications under "Qualifications" or "Skills". But we also have Skills heading allowed. Could put required experience under Requirements, preferred qualifications under Qualifications, and maybe skills under Skills (like automation, data systems, records management, analytical discipline). However the preferred qualifications already include skills. Could separate. Let's map: - Requirements: Required Experience/Skills (the three bullet points). - Qualifications: Preferred Qualifications (Automation, Data Systems, Records Management, Analytical Discipline) plus Education (Some college credits required; an Associate’s Degree is preferred.) - Skills: maybe we could list specific technical skills: Power Automate, Python, SharePoint, Tableau, etc. But those are already in preferred qualifications. Could put them under Skills as a list. But we must not create thin sections. Better to have fewer substantive sections. Perhaps combine Required and Preferred into Qualifications, and put Skills as separate if we have distinct skill list. However the preferred qualifications already list skills; we could put them under Skills. Let's think: The instruction: "Prefer a few substantive sections over many thin ones." So maybe we have About the role, Responsibilities, Requirements (including required and preferred), Benefits, Pay. That's 5 sections. Could omit Qualifications and Skills if we incorporate into Requirements. But we need to preserve all info; we can put required experience and preferred qualifications together under Requirements as a list, maybe with subheadings? But we can't have subheadings inside list? Could use

  for subheadings then

  . That's okay. Thus sections: - About the role (intro) - Responsibilities (list) - Requirements (list of required experience + preferred qualifications + education) - Benefits (list) - Pay (salary range) We'll omit Schedule. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to output only HTML fragment. Let's craft. First, About the role:

  Senior Data Analyst position supporting the 287(g) program. Hybrid role based in Washington, DC. Requires Public Trust clearance and US Citizenship. The incumbent will own the end-to-end data lifecycle for the 287(g) program, managing automated data pipelines, clearance and credentialing tracking, and cross-functional reporting to ensure data integrity and seamless coordination between operational stakeholders and federal security units.

  Now Responsibilities:

  Responsibilities

  • Pipeline Management: Oversee and maintain Power Automate workflows for inbox monitoring, PDF staging, and automated record creation.
  • Data Transformation: Utilize Python-based extraction processes to convert raw PDF forms into standardized JSON records. Ensure normalized field mapping for ingestion.
  • Quality Assurance: Perform daily data quality audits to reconcile discrepancies between system records, troubleshoot JSON ingestion failures, and ensure source of truth consistency.
  • Security Processing: Manage the initiation and submission of background investigation packets for 287(g) programs. Verify all documents for completeness and signature validity.
  • Compliance Protocol: Manage strict PII/CUI security standards, including password-protected file handling and secure transmission of initiation packets.
  • Lifecycle Tracking: Maintain process visibility via Tableau and tracking tools; proactively flag stale cases or clearance blockers to federal leads.
  • Training Readiness: Monitor training mailboxes, validate course eligibility, and execute “Pass/Fail” updates in SharePoint.
  • Credentialing Fulfillment: Execute manual and automated shipping batches. Oversee the generation, attachment, and distribution of G-570/G-504 documents; track receipt/verification status to close out credentialing loops.
  • Serve as the primary point of contact for external agencies regarding training access, login errors, and enrollment status, following standardized escalation/response SOPs.
  • Reporting: Generate recurring and ad-hoc reports using Excel-based data sets and cross-functional trackers.
  • Documentation: Maintain SOPs, tracking tables, and SharePoint repository structures. Ensure all programmatic communications and work products are logged for transition continuity and institutional knowledge retention.
  Now Requirements: We need to include required experience bullets and preferred qualifications and education. Let's list: Required Experience/Skills: - Project Oversight Experience: 3-5 years of experience overseeing aspects of a project, leading a team on large projects or a significant segment of large and complex projects; ability to analyze new and complex project-related problems and create innovative solutions involving schedule, technology, methodology, tools, solution components, and financial management of the project. - Systems & Applications Planning: Experience providing application systems analysis and developing long- and short-range plans for application selection, systems development, systems maintenance, and production activities for necessary support resources (e.g., the data pipelines, Power Automate workflows, and Tableau/SharePoint tracking systems used in this role). - Functional Area Experience: 3-5 years of experience in the relevant functional area — data analytics, data management, or reporting/records processing. Preferred Qualifications: - Automation: Advanced working knowledge of Power Automate (cloud flows, triggers, conditional logic) and Python (data extraction/parsing/JSON). - Data Systems: Proficiency in SharePoint (list management, complex folder structures) and Tableau (data visualization and status reporting). - Records Management: Proven experience handling PII and CUI in accordance with federal security protocols; ability to manage password-encrypted document workflows. - Analytical Discipline: Ability to reconcile data across disparate systems and maintain 100% accuracy in highly regulated environments. - Education: Some college credits required; an Associate’s Degree is preferred. We'll put these as list items. Thus:

  Requirements