MRO Data Engineer

We need to output HTML fragment with sections: About the role? The posting includes "About Arcticom, LLC" and "About this position". The job title is MRO Data Engineer. We should not repeat job title as heading. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. We have: - About Arcticom, LLC: description of company. Could be "About the role"? Actually "About Arcticom, LLC" is company overview. Could be "About the role" maybe not. But we can create a section "About the role" with description of position? The posting includes "About this position: MRO Data Engineer Location – Dayton, OH". That's about the position. So we can put that under

About the role

with a paragraph. - Essential Duties & Responsibilities: list of duties. Use

• . - Required (Minimum Necessary) Qualifications: includes education, experience, citizenship, clearance, residency, DoD experience. Also includes Knowledge, Skills, Abilities, And Other Characteristics (technical skills, etc). Also includes Experience (years). Also includes License/Certification. Also includes Preferred Certifications etc. Also includes AI aware, familiarity with Air Force-specific systems, Live within 50 commutable miles of Dayton, OH. Also includes Supervisory Responsibilities (none). DOT Covered etc. Physical Requirements, Work Environment, Work Location, Additional Qualifying Factors (drug screening, background check, clearance, access to military installations). Shareholder Preference, EEO statement. We need to decide which sections to output: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: Wage/Salary Range: $135k - $155k. So we can include Pay section. Schedule: Not mentioned explicitly. There's hybrid remote location but not schedule. So we should not create Schedule section unless present. Benefits: Not mentioned. No benefits listed. So we should not create Benefits. Skills: Could be a section for technical skills etc. But we have many skills listed under Knowledge, Skills, Abilities. Could combine into Skills section. However we also have Qualifications (education, experience, clearance). Could separate. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information. So we need to include all details. We must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement at end, also the "Shareholder Preference" maybe considered not boilerplate? It's specific to the company but could be considered preferential hiring. Might be considered substantive? It's about hiring preference. Might keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Shareholder Preference is not EEO, it's a preference. Might keep? But it's still a kind of preferential hiring statement. Not sure. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So only those specific types. Shareholder Preference is not EEO, it's a preference. Might be okay to keep. However it's also a kind of affirmative action? Might be considered similar to EEO? It's a preference for shareholders. Not exactly EEO. I'd keep it as part of Additional Qualifying Factors maybe. We also need to remove duplicated lines. There's some duplicated lines about "Ability to work collaboratively with a diverse team of contractors and government personnel" appears twice slightly different. We should deduplicate. We need to output only HTML fragment, no markdown. Let's structure:

  About the role

  MRO Data Engineer located in Dayton, OH. Hybrid remote work at Wright-Patterson AFB, OH 45433.

  Maybe also include company description? Could be separate section "About Arcticom, LLC" but not in allowed headings. Could incorporate into About the role? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. So we can put company overview under About the role? Might be okay. Better: About the role includes description of position and maybe company. We'll include a paragraph summarizing both. Then Responsibilities: list of essential duties. Then Requirements: maybe include education, citizenship, clearance, residency, DoD experience. Then Qualifications: maybe include technical skills and experience years. But we have overlapping. Could combine Requirements and Qualifications into one? But we need to follow headings only if content exists. We can have both. Let's extract: Requirements (Minimum Necessary) Qualifications includes: - Education: Bachelor’s degree in computer science, engineering, or related field from accredited US university. - Experience: Must be US Citizen, must obtain/maintain NACI clearance, must reside within 50 miles of Dayton, OH, must have experience working with DoD or another federal agency. Then Knowledge, Skills, Abilities, And Other Characteristics includes technical skills list. Then Experience years: Python 4 years preferred, SQL 4 years preferred, SharePoint Development 3 years preferred, Spark 3 years preferred, AWS 3 years preferred, S3 3 years preferred, AI 2 years preferred, Databricks 2 years required. License/Certification: US federal government security clearance (preferred), AWS Certified Solutions Architect (preferred), Databricks Certified Data Engineer Professional (preferred). Also "Preferred Certifications such as AWS Certified Solutions Architect or Databricks Certified Data Engineer" (duplicate). Also "AI aware". Also "Familiarity with Air Force-specific systems or DoD compliance frameworks". Also "Live within 50 commutable miles of Dayton, OH" (duplicate of residency). Also Supervisory Responsibilities: none. DOT Covered: not applicable. Physical Requirements: mental alertness. Work Environment: situational awareness. Work Location: Hybrid remote in Wright-Patterson AFB, OH 45433. Additional Qualifying Factors: pre-employment drug screening, background check, clearance levels, access to military installations. Shareholder Preference: BSNC gives hiring preference to shareholders etc. Bering Straits Native Corporation is an equal opportunity employer (EEO) - remove. We need to avoid duplication. Let's craft sections:

  About the role

  MRO Data Engineer position based in Dayton, OH with hybrid remote work at Wright‑Patterson AFB (45433). Arcticom, LLC provides network and systems administration, enterprise architecture, resource planning, certification and accreditation, software design, programming, maintenance of telecommunications and land mobile radio equipment and systems, help desk support, and IT transformation services.

  Responsibilities

  • Build and optimize ETL data pipelines using Databricks and Apache Spark
  • Develop scalable data models leveraging Spark DataFrames and Spark SQL for efficient querying, aggregation, and integration against numerous diverse data sources
  • Utilize Python and Regular Expressions for advanced text parsing, pattern matching, and data cleansing to prepare structured datasets for downstream ingestion
  • Use APIs for seamless data exchange and automation across systems
  • Manage SharePoint data (lists, libraries, files, metadata) programmatically using Python and Microsoft Graph API
  • Leverage Microsoft 365 tools for documentation and collaboration
  • Develop and maintain Amazon Web Services (AWS) including S3
  • Fully utilize the Microsoft 365 environment for cross‑functional data sharing and productivity
  • Use Jira to track and manage issues, tasks, and project workflows
  • Collaborate with cross‑functional teams and technical stakeholders to define data transformations of legacy systems to modern schemas
  • Leverage Subject Matter Expert (SME) collaboration to interpret business rules and build business logic into data extracts and transformation processes
  • Build and maintain strong working relationships with SMEs, helping to identify requirements for data transformations based on iterative product feedback

  Requirements

  • Bachelor’s degree in computer science, engineering, or a related field from an accredited United States university
  • Must be a U.S. Citizen
  • Must be able to obtain and maintain a favorable National Agency Check with Inquiries (NACI) clearance
  • Must reside within 50 miles of the customer site in Dayton, OH
  • Must have experience working with the Department of Defense (DoD) or another federal agency

  Qualifications

  • Technical skills and hands‑on experience with:
    • Databricks, Apache Spark, and cloud‑based data engineering and modeling
    • SQL for querying and managing relational data
    • AWS cloud services, including S3
    • Python for data analysis, cleansing, and visualization
    • SharePoint lists, document libraries, and Microsoft Graph
    • Microsoft 365 apps and integration workflows
    • Developing and consuming APIs for data exchange between different systems
    • Jira or other agile workflow management systems for issue and project tracking
    • Artificial Intelligence (AI) proficiency to incorporate into daily activities and workflows
  • Experience (preferred unless noted):
    • Python: 4 years (preferred)
    • SQL: 4 years (preferred)
    • SharePoint Development: 3 years (preferred)
    • Spark: 3 years (preferred)
    • AWS: 3 years (preferred)
    • S3: 3 years (preferred)
    • AI: 2 years (preferred)
    • Databricks: 2 years (required)
  • Licenses/Certifications (preferred):
    • U.S. federal government security clearance
    • AWS Certified Solutions Architect
    • Databricks Certified Data Engineer Professional
  • Additional qualifications:
    • AI aware
    • Familiarity with Air Force‑specific systems or DoD compliance frameworks
    • Live within 50 commutable miles of Dayton, OH

  Pay

  $135k - $155k salary range

  We should not include Benefits or Schedule. Check for any duplicated content: We have residency mentioned in Requirements and also in Additional qualifications (Live within 50 commutable miles). Could deduplicate by keeping only one. Since Requirements already includes residency, we can remove the duplicate in Additional qualifications. Also "Must be able to obtain and maintain a favorable NACI clearance" is similar to "U.S. federal government security clearance (preferred)". NACI is a specific clearance; we can keep both as they are distinct: NACI required, federal security clearance preferred. Keep both. Also "Experience working with DoD or another federal agency" is in Requirements. Also "Familiarity with Air Force‑specific systems or DoD compliance frameworks" is additional; keep. Check for any other duplicates: "Manage SharePoint data..." appears only once. "Develop and maintain Amazon Web Services (AWS) including S3" appears once. Check for any boilerplate: We removed EEO statement, shareholder preference? We kept shareholder preference? Actually we didn't include shareholder preference. We omitted it. That's okay; it's not EEO but could be considered preferential hiring. The instruction