Senior Systems Engineer - TS/SCI

We need to output HTML fragment with sections only where there is real content. Must use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove application instructions. The posting includes location, security clearance, responsibilities, minimum requirement, preferred qualification, about Xcelerate Solutions (company description). Also includes "Location: Bethesda, MD (Hybrid)" and "Security Clearance: TS/SCI". Those could be part of "About the role" maybe. We need to decide sections. We have content for: - About the role: description of role, mission, impact, team, location, hybrid, security clearance. - Responsibilities: list of responsibilities. - Requirements: Minimum Requirement (education/experience, clearance, etc.) - Qualifications: Preferred Qualification list. - Skills: maybe combine? The posting includes many skill items in both requirements and preferred. Could treat "Skills" as a section summarizing technical skills? But we must only include sections if posting has real specific content. The posting includes many skill items; we could put them under "Skills". However we already have Requirements and Qualifications sections; we could also have Skills if there is distinct skill list not covered. But we can also merge skill items into Requirements/Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one? But they ask to use headings for those specific names if content exists. We have content for Requirements (minimum requirement) and Qualifications (preferred). So we should include both. Skills: The posting includes many skill items but they are already within Requirements and Preferred Qualification. Could still create a Skills section but might be thin duplication. Better to not create Skills unless there is distinct skill list not already covered. Since the posting includes skill items in both sections, we could omit Skills. Benefits, Pay, Schedule: The posting mentions flexible schedule, occasionally remote, but no explicit benefits, pay, or schedule details. It says "we offer a flexible schedule and, occasionally, some tasks may be performed remotely." That's schedule info. So we could include a Schedule section with that sentence. Benefits: not mentioned. Pay: not mentioned. So we omit Benefits and Pay. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. We need to use

for each heading. Use

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

  for prose. We must preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines. Let's extract content. About the role: The first paragraph(s) before Responsibilities. Original: "Senior Systems Engineer (Hybrid) - TS/SCI Xcelerate Solutions has an exciting opening for you, as our next TS/SCI cleared Senior Systems Engineer, to play a critical role with design, engineering, development and deployment of software supporting the DIA-NMEC (National Media Exploitation Center) DOMEX Technology Platform (DTP). Under this 10-year contract containing multiple Task Orders, we support the DOMEX Data Discovery Platform (D3P) Modernization program as well as DIA-OSIC’s mission to centralize and standardize Tasking, Collection, Processing, Exploitation and Dissemination (TCPED) of Open Source Intelligence (OSINT) across the DoD and IC enterprise. This position provides an opportunity to have impact as part of a mission focused, solutions oriented, and adaptive team that values innovation, collaboration, and professional development. The selected individual will work closely with the Lead Systems Engineer, Release Train Engineer, and government leads to decompose high priority requirements from the product roadmap into valuable delivered solutions, executing on requirements analysis, design, system integration, and system testing. As a Senior Systems Engineer you will lead an application team responsible for maintaining the continuous flow of new software enhancements and deployments, while you manage risks, escalate impediments, and help to drive continuous process improvement. While most work is conducted on-site at our client location in Bethesda, MD, we offer a flexible schedule and, occasionally, some tasks may be performed remotely. Come join our award-winning organization and work with some of the most talented and brightest minds in the GovCon industry." Also includes "Location: Bethesda, MD (Hybrid)" and "Security Clearance: TS/SCI". Those could be included in About the role as prose. We must not repeat job title as heading, but we can include it in prose? Probably okay. We'll create About the role paragraph(s) combining all that. Responsibilities: list after "Responsibilities". It starts with "Manage, direct, coordinate, and provide technical direction for all aspects of the team’s development efforts." then many sentences each ending with period. Some are long. We need to turn each duty into

• . We must preserve all substantive information; not summarize. So each sentence becomes a list item. However some sentences contain multiple duties separated by commas; but we can keep as is. We need to extract each bullet. Let's copy the responsibilities block: "Manage, direct, coordinate, and provide technical direction for all aspects of the team’s development efforts. Plan, design, and oversee implementation of software development solutions. Provide technical support, coordination, and execution of systems engineering activities such as feature/requirements analysis, design, implementation planning, integration and test, sustainment, documentation, deployment, and system assessment. Ensure sound engineering practices are followed. Provide direction for interpretation and application of policies and procedures to the engineering and development activitiesDevelop a working knowledge of government business processes and provide recommendations accordingly. Collaborate with other development teams to identify and develop high-value integrations with other systems/applications. Develop, manage and continually improve the backlog of work items for an Agile scrum team. Update and prioritize stories and epics via feedback from various program stakeholders ensuring the team is always working on the highest-value tasks. Support Scaled Agile Framework (SAFe) program increment planning and execution through creation of work tickets in GitLab as well as program/system documentation using collaboration software (e.g., GitLab wiki). Lead/participate in all Agile ceremonies to include daily stand up, planning, reviews, and retrospectives. Stay informed of increment and sprint progress and work with the team to identify and remove impediments and dependencies. Perform backlog refinement on a regular basis. This may include decomposing features into workable stories, prioritizing or reprioritizing items in the backlog for upcoming sprints, refining acceptance criteria and complexity estimates or removing tickets that are no longer relevant. Accept or reject completed work based on defined acceptance criteria to ensure delivery of high-quality software. Lead the design and architecture of backend systems and services. Drive initiatives across the engineering team related to scalability, reliability, and performance. Develop requirements and design documents Contribute to and review RFCs, and requirements, design, and architecture reviews Coordinate with Test Team to develop and monitor automated system integration tests to identify failed modules and components Manage individual project priorities, deliverables, and deadlines Provides specific input to the software components of system design to include hardware/software trade-offs, software reuse, use of COTS/GOTS in place of new development, and requirements analysis and synthesis from system level to individual software components Foster an environment of collaboration with the different team members in the goal of providing quality service and product to our customers Act as a mentor to mid-level and junior engineers, offering guidance on best practices and career growth" Note there are some formatting issues: missing periods, some lines run together. We'll keep as is but ensure each line is a list item. We need to ensure we don't lose any content. We'll treat each line as an item. Requirements: Minimum Requirement block: "Minimum Requirement BS in Engineering, Computer Science, Systems Engineering, or related field and 12 – 15 years of prior relevant experience or Masters with 10 – 13 years of prior relevant experience. Additional years of experience in lieu of degree are acceptableMust have an active Top Secret security clearance with the ability to obtain and maintain a TS/SCI with Polygraph. Software development experience in languages such as Java or Python. Experience as a Systems Enginer, Product Owner, or a similar role in an Agile software development team. Experience with requirements and design documentation, including process flow diagrams. Demonstrated ability to break down complex problems into actionable steps. Experience managing and prioritizing product backlogs effectively. Strong understanding of Agile methodologies, and experience with tools like Gitlab, Jira, and Confluence. Experience with facilitating scrum for the team (Planning, Retrospective, Grooming & Review/Demo). Excellent communication skills (verbal and written) to articulate technical and non-technical concepts to diverse audiences. Proven ability to work cross-functionally with engineering, design, and project management teams. Demonstrated ability to manage expectations and maintain strong relationships with government and contractor stakeholders." We need to split into list items. Each sentence separated by period. However some sentences lack period (like "Additional years of experience in lieu of degree are acceptableMust have..."). We'll need to separate logically. Let's break: - BS in Engineering, Computer Science, Systems Engineering, or related field and 12 – 15 years of prior relevant experience or Masters with 10 – 13 years of prior relevant experience. - Additional years of experience in lieu of degree are acceptable. - Must have an active Top Secret security clearance with the ability to obtain and maintain a TS/SCI with Polygraph. - Software development experience in languages such as Java or Python. - Experience as a Systems Engineer, Product Owner, or a similar role in an Agile software development team. (Note typo "Enginer" but we keep as is? Should we preserve original text? It says "Systems Enginer". We must preserve ALL substantive information; do not invent or summarize away detail. Should we keep the typo? Probably yes, we must keep as is. So "Experience as a Systems Enginer, Product Owner, or a similar role in an Agile software development team." - Experience with requirements and design documentation, including process flow diagrams. - Demonstrated ability to break down complex problems into actionable steps. - Experience managing and prioritizing product backlogs effectively. - Strong understanding of Agile methodologies, and experience with tools like Gitlab, Jira, and Confluence. - Experience with facilitating scrum for the team (Planning, Retrospective, Grooming & Review/Demo). - Excellent communication skills (verbal and written) to articulate technical and non-technical concepts to diverse audiences. - Proven ability to work cross-functionally with engineering, design, and project management teams. - Demonstrated ability to manage expectations and maintain strong relationships with government and contractor stakeholders. Now Qualifications (Preferred Qualification): "Preferred Qualification Experience with Kafka or other message passing systemsExperience on a production/enterprise systemCloud infrastructure experienceExperience with Appian or other low-code software technologiesExperience with any of the following technologies:PostgreSQLContainerization, especially with DockerDevOps practices and tools including Continuous Integration/Continuous Delivery (CI/CD) tools and practices, especially Gitlab or JenkinsGraphQLKeycloakProactive in identifying tech debt, systemic issues, and areas for team/process improvementExpertise building and maintaining microservices in production in KubernetesUnderstanding of Elasticsearch internals: sharding, performance tuning, analyzers, query DSLElasticsearch certifications or other program stack related certificationsStrong Kafka experience: event design, stream processing, performance tuningFamiliarity with schema registries and Kafka streaming patternsFamiliarity with authentication and authorization products such as KeycloakExperience with security best practices for services: authN/Z, secrets management, data protectionGraphQL familiarityHardware on-prem and cloud-based deployments using KubernetesProficiency with infrastructure-as-code (ie CloudFormation, Terraform, Pulumi)Experience of a production/enterprise systems at scaleKnowledge of distributed systems concepts (e.g., idempotency, eventual consistency)Experience leading technical projects and mentoring engineersStrong testing discipline with