Scheduler L3

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to parse the posting. The posting includes: - Title: "Requirements Synergy is looking for an experience Scheduler to join our team." Actually the first line: "Requirements Synergy is looking for an experience Scheduler to join our team." Might be a typo; but we ignore job title heading. - About the role: The paragraph after first line: "The Scheduler is responsible for designing, developing, and maintaining detailed resource-loaded schedules for implementation, developmental and operational systems. Works with developmental and operational teams to develop detailed schedules and assists in keeping these schedules current. Uses or recommends automated tools such as MS Project, Primavera or program mandated software. Develops and or modifies project schedules and or the integration of multiple project schedules into an overall Master Program Schedule. Maintains the overall Master Program /Project Schedule. Links project schedules with the overarching program, Investment Portfolio, functional area and/or other Integrated Master Plans (IMPs). Provides hands-on development of layered schedules and IMPs that address how an acquisition project is progressing and how that project contributes to overarching requirements and objectives. Maintains status on linkages and dependencies with related projects. Daily duties may include the following: ..." Then a list of daily duties (bulleted). Then "Requirements" section: includes TS/SCI with full scope polygraph, 12 years experience, Bachelor's degree, etc. Also includes "Requirements Requirs a TS/SCI with full scope polygraph Twelve (12) years experience as a Scheduler in programs and contracts of similar scope, type, and complexity is required.Bachelor's degree in a technical or business discipline from an accredited college or university is required.Shall have two (2) years of demonstrated experience managing a schedule for an engineering program involving hardware and software development and multiple sub-components using MS Project or Privavera. Shall have successfully completed an advanced level MS Project or Primavera course and demonstrated experience with MS Project and or Primavera.Certification for the Association for the Advancement of Cost Engineering (AACE) and or Planning and Scheduling Professional (PSP) is desired.A master's degree may be substituted for two (2) years of experience, reducing the requirement to ten (10) years of experience. Four (4) years of additional scheduling experience may be substituted in lieu of Bachelor's degree increasing the years of experience requirement to sixteen (16) years." Then "Synergy ECP, a platform company..." is about company description. Could be "About the role"? Actually that's more about company. Could be "About the company" but not in allowed headings. We could put that under "About the role"? Not exactly. But we have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have responsibilities: daily duties list. Also earlier description of role responsibilities. Could combine into Responsibilities. Requirements: TS/SCI, years experience, degree, etc. Qualifications: maybe education, certifications, etc. But we have overlapping. We could put education under Qualifications, certifications under Skills? But we need to follow instruction: Use headings only when posting has real specific content. We can decide to have sections: About the role (maybe company overview?), Responsibilities, Requirements, Qualifications, Skills, Benefits. Pay and Schedule not present, so omit. We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, application instructions, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out the EEO paragraph, the "If you are interested..." etc. Also remove company description? That's substantive? It's about Synergy ECP, maybe considered "About the role"? Not exactly role but company. Could be considered "About the role"? Might be okay to include as part of About the role? But the instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put company overview under About the role. However the posting already has a description of the role responsibilities; we could put that under Responsibilities. The company description could be under About the role (maybe as a brief overview). But we need to ensure we don't invent content. The company description is present: "Synergy ECP, a platform company with Falfurrias Capital Partners, has a talented, dedicated staff to provide a broad range of services to the defense and intelligence industries. Our capabilities are focused on software engineering, cybersecurity, system engineering and IT services. Providing these services, Synergy ECP, has earned a client list that includes numerous Fortune 100 companies, in addition to multiple US government agencies and US military services. Synergy ECP possesses pertinent and highly valued credentials, specialized certifications, and clearance levels to secure our clients’ computer networks and information at a time when a premium is placed on cyber security. In an ultra-competitive environment, Synergy ECP has thrived by adhering to its name – making sure excellence is displayed by its Employees, to its Customers and by Improving Performance (ECP). We simply can’t have one without the other. It’s what sets us apart – enabling us to be an autonomous agile business that delivers huge results to meet the ever-evolving demands of our customers. Synergy ECP was established in 2007 and its management team has over 30+ years of Department of Defense and Intelligence Community experience. Our leadership team and strong, determined staff are ready to embrace new challenges and continue as a driving force in our field." That's substantive; we can include under About the role. Now Responsibilities: The role description and daily duties list. We need to extract the list items: "Assist in defining and implementing schedule software (MS Project, Primavera, or specific program mandated software, etc.) management processes and proceduresImplement schedule version control processes, policies and proceduresAssist in maintaining and developing the environment for the overall Master Program/Project Schedule and or the integration of multiple project schedules into an overall Master Program ScheduleMaintain the schedule product build, staging, testing, deployment and integrationDefine and implement schedule configuration management processes and procedures; such as creating product build scripts and procedures, and integrate those scripts with the schedule build processDevelop schedule version control processes, policies and procedures and ensures that they are followed on development or operational schedule development and implementation projectsFacilitate weekly meetingsProvide recommendations to the program manager for allocation of management reserve to address resource/schedule constraintsCoordinate a cross-walk of milestones and interdependencies among projects and/or functional areas (engineering, manufacturing, test, quality control, etc)" Note there are no spaces between some items; we need to separate them logically. We'll treat each sentence as a list item. We'll split by periods? But we need to preserve all info. We'll create

• for each duty. We'll need to ensure we don't miss any. Let's parse the duties paragraph: "Daily duties may include the following: Assist in defining and implementing schedule software (MS Project, Primavera, or specific program mandated software, etc.) management processes and proceduresImplement schedule version control processes, policies and proceduresAssist in maintaining and developing the environment for the overall Master Program/Project Schedule and or the integration of multiple project schedules into an overall Master Program ScheduleMaintain the schedule product build, staging, testing, deployment and integrationDefine and implement schedule configuration management processes and procedures; such as creating product build scripts and procedures, and integrate those scripts with the schedule build processDevelop schedule version control processes, policies and procedures and ensures that they are followed on development or operational schedule development and implementation projectsFacilitate weekly meetingsProvide recommendations to the program manager for allocation of management reserve to address resource/schedule constraintsCoordinate a cross-walk of milestones and interdependencies among projects and/or functional areas (engineering, manufacturing, test, quality control, etc)" We can separate by noticing each starts with a verb: Assist..., Implement..., Assist..., Maintain..., Define..., Develop..., Facilitate..., Provide..., Coordinate... Thus we can create list items accordingly. Now Requirements: The block after "Requirements". Contains TS/SCI, 12 years experience, Bachelor's degree, 2 years demonstrated experience managing schedule for engineering program hardware/software using MS Project or Primavera, completed advanced level MS Project or Primavera course, demonstrated experience with MS Project or Primavera, Certification AACE or PSP desired, master's degree substitution, 4 years additional scheduling experience substitution for Bachelor's. We need to preserve all details. We could split into list items. Now Qualifications: Could include education (Bachelor's degree), maybe also master's substitution? But that's already in Requirements. Could treat Qualifications as education and certifications? But we already have certification in Requirements. Might be redundant. However we need to avoid thin sections; maybe combine Requirements and Qualifications? But we have to follow headings only if content exists. We could have Requirements (including experience, clearance, degree) and Qualifications (education, certifications). But we risk duplication. Let's see if we can separate: Requirements: TS/SCI clearance, years of experience, demonstrated experience, etc. Qualifications: Bachelor's degree, master's substitution, certification desired. However the posting also mentions "Bachelor's degree in a technical or business discipline from an accredited college or university is required." That's a qualification. Also "Certification for the Association for the Advancement of Cost Engineering (AACE) and or Planning and Scheduling Professional (PSP) is desired." That's a qualification/skill. Also "Shall have successfully completed an advanced level MS Project or Primavera course and demonstrated experience with MS Project and or Primavera." That's a skill/qualification. We could have sections: Requirements (clearance, years experience), Qualifications (education, certifications, course completion), Skills (MS Project, Primavera, scheduling tools). But we need to avoid too many thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine into Requirements and Qualifications only, and maybe Skills if we have distinct skill set. We have specific skills: MS Project, Primavera, schedule software, version control, configuration management, etc. Those are more responsibilities/skills. We could have Skills section for tools: MS Project, Primavera, schedule configuration management, version control, etc. But many of those appear in responsibilities. Given the instruction to prefer few substantive sections, we could have: About the role, Responsibilities, Requirements, Benefits. That's four sections. That seems reasonable. We'll put education and certifications under Requirements (since they are requirements). We'll put skills maybe under Responsibilities (as part of duties). We'll omit Qualifications and Skills separate headings. Thus sections: - About the role: company overview paragraph. - Responsibilities: role description paragraph + list of daily duties. - Requirements: clearance, years experience, degree, experience specifics, course, certification desired, substitution rules. - Benefits: compensation, health & retirement, education, work/life balance, corporate facilities. We must not include Pay or Schedule sections. Now we need to format. We'll output HTML fragment:

  About the role

  Synergy ECP, a platform company with Falfurrias Capital Partners, has a talented, dedicated staff to provide a broad range of services to the defense and intelligence industries. Our capabilities are focused on software engineering, cybersecurity, system engineering and IT services. Providing these services, Synergy ECP, has earned a client list that includes numerous Fortune 100 companies, in addition to multiple US government agencies and US military services. Synergy ECP possesses pertinent and highly valued credentials, specialized certifications, and clearance levels to secure our clients’ computer networks and information at a time when a premium is placed on cyber security. In an ultra-competitive environment, Synergy ECP has thrived by adhering to its name – making sure excellence is displayed by its Employees, to its Customers and by Improving Performance (ECP). We simply can