Director, DevSecOps Engineering

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines, application instructions. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Job Schedule: 9/80 description. Also includes salary range (Pay). Benefits: mentions variety of benefits. So we can include Benefits, Pay, Schedule sections. We need sections: About the role (maybe from job description paragraph). Responsibilities (Essential Functions). Requirements (maybe Qualifications? Actually Qualifications is separate). Skills (Preferred Additional Skills). Qualifications (the qualifications). Benefits, Pay, Schedule. We must not include headings with filler. Ensure each section has content. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists where appropriate. We must not repeat job title as heading. So no heading for Director, DevSecOps Engineering. We must not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

  or drop it. The Job Code and location maybe we can include in a short paragraph under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location and maybe job code in a short paragraph. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out all the EEO paragraphs, drug-free workplace, E-Verify, etc. We must preserve substantive info: job description, essential functions, qualifications, preferred additional skills, benefits, pay, schedule. We need to be careful not to lose any detail. Let's extract. Job Title: Director, DevSecOps Engineering (not used as heading). Job Code: 44684 (minor metadata). Job Location: Camden, NJ; Millersville, MD; Palm Bay, FL. Job Schedule: 9/80: Employees work 9 out of every 14 days totaling 80 hours worked and have every other Friday off. Job Description: paragraph: "In a fast moving and increasingly complex world, L3Harris is anticipating and rapidly responding to challenges with agile technology – creating a safer and more secure future. Join our trailblazing Maritime team, where you'll dive into the thrilling world of high-assurance encryption products. We are seeking a software engineering leader to drive adoption and disciplined execution of agile software engineering practices across the Maritime Sector. This role will help shape the software engineering approach within our Maritime businesses, advise engineering leadership on best practices, and partner with programs to improve efficiency, consistency, and execution of software development." Essential Functions (list): Build an engineering pipeline to facilitate efficient, traceable, low defect, high-quality software development in our encryption business and beyond. Define, implement, and continuously improve software engineering processes, practices, standards, tools, and governance across multiple encryption programs and teams. Advise engineering and business leadership on software engineering strategy, process maturity, organizational capability, and execution improvement opportunities. Provide guidance and oversight to software teams throughout the software development lifecycle. Evaluate current software engineering performance across programs, identify systemic gaps and risks, and lead actions to improve effectiveness, quality, and predictability. Review and influence software development plans, technical approaches, cost and schedule estimates, proposals, and program startup activities to ensure alignment with software engineering best practices. Use data‑driven analysis to assess software engineering health, monitor organizational performance, and recommend and implement continuous improvement actions. Mentor technical leaders and engineering teams. Foster a culture of accountability, technical excellence, collaboration, and continuous improvement across the software engineering discipline. Travel up to 15%. Valid driver’s license if travel requires site access or local transportation. Qualifications: Bachelor’s degree in Computer Science, Software Engineering, Computer Engineering, Electrical Engineering, or a related technical field and a minimum of 15 years of prior relevant experience, or a graduate degree and a minimum of 13 years of prior related experience. In lieu of a degree, a minimum of 19 years of prior related experience. Broad and progressive software engineering experience, including significant leadership responsibility across multiple teams, programs, or organizational units. Ability to influence senior engineering, program, and business leaders and drive change across functional and program boundaries. Strong knowledge of the full software development lifecycle, including requirements capture, software architecture, design, coding, integration, test, release, and sustainment. Experience implementing AI and automation into software development and deployment pipelines in both classified and unclassified infrastructures. Experience with Agile, DevSecOps, digital engineering, model‑based development, automated test, and secure software development practices. Familiarity with software engineering governance, lifecycle compliance, peer review rigor, development metrics, and engineering performance measurement. Verbal, written, interpersonal, and presentation skills to communicate effectively with both technical and executive audiences. Experience operating in a regulated, mission‑critical, or highly disciplined engineering environment. Active and existing U.S. DoD Secret security clearance required to start. Preferred Additional Skills: Advanced degree in Computer Science, Software Engineering, Engineering Management, or a related technical discipline. Experience in defense, aerospace, secure communications, encryption, embedded systems, or other highly regulated environments. Experience leading software engineering process improvement initiatives across an organization, business area, or portfolio. Experience supporting proposal, capture, program startup, and execution planning activities with strong software engineering cost, schedule, and staffing inputs. Experience in one of the following technology areas: Software engineering pipelines; RESTful API service design; Real‑time embedded software development and embedded interfaces (I2C, RS232, CAN, Ethernet); VoIP systems, SIP‑based call control, or real‑time media applications; Networking basics, such as HTTPS and websockets. Pay: "In compliance with pay transparency requirements, the salary range for this role in California, Connecticut, Massachusetts, New Jersey, Washington, and the Greater D.C. area, Denver, or NYC areas is $194,500 - $361,500. The salary range for this role in Colorado state, Hawaii, Illinois, Maine, Maryland, Minnesota, New York state, Cleveland Ohio, Vermont and Virginia is $194,500 - $361,50." There's a typo: $361,50 missing a zero? Probably $361,500. We'll keep as written but note it's likely a typo. We must preserve exactly as posted? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the text exactly as given, including the typo. So we include both ranges. Benefits: "L3Harris also offers a variety of benefits, including health and disability insurance, 401(k) match, flexible spending accounts, EAP, education assistance, parental leave, paid time off, and company-paid holidays. The specific programs and options available to an employee may vary depending on date of hire, schedule type, and the applicability of collective bargaining agreements." We should not include the LI-LS2 tag etc. Now we need to output HTML fragment. Structure:

  About the role

  ... include job description paragraph plus maybe location and job code as short p.

  But we need to decide: Should we include location and job code in About the role? Probably yes as minor metadata. We can do:

  Job Code: 44684. Locations: Camden, NJ; Millersville, MD; Palm Bay, FL.

  Then the job description paragraph. Alternatively we could combine into one p. We must not repeat job title as heading. Now Responsibilities: use
  • for each essential function. Requirements: maybe we treat Qualifications as Requirements? But we have separate Qualifications section. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need both Requirements and Qualifications sections. The posting has "Qualifications:" and also "Preferred Additional Skills:" which could be Skills. There's no explicit "Requirements" separate from Qualifications. But we could treat the qualifications as Requirements? However we have both Qualifications and Skills sections. The posting includes "Qualifications:" (the mandatory) and "Preferred Additional Skills:" (preferred). So we can map: - Requirements: maybe the mandatory qualifications? But we already have Qualifications section for that. The instruction says we can include sections only when posting has real specific content. So we need to decide what goes into Requirements vs Qualifications. The posting does not have a separate "Requirements" heading; but we could treat the mandatory qualifications as Requirements and the "Qualifications" heading as maybe duplicate? Actually the posting uses "Qualifications:" as the heading for mandatory qualifications. So we could map that to Qualifications section. Then what about Requirements? Could be empty; we should not include a Requirements section if no specific content. So we omit Requirements. Similarly Skills: we have Preferred Additional Skills, so we can map to Skills section. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule. We must not include Requirements. Now we need to ensure we use

    • for any list of duties/requirements/benefits. For Qualifications, it's a list of items; we can make a
      . For Skills, also a
      . For Benefits, also a
      . For Responsibilities, also a
      . For Pay and Schedule, we can use

      as they are prose. Now we need to preserve all substantive info. Let's extract each piece. About the role: include job code and location, plus job description paragraph. Job description paragraph: "In a fast moving and increasingly complex world, L3Harris is anticipating and rapidly responding to challenges with agile technology – creating a safer and more secure future. Join our trailblazing Maritime team, where you'll dive into the thrilling world of high-assurance encryption products. We are seeking a software engineering leader to drive adoption and disciplined execution of agile software engineering practices across the Maritime Sector. This role will help shape the software engineering approach within our Maritime businesses, advise engineering leadership on best practices, and partner with programs to improve efficiency, consistency, and execution of software development." We'll keep that exactly. Now Responsibilities: list each essential function as

      • . Need to preserve the exact phrasing. Essential Functions list: - Build an engineering pipeline to facilitate efficient, traceable, low defect, high-quality software development in our encryption business and beyond. - Define, implement, and continuously improve software engineering processes, practices, standards, tools, and governance across multiple encryption programs and teams. - Advise engineering and business leadership on software engineering strategy, process maturity, organizational capability, and execution improvement opportunities. - Provide guidance and oversight to software teams throughout the software development lifecycle. - Evaluate current software engineering performance across programs, identify systemic gaps and risks, and lead actions to improve effectiveness, quality, and predictability. - Review and influence software development plans, technical approaches, cost and schedule estimates, proposals, and program startup activities to ensure alignment with software engineering best practices. - Use data‑driven analysis to assess software engineering health, monitor organizational performance, and recommend and implement continuous improvement actions. - Mentor technical leaders and engineering teams. - Foster a culture of accountability, technical excellence, collaboration, and continuous improvement across the software engineering discipline. - Travel up to 15%. - Valid driver’s license if travel requires site access or local transportation. We need to keep the hyphen and en dash etc. We'll copy