Principal Data Modernization Engineer

We need to output HTML fragment with sections: headings

for sections like 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. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "ACTIVE SECURITY CLEARANCE AT THE TS/SCI POLYGRAPH LEVEL IS REQUIRED" - that's a requirement, should be included under Requirements or Qualifications. Also "We are seeking a proactive, visionary Data Modernization Systems Engineer & Technical Project Manager..." is description, maybe About the role. We need to parse content: - Job description: "ACTIVE SECURITY CLEARANCE AT THE TS/SCI POLYGRAPH LEVEL IS REQUIRED" (requirement) - "We are seeking a proactive, visionary Data Modernization Systems Engineer & Technical Project Manager to serve as the lead interface for the customer’s Chief Data Architect on the TKO program. In this high-visibility, transformative role, you will be the face of a critical initiative aimed at streamlining enterprise data processing and reshaping the customer’s entire data environment. You will bridge high-level architectural strategy with tactical engineering execution—translating vague guidance into clear courses of action, aligning stakeholders, driving agile release planning, and continuously identifying new growth opportunities." This is role description / responsibilities. - "The annual base salary range for this role is $165,000-$196,000 (USD) , which does not include discretionary bonus compensation or our comprehensive benefits package. Actual compensation offered to the successful candidate may vary from posted hiring range based upon geographic location, work experience, education, and/or skill level, among other things." This is Pay info. - Then list of Required Skills (bulleted). Then Desired Skills. - Then "About Nyla Technology Solutions" paragraph. - Then "Taking Care of All of You" describing benefits: Nyla FLEX program details: PAY, LEAVE, SCHEDULE, health care, 401k matching, Professional Development $5k per year, student loan repayment, 8 hours volunteering. We need to output sections: maybe About the role (description), Responsibilities (maybe combine with description), Requirements (clearance + education + experience), Qualifications (maybe same as Requirements?), Skills (Required and Desired), Benefits (FLEX details, health care, 401k, etc.), Pay (salary range), Schedule (maybe part of Benefits? but we have schedule info in FLEX: ability to scale down to 30-32 hours). Since schedule info is present, we can create a Schedule section. We must not create sections with filler like "commensurate with experience". We have actual content. We must not repeat job title as heading. We must not include Job ID etc. We must not include boilerplate like equal opportunity employer (though it's at end). Remove that. We must not include application instructions. We must preserve all substantive info. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide which sections to include. Potential sections: - About the role (description) - Responsibilities (maybe same as description; but we could combine) - Requirements (clearance, education/experience) - Qualifications (maybe same as Requirements; but we could avoid duplication) - Skills (Required and Desired) - Benefits (FLEX program details, health care, 401k, professional development, student loan repayment, volunteering) - Pay (salary range) - Schedule (flex schedule info) We must avoid thin sections. But we have enough content for each. We need to ensure we don't create a section with just placeholder text. All have content. We need to extract specifics: About the role: "We are seeking a proactive, visionary Data Modernization Systems Engineer & Technical Project Manager to serve as the lead interface for the customer’s Chief Data Architect on the TKO program. In this high-visibility, transformative role, you will be the face of a critical initiative aimed at streamlining enterprise data processing and reshaping the customer’s entire data environment. You will bridge high-level architectural strategy with tactical engineering execution—translating vague guidance into clear courses of action, aligning stakeholders, driving agile release planning, and continuously identifying new growth opportunities." Responsibilities: Could be same as above; but maybe we can extract duties: "serve as the lead interface for the customer’s Chief Data Architect on the TKO program", "be the face of a critical initiative aimed at streamlining enterprise data processing and reshaping the customer’s entire data environment", "bridge high-level architectural strategy with tactical engineering execution—translating vague guidance into clear courses of action, aligning stakeholders, driving agile release planning, and continuously identifying new growth opportunities." We'll put as

  • . Requirements: "ACTIVE SECURITY CLEARANCE AT THE TS/SCI POLYGRAPH LEVEL IS REQUIRED", plus education/experience: "Education: Bachelor’s Degree in Computer Science, Software Engineering, or a related technical discipline, paired with relevant full-lifecycle software development experience (or equivalent combination of education and hands-on professional experience) PLUS 10+ years experience as a SE in programs and contracts of similar scope, type, and complexity OR High School Diploma / GED, PLUS 14+ years of specialized technical experience in lieu of a degree." Qualifications: maybe same as Requirements; but we could treat Requirements as qualifications. To avoid duplication, maybe we combine Requirements and Qualifications into one section called Requirements/Qualifications. But instructions: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include both Requirements and Qualifications if they have distinct content. However the posting lumps education/experience under "Education:" and then "Required Skills". The "Required Skills" is separate. So we could have Requirements = clearance + education/experience. Qualifications = maybe the Required Skills list? But they already have a Skills section. Better to treat Requirements as clearance + education/experience, Qualifications as maybe nothing else; but we could omit Qualifications if no distinct content. However instructions: "Prefer a few substantive sections over many thin ones." So we could omit Qualifications if it would be thin. Let's see if we have any content for Qualifications beyond Requirements and Skills. The posting does not have a separate "Qualifications" heading; it's just Education and experience. So we can treat that as Requirements. Then we can have Skills section for Required and Desired skills. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Now extract content for each. About the role: as above paragraph. Responsibilities: list of duties: lead interface, face of initiative, bridge strategy, translate guidance, align stakeholders, drive agile release planning, identify growth opportunities. We could also include "serve as the lead interface for the customer’s Chief Data Architect on the TKO program" etc. Requirements: clearance + education/experience. Skills: Required Skills list and Desired Skills list. We need to format as
    • for any list of duties/requirements/benefits. For Skills, we have two lists: Required Skills and Desired Skills. Could make subheadings? Not allowed to create new headings beyond the specified ones. But we could embed headings inside? Probably not. Better to make two separate
      with preceding

      indicating Required Skills and Desired Skills. That's okay. Benefits: includes Nyla FLEX program details: PAY (annual leave, holidays, cash out, extra hours, 1.3x rate after 1880 hours), LEAVE (buy additional annual leave up to 6 weeks, plus holidays, paid anniversary leave), SCHEDULE (flex to 30-32 hours), health care (100% covered), 401k matching 10% with full vesting day 1, Professional Development $5k per year, student loan repayment program, 8 hours volunteering annually. We need to capture all that. Pay: salary range $165,000-$196,000 USD, note about discretionary bonus, variation based on location etc. Schedule: from Benefits we have schedule info: ability to scale down to 30-32 hours while still enjoying benefits. Also mention flexibility to cash out annual leave, opt out benefits, arrange additional hours on contract (>40 hrs/week), option to earn 1.3x hourly after 1880 hours. That's more about pay and schedule. But we already have Pay section for salary range; schedule info could go under Schedule section. However the schedule info also includes ability to cash out annual leave etc. That's more about leave/pay. But we can put schedule specifics under Schedule: ability to scale down to 30-32 hours, flexibility to adjust hours, etc. We must not repeat content across sections unnecessarily, but we can include relevant details. Let's extract schedule specifics: "With Nyla FLEX, you have the freedom to scale down to 30-32 hours while still enjoying the top-notch Nyla benefits you know and love." Also earlier: "PAY - Nyla starts with 4 weeks of Annual Leave plus 11 holidays and an additional day of Annual Leave for each year you’re at the company. You have the flexibility to cash out your annual leave hours, opt out of other Nyla benefits, and/or arrange for additional hours on contract* (over 40 hrs/week). There’s even an option to earn 1.3 times your hourly rate once you work over 1880 hours on contract!" That's pay/leave. "LEAVE - Want to spend more time with the family? Want more time to travel the world? You can BUY additional annual leave for a total of 6 weeks of annual leave. That’s up to 240 hours of leave plus 11 holidays! That’s not even including paid anniversary leave!" "SCHEDULE - Does the traditional 40-hour workweek no longer fit your lifestyle? With Nyla FLEX, you have the freedom to scale down to 30-32 hours while still enjoying the top-notch Nyla benefits you know and love. It's flexibility that works for you without compromising the perks!" Thus schedule section: ability to scale down to 30-32 hours, flexibility to adjust hours, etc. Pay section: salary range, note about discretionary bonus, variation. Benefits section: health care 100% covered, 401k matching 10% full vesting day 1, Professional Development $5k per year, student loan repayment program, 8 hours volunteering annually, plus maybe mention of Nyla FLEX program? But we already have Pay, Leave, Schedule sections covering FLEX details. However the FLEX program details include pay, leave, schedule. So we could treat Benefits as the other benefits (health care, 401k, professional development, student loan repayment, volunteering). And Pay, Leave, Schedule sections cover the FLEX specifics. However the instruction says to use headings like Benefits, Pay, Schedule. So we should have Benefits section for non-FLEX benefits. Pay section for salary range (and maybe also mention of FLEX pay aspects? but we already have Pay section for salary; we could also include FLEX pay details there, but that may duplicate. However we could keep Pay section just for salary range, and Leave and Schedule sections for those specifics. But we are not required to have Leave heading; only listed headings include Benefits, Pay, Schedule. Not Leave. So we cannot create a Leave heading. So we need to incorporate leave info into either Benefits or Pay or Schedule. Since we have Pay and Schedule headings, we could put leave details under