Senior DevSecOps Engineers

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 need to parse the job description. Key parts: - Job Description: Type of Requisition: Regular Clearance Level Must Currently Possess: None Clearance Level Must Be Able To Obtain: None Other Public Trust/Other Required: Job Family: Cyber and IT Risk Management Skills: Job Qualifications: Apache Tomcat, JavaScript, Linux, Security Standards, Software Development Life Cycle (SDLC) Certifications: None Experience: 5 + years of related experience US Citizenship Required: No But we should not repeat job title as heading. The page already shows it. So we start with maybe "About the role" section containing the description paragraph(s) after "Job Description: SR DEVSECOPS ENGINEER ..."? Actually the description includes a paragraph about AOUSC, responsibilities, etc. We'll need to extract substantive info. We need sections: - About the role: could contain the paragraph describing the role, mission, etc. - Responsibilities: list of responsibilities (bulleted). The posting has a big block under RESPONSIBILITIES with many sentences separated by line breaks? We'll need to turn each sentence into

. - Requirements / Qualifications: The posting has "REQUIRED EXPERIENCE & QUALIFICATIONS" with bullet-like list. Also there is "Job Qualifications:" earlier listing skills: Apache Tomcat, JavaScript, Linux, Security Standards, SDLC. Also "Skills:" earlier? There's "Skills:" after Job Family. Might be duplicate. We need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: "The likely salary range for this position is $114,750 - $155,250." That's specific, so include Pay section. Schedule: "Scheduled Weekly Hours: 40" and maybe "Telecommuting Options: Remote Work Location: Any Location / Remote". Also "Travel Required: None". So schedule info includes weekly hours, remote, travel. So we can include Schedule section. Benefits: There's a big block under "Total Rewards At GDIT:" describing benefits. So include Benefits section. Skills: There's a list of skills: Apache Tomcat, JavaScript, Linux, Security Standards, SDLC, also C, Java, JSF, PrimeFaces, JavaScript, CSS, Linux shell, etc. Also "Strong experience implementing and supporting end-to-end automated DevSecOps pipelines and processes", etc. But many of those are in responsibilities/qualifications. We could still have a Skills section summarizing technical skills. However we must avoid filler. We have explicit skill list earlier: "Job Qualifications: Apache Tomcat, JavaScript, Linux, Security Standards, Software Development Life Cycle (SDLC)". Also later "Proficient skills in C, Java, JSF, Tomcat, PrimeFaces, JavaScript, CSS, and/or Linux shell". Also "Strong experience in RedHat Linux". Also "Strong experience with providing engineering support for software application in the full DevOps pipeline". Also "Experience with DevOps tools (Jira, Confluence, GitLab CI/CD, GitHub Actions, Jenkins, Bash, Subversion, JetBrains Tool Suite)". Also "Experienced in providing DevSecOps implementation using Jenkins, Gitlab, or similar tools". Also "Experienced in developing, testing, and maintaining containerized applications". Also "Working knowledge of source version control, build/release tools and methodologies, and CI/CD pipelines". Also "Working knowledge of Software Build process." Also "Strong 'security first' mindset". Also "In-depth knowledge of agile methodologies". Also "Preferred: Perl". Also "Excellent presentation and communication skills." etc. We could create a Skills section that consolidates these. But we must not repeat content verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep the info, but we can reorganize into sections. It's okay to list skills in a

• under Skills section, as long as we don't lose detail. However we must ensure we don't lose any detail; we can duplicate info across sections? Probably okay but better to keep each piece in appropriate section. For example, responsibilities section already includes many of those tasks; skills section could list technical skills and tools. That's fine. We need to avoid creating sections with filler like "commensurate with experience". We have specific pay range, so Pay section is valid. Schedule: we have weekly hours 40, remote, travel none. That's specific. Benefits: we have detailed description. Now we need to output HTML fragment only, no or . Use

  for headings. Use

  • for lists. Use

    for prose. We must not include job ID/requisition numbers as headings; we can put metadata in a short

    or drop it. The "Type of Requisition: Regular Clearance Level Must Currently Possess: None Clearance Level Must Be Able To Obtain: None Other Public Trust/Other Required: Job Family: Cyber and IT Risk Management" could be considered metadata; we could drop it or put in a short p under About the role maybe. But we should preserve ALL substantive information; dropping it might lose info. However the instruction says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." So we can fold minor metadata into a short

    . So we can include a short paragraph at top maybe under About the role or before sections containing that metadata. But we also have "Job Description: SR DEVSECOPS ENGINEER" which is the title; we should not repeat as heading. So we can start with a

    containing the metadata: "Type of Requisition: Regular; Clearance Level: None required; Job Family: Cyber and IT Risk Management." etc. Then About the role: we can have a paragraph describing the role: "Seize your opportunity to make a personal impact supporting the Administrative Office of the United States Courts (AOUSC). The AOUSC is responsible for providing oversight, supervision, and coordination of the court and judicial case management systems. These systems include the Judiciary’s Case Management/Electronic Case Files (CM/ECF) and Public Access to Court Electronic Records (PACER) systems. The Senior DevSecOps Engineer will work as part of the PACER Development team responsible for developing, operating, and supporting internal and external systems that allow for secure public access to court electronic records for the Judiciary." That seems good. Responsibilities: we need to list each bullet. The responsibilities block is a long paragraph with many sentences separated by line breaks? We'll split by sentences that start with a verb. We'll create

  • for each. Let's extract responsibilities sentences: - Develop, maintain, and support products such as PACER account registration and management, PACER authentication, PACER billing and the PACER Case Locator as well as internal systems such as PACER Account Maintenance System, PSC Help Desk Support application, and Court PACER access reports - Monitor continued compliance with Payment Card Industry (PCI) and other security standards through secure development practices - Conduct requirements gathering, design, analyze, develop, test, deploy, support, and maintain systems across the software development lifecycle - Develop and maintain enterprise-class software systems using C, Java, JSF, PrimeFaces, JavaScript, CSS, and/or Linux shell - Develop secure web services utilizing standards such as SOAP, REST, WSDL, XSD, XML, and/or JSON - Independently and collaboratively design and create efficient, scalable and resilient software solution - Create and document use cases, test cases, and system validation results - Participate in an Agile work environment including planning, retrospectives, demos, and stand-ups - Review and validate functional requirements, system description, and design artifacts and prepare complete documentation packages - Review project related documentation and modification requests and provide impact/feasibility analysis - Define, document, and maintain system and software architectures, ensuring alignment with enterprise standards and supporting integration across internal and external system - Implement secure engineering practices, vulnerability remediation, and compliance activities such as ATO, PCI, and FISMA - Conduct performance analysis, capacity planning, and system tuning; design and test continuity of operations (COOP) and disaster recovery (DR) capabilities - Manage Software configurations, version control, and source code repositories; participate in change control process - Provide knowledge transfer, training, and documentation for Technical Points of Contact - Evaluate and recommend emerging technologies, frameworks, and tools to improve efficiency, reduce technical debt, and sustain system viability We'll put each as
  • . Requirements: The posting has "REQUIRED EXPERIENCE & QUALIFICATIONS" with bullet-like list. Let's extract: - 5+ years of experience in IT system engineering, systems development, systems coding and programming - Bachelor’s degree in computer science, Software Engineering, or related field - Comprehensive knowledge of security compliance and security control - Proficient skills in C, Java, JSF, Tomcat, PrimeFaces, JavaScript, CSS, and/or Linux shell - Strong experience implementing and supporting end-to-end automated DevSecOps pipelines and processes - Strong experience in RedHat Linux - Strong experience in and understanding of Cloud APIs and Cloud technologies with some programing experience - Strong experience with providing engineering support for software application in the full DevOps pipeline - Demonstrated ability to adapt to different enterprise security requirements. - Experience with DevOps tools (Jira, Confluence, GitLab CI/CD, GitHub Actions, Jenkins, Bash, Subversion, JetBrains Tool Suite) - Experience as platform team developer who develops and manages the CI/CD pipelines of a wide variety of applications - Experienced in providing DevSecOps implementation using Jenkins, Gitlab, or similar tools - Experienced in developing, testing, and maintaining containerized applications - Working knowledge of source version control, build/release tools and methodologies, and CI/CD pipelines - Working knowledge of Software Build process. - Strong "security first" mindset - Strong experience in and understanding of Cloud APIs and Cloud technologies with some programing experience (duplicate? appears twice) - In-depth knowledge of agile methodologies - Preferred: Perl We need to avoid duplication; but we can keep as is; maybe combine duplicates. Qualifications: earlier there is "Job Qualifications: Apache Tomcat, JavaScript, Linux, Security Standards, Software Development Life Cycle (SDLC)". That's basically a subset of skills; we could treat that as Qualifications section maybe overlapping with Requirements. But we need to decide which sections to include: Requirements, Qualifications, Skills. The instruction says use headings for those if they have real specific content. We have content for Requirements (the list). Qualifications maybe the degree and experience? Actually the "Job Qualifications:" line is a list of specific technologies; that could be considered Skills. The "Skills:" line earlier maybe also. To avoid redundancy, we could have: - About the role - Responsibilities - Requirements (includes experience, education, security knowledge, DevOps experience, etc.) - Skills (technical skills: languages, frameworks, tools, Cloud, etc.) - Benefits - Pay - Schedule We can omit Qualifications if its content is covered elsewhere. But we need to preserve all substantive info; if we omit Qualifications heading but include its content under Skills or Requirements, that's fine as long as we don't lose info. The "Job Qualifications: Apache Tomcat, JavaScript, Linux, Security Standards, SDLC" is a list of specific technologies; we can include those under Skills. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now we need to format. We'll start with a

    for metadata: maybe "Type of Requisition: Regular; Clearance Level