DMS MRO Data Engineer

We need to output only HTML fragment, with headings

for 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 as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Key info: - About Arcticom, LLC: description of company. Could be "About the role"? Actually "About Arcticom, LLC" is company description. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and maybe company? The posting includes "About Arcticom, LLC" then "About this position: DMS MRO Data Engineer Location – Dayton, OH". Then "Essential Duties and Responsibilities" etc. We need to preserve all substantive information. We need sections: maybe "About the role" (company and position overview), "Responsibilities" (essential duties), "Requirements" (minimum necessary qualifications?), "Qualifications" (education, experience, certifications?), "Skills" (knowledge, skills, abilities), "Pay" (wage/salary range), maybe "Schedule"? Not given. "Benefits"? Not given. So we only include sections with real content. We must not create sections with filler like "not specified". So we omit Benefits, Schedule if not present. We need to include Pay: Wage/Salary Range: $125k - $150K. So include

Pay

with

$125k - $150K

. We need to include maybe "Location" info? Could be part of About the role or maybe separate? Not a defined heading. Could embed in About the role paragraph. We need to include "Work Location: Hybrid remote in Wright-Patterson AFB, OH 45433". Also "Must reside within 50 miles of the customer site in Dayton, OH". Also "Live within 50 commutable miles of Dayton, OH". So include location details. We need to include "Applicants will be notified via phone or email within ten (10) business days of submittal." That's application instruction; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that line. We need to drop duplicated lines, boilerplate like EEO statements, etc. We need to keep all substantive info: company description, position description, essential duties, required qualifications (education, experience, licenses/certifications), knowledge/skills/abilities, relationship management, supervisory responsibilities (none), DOT covered (none), physical requirements, work environment, additional qualifying factors (drug screening, background check, clearance, shareholder preference, equal opportunity). Some of those may be considered boilerplate? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The shareholder preference and equal opportunity statements might be considered EEO boilerplate; we should remove them. Also "Bering Straits Native Corporation is an equal opportunity employer..." is EEO boilerplate; remove. Also "Shareholder Preference ..." maybe not EEO but could be considered specific? It's a preference for BSNC shareholders; might be substantive? It's a hiring preference; could be considered part of qualifications? Might keep? The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. Shareholder preference is not EEO; it's a specific preference. Might keep? However it's somewhat like a policy; but it's not boilerplate? It's specific to the contractor. I'd keep it as part of Additional Qualifying Factors maybe. But we also have "Necessary Physical Requirements" and "Work Environment". Those are substantive; we could include under a section maybe "Working Conditions"? Not in list of allowed headings. The allowed headings are limited to those examples; but we can still use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings; but we could also use other headings if needed? It says "use

for section headings (e.g. ...)" meaning those are examples; we likely should stick to those headings. So we need to map content to those headings. Thus we need to fit all substantive info into those categories: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About the role: company description, position title, location, maybe work arrangement. - Responsibilities: essential duties list. - Requirements: maybe minimum necessary qualifications (education, experience, licenses/certifications) and also citizenship, clearance, residency, DoD experience. - Qualifications: maybe preferred qualifications? Or we could combine Requirements and Qualifications? But we need to avoid duplication. Could treat Requirements as "Required (Minimum Necessary) Qualifications" and Qualifications as "Preferred Qualifications" or "Additional Qualifying Factors". However the instruction says we should not create thin sections; we prefer few substantive sections. Could combine into one "Requirements" section that includes both required and preferred? But we have separate headings for Requirements and Qualifications; we could use both if they have distinct content. Let's see content: Required (Minimum Necessary) Qualifications: - Education: Bachelor's (US accredited Required) - Experience: 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: S. federal government security clearance (Preferred), AWS Certified Solutions Architect (Preferred), Databricks Certified Data Engineer Professional (Preferred) - Work Location: Hybrid remote in Wright-Patterson AFB, OH 45433 Then later "Requirements Knowledge, Skills, Abilities, and Other Characteristics": - Must be a U.S. Citizen - Must be able to obtain and maintain a favorable NACI clearance - Must reside within 50 miles of the customer site in Dayton, OH - Must have experience working with the DoD or another federal agency Then "Qualifications" heading again: Bachelor’s degree in computer science, engineering, or a related field from an accredited United States university Technical skills, hands-on experience, and proficiency with: list (Databricks, Spark, cloud data engineering, SQL, AWS S3, Python, SharePoint lists, Microsoft Graph, Microsoft 365 apps, APIs, Jira, AI proficiency) Relationship Management and Teamwork: list of soft skills Preferred Certifications such as AWS Certified Solutions Architect or Databricks Certified Data Engineer AI aware Familiarity with Air Force-specific systems or DoD compliance frameworks Live within 50 commutable miles of Dayton, OH Then "Supervisory Responsibilities": none. "DOT Covered/Safety-Sensitive Role Requirements": not subject. "Necessary Physical Requirements": description. "Work Environment": description. "Additional Qualifying Factors": pre-employment drug screening, background check, clearance, access to military installations. "Shareholder Preference": BSNC gives hiring preference to shareholders... "Bering Straits Native Corporation is an equal opportunity employer..." (EEO) - remove. Thus we have many overlapping items. We need to decide how to map to headings. Potential plan: - About the role: company description + position overview (title, location, hybrid remote, etc.) - Responsibilities: essential duties list (bulleted). - Requirements: combine the mandatory requirements: education (Bachelor's), citizenship, NACI clearance, residency within 50 miles, DoD experience, Databricks 2 years required, maybe also mention required experience? Actually the Required (Minimum Necessary) Qualifications includes many "Preferred" items; only Databricks 2 years is Required; also Bachelor's required. So we can list required: Bachelor's degree (US accredited), Databricks 2 years experience, US Citizen, ability to obtain NACI clearance, reside within 50 miles of Dayton, OH, DoD/federal agency experience. Also maybe mention hybrid remote location? Could be in About the role. - Qualifications: preferred qualifications and skills: Python 4 years, SQL 4 years, SharePoint Development 3 years, Spark 3 years, AWS 3 years, S3 3 years, AI 2 years, federal govt security clearance preferred, AWS Cert Solutions Architect preferred, Databricks Cert Data Engineer Professional preferred, plus the technical skills list from Qualifications section (Databricks, Spark, SQL, AWS S3, Python, SharePoint, Microsoft Graph, Microsoft 365, APIs, Jira, AI proficiency), relationship management soft skills, familiarity with Air Force-specific systems/DoD compliance frameworks, AI aware, shareholder preference (maybe include), etc. - Skills: maybe we could separate technical skills vs soft skills? But we already have Qualifications covering technical skills; maybe Skills could be the soft skills (relationship management, teamwork, initiative, meticulous, cross-functional, rapid learning, collaboration). However the instruction says we can use Skills heading for skills. We could put the soft skills under Skills. - Pay: wage/salary range. - Benefits: none -> omit. - Schedule: none -> omit. We must not create sections with filler. So we will include About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Check if any content missing: physical requirements, work environment, additional qualifying factors (drug screening, background check, clearance, access to military installations). Those are substantive; we need to include them somewhere. Could be part of Requirements or Qualifications? They are not exactly qualifications but conditions of employment. Could be placed under Requirements (maybe as "Additional Requirements") but we already have Requirements heading. Could add a bullet list under Requirements for those. Or we could create a separate section like "Working Conditions" but not allowed. Might be okay to include under Requirements as they are requirements for employment. Thus under Requirements we can include: US Citizenship, NACI clearance, residency within 50 miles, DoD experience, pre-employment drug screening, acceptable background check, ability to obtain access to military installations, shareholder preference? Actually shareholder preference is a preference not a requirement. Could be under Qualifications. We also need to include physical requirements and work environment description. Could be under Requirements as well (maybe as "Physical & Work Environment Requirements"). But we need to avoid making the section too thin; we can combine. Let's draft. First, About the role:

Arcticom, LLC provides network and systems administration, enterprise architecture and 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 among other services. This position is for a DMS MRO Data Engineer located in Dayton, OH with a hybrid remote arrangement at Wright‑Patterson AFB, OH 45433.

That captures company description and position. Responsibilities: list of essential duties. We need to extract the essential duties list from the posting: - Build and optimize ETL data pipelines using Databricks and Apache Spark - Develop scalable data models leveraging Spark Data Frames 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