Software Developer SME (Systems Software) (TS/SCI with Poly Required)

We need to output HTML fragment with sections: About the role? The posting includes description of GCI and role. We need to extract sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections that have real specific content. The posting includes a description of duties/skills (the long list). It also includes "Required Skills" and "Desired Skills". Also includes clearance requirement. No explicit Benefits, Pay, Schedule. So we should not include those sections. Also we need to avoid repeating job title as heading. The job title is "SME Software Developer". Not to repeat as heading. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Equal Opportunity Employer / Individuals with Disabilities / Protected Veterans" which is EEO boilerplate, should be removed. Also "GCI embodies excellence..." is introductory prose about company; could be part of "About the role" maybe. We'll include that as prose under About the role. We need to include a section only when posting has real specific content for it. So we can have: - About the role (intro description) - Responsibilities (list of duties) - Requirements (maybe required skills) - Qualifications (maybe desired skills? Or we could combine required and desired under Skills? The instruction says use headings like Requirements, Qualifications, Skills. We need to decide. We have Required Skills and Desired Skills sections. Could map Required Skills to "Requirements" and Desired Skills to "Qualifications". Or we could have a "Skills" section that includes both required and desired. But we need to follow instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include multiple of those if content exists. We have content for Responsibilities (the long list of duties). We have Required Skills (list). We have Desired Skills (list). We have clearance requirement (US Citizen, TS/SCI with Polygraph). That could be part of Requirements or Qualifications. We also have introductory paragraph about GCI and role. That could be About the role. Thus we can output:

  About the role

  GCI embodies excellence, integrity and professionalism. The employees supporting our customers deliver unique, high-value mission solutions while effectively leverage the technological expertise of our valued workforce to meet critical mission requirements in the areas of Data Analytics and Software Development, Engineering, Targeting and Analysis, Operations, Training, and Cyber Operations. We maximize opportunities for success by building and maintaining trusted and reliable partnerships with our customers and industry. At GCI, we solve the hard problems. As a SME Software Developer, a typical day will include the following duties/skills:

  Then Responsibilities: we need to list duties. The duties start after "Work Requirements". Actually the text after that includes a long list of duties. We'll extract each bullet as
• . The list is long and includes many sentences separated by periods. We need to preserve all substantive information; we should not summarize. So we need to break into list items each representing a duty. The original text: "Work Requirements Perform a review of Customer's secure and unsecure phone system, network and platform hardware, software, network environments and identify individual application and enterprise systems and services that can be modernized or optimized, taking into account the interactions between the application systems and services, and their relationships to Customer core business processes.Assist the Customer to assess lifecycle status, obsolescence, duplication, interoperability, standards alignment, investment dependencies, and modernization opportunities.Identify cross-domain dependencies, gaps, redundancies, constraints, risks, and considerations across infrastructure, applications, data, security, identity, cloud, and network.Evaluate relevant technologies and trends; identify mission-aligned use cases; frame expected value, risk, dependencies, and adoption considerations.Provide technology recommendations to advise and develop the Customers Enterprise technology roadmap, used to predict end of life equipment and tech.Work in partnership with the Chief Architect on future iterations of this roadmap.Provide actionable adoption, sustainment, migration, consolidation, and retirement recommendations for hardware and software.Help prepare decision packages for internal Customer review boards or Customer IT leadership that clearly document outcomes, alternatives, assumptions, dependencies, tradeoffs, costs, risks, technical-debt implications, standards impact, and recommendations.Coordinate technical proposals and recommendations with Customer engineering teams who will partner to develop and deploy the architecture solutions.Deliver concise executive briefings and clearly communicate the overall cost associated (OCA) with proposed architecture and value to Customer including value proposition, available services, decisions influenced, risks reduced, and modernization progress.Develop and maintain enterprise reference architectures, conformance criteria, and exception guidance; develop and maintain current-state, target-state, and transition-state architecture products such as engineering designs.Assess OCA maturity, stakeholder demand, current architecture activities, and capability gaps.Develop and maintain a prioritized list of proposed architecture initiatives with associated costs, intake process, work plan, methods, templates, repository structure, and performance measures.Coordinate products with Customer IT departments, and other program stakeholders, to ensure they are authoritative, reusable, implementable, and operationally supportable.Build automation-heavy workflows and front door experiences for ServiceNow.Implement Flow Designer and Integration Hub patterns to include approvals, routing, notifications, and orchestration.Build and extend catalog items for IT support and service requests; new business requirements intake (demand-style); and security processing requirements (visit requests, access requests, or similar).Support Customer A&A processes; build or extend catalog items for Authorization and Assessment (A&A) tasks; Risk Management Framework (RMF) tasks; or for evidence requests.Support PPM configuration buildouts such as forms, flows, templates.Create reusable subflows such as approval chains, task pack generation, SLA timers, or escalations.Lead process mapping and future-state design for enterprise intake and vetting, demand which support the project lifecycle, RMF A&A lifecycle aligned to Research Development Support Activity (ROSA) RMF SOPs, and security paperwork (visit requests) lifecycle and approval chain.Write user stories and acceptance criteria and manage User Acceptance Testing (UAT).Provide training on ServiceNow custom workflows.Help users adjust to changes related to the implementation or enhancement of a ServiceNow instance with 2.5k users.Provide ServiceNow training, write knowledge base articles, and help to market service now internally to program resources, with a goal of increased adoption of the tool.Facilitate workshops with Customer Security (ISSO or ISSM), system owners, AO reps, or PMO.Create SOPs and quick reference guides." We need to split into list items. Each sentence separated by period (or maybe semicolon). We'll treat each distinct duty as a list item. We'll need to ensure we don't lose any detail. Could be many items; but we can keep them as separate
• . It's okay. Then Requirements: Required Skills list. Each bullet starts with "Enterprise Architecture- Demonstrated experience ..." and many repeats. We need to preserve all. Could list each as
• . There are many repeated lines; we should not deduplicate unless they are duplicated lines (the instruction says remove duplicated lines). Indeed there are many repeated lines: "Enterprise Architecture- Demonstrated experience with enterprise architecture leadership in a complex, federated, regulated, or mission-oriented IT enterprise." appears once? Actually there are multiple similar but each line is slightly different: they list many aspects. They are not exact duplicates but similar pattern. We should keep each line as it is. Then Qualifications: Desired Skills list. Also we need to include clearance requirement: "A candidate must be a US Citizen and requires an active/current TS/SCI with Polygraph clearance." This could be part of Requirements or Qualifications. Probably Requirements. We also need to remove EEO line at end. Now produce HTML fragment. We must not include or . Just the fragment. We'll structure:

  About the role

  ... intro ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...
  We should not include Skills heading separately if we already have Requirements and Qualifications. But we could also include Skills heading combining both? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid having both Requirements and Qualifications and Skills. But we should avoid thin sections. We have substantive content for Requirements and Qualifications, so we can include those. Skills heading maybe redundant. We'll omit Skills. Now we need to ensure we don't include any boilerplate like "Equal Opportunity Employer...". Remove. Now craft the HTML. We need to be careful with escaping any HTML special characters like &, <, >. The text includes parentheses and ampersand? There's "(OCA)" and maybe "&" not present. There's "IC" etc. No problematic characters. There's "TS/SCI". Slash is fine. We'll produce list items as sentences. Need to ensure each
• ends with proper punctuation? Not required. Let's extract responsibilities list items by splitting at periods that are followed by a capital letter or start of new duty. But we can approximate by using the sentences as they appear separated by periods. We'll just copy each sentence as an item. Let's list them: 1. Perform a review of Customer's secure and unsecure phone system, network and platform hardware, software, network environments and identify individual application and enterprise systems and services that can be modernized or optimized, taking into account the interactions between the application systems and services, and their relationships to Customer core business processes. 2. Assist the Customer to assess lifecycle status, obsolescence, duplication, interoperability, standards alignment, investment dependencies, and modernization opportunities. 3. Identify cross-domain dependencies, gaps, redundancies, constraints, risks, and considerations across infrastructure, applications, data, security, identity, cloud, and network. 4. Evaluate relevant technologies and trends; identify mission-aligned use cases; frame expected value, risk, dependencies, and adoption considerations. 5. Provide technology recommendations to advise and develop the Customers Enterprise technology roadmap, used to predict end of life equipment and tech. 6. Work in partnership with the Chief Architect on future iterations of this roadmap. 7. Provide actionable adoption, sustainment, migration, consolidation, and retirement recommendations for hardware and software. 8. Help prepare decision packages for internal Customer review boards or Customer IT leadership that clearly document outcomes, alternatives, assumptions, dependencies, tradeoffs, costs, risks, technical-debt implications, standards impact, and recommendations. 9. Coordinate technical proposals and recommendations with Customer engineering teams who will partner to develop and deploy the architecture solutions. 10. Deliver concise executive briefings and clearly communicate the overall cost associated (OCA) with proposed architecture and value to Customer including value proposition, available services, decisions influenced, risks reduced, and modernization progress. 11. Develop and maintain enterprise reference architectures, conformance criteria, and exception guidance; develop and maintain current-state, target-state, and transition-state architecture products such as engineering designs. 12. Assess OCA maturity, stakeholder demand, current architecture activities, and capability gaps. 13. Develop and maintain a prioritized list of proposed architecture initiatives with associated costs, intake process, work plan, methods, templates, repository structure, and performance measures. 14. Coordinate products with Customer IT departments, and other program stakeholders, to ensure they are authoritative, reusable, implementable, and operationally supportable. 15. Build automation-heavy workflows and front door experiences for ServiceNow.