Sr. Software Architect

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, scam warning, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions. We need to parse the description. Key parts: - Intro: "Leidos has a new and exciting opportunity for a Sr. Software Architect in our INTEL Sector's Cyber & Analytics Business Area (CABA). Our talented team is at the forefront in Security Engineering, Computer Network Operations (CNO), Mission Software, Analytical Methods and Modeling, Signals Intelligence (SIGINT), and Cryptographic Key Management. At Leidos, we offer competitive benefits, including Paid Time Off, 11 paid Holidays, 401K with a 6% company match and immediate vesting, Flexible Schedules, Discounted Stock Purchase Plans, Technical Upskilling, Education and Training Support, Parental Paid Leave, and much more. Join us and make a difference in National Security!" - Then: "The Senior Software Architect will lead the development of new capabilities for a complex, high‑performance system. This role oversees a team of developers, drives high‑level architectural decisions, and manages the full software development process in an Agile environment. The architect collaborates daily with program management, integration, testing, and information assurance teams, serving as the technical expert for system design. Responsibilities include defining architectural direction, evaluating requirements against cost and schedule constraints, and establishing strategies for application monitoring, infrastructure, interfaces, and critical business functions." - Then "Position Responsibilities Will Include" list of responsibilities (multiple sentences). We'll need to extract bullet points. - Then "Option to work a 9/80 work schedule (i.e., 9-hour days, then work 8 hours on first Friday and off the second Friday)." - Then "Required Qualifications" list. - Then "Desired Qualifications" list. - Then "If you're looking for comfort, keep scrolling..." etc (marketing fluff). Might be considered boilerplate? It's not required but maybe we can keep as part of About the role? It's fluff but maybe not needed. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The marketing fluff is not boilerplate but could be considered filler. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The fluff is not substantive? It's more promotional. Might be considered not essential but still part of description. However we can keep it under About the role maybe. - Then "Original Posting September 17, 2026" etc - metadata, we can drop or put in short p. - Then "For U.S. Positions: While subject to change..." etc - maybe drop as boilerplate. - Then "Pay Range Pay Range $131,300.00 - $237,350.00" etc. We need Pay section if posting actually states them. Yes they have pay range. So include Pay section. - Then "About Leidos" etc - maybe not needed but could be About the role? Actually About Leidos is company description; could be part of About the role? But we already have About the role maybe we can include a short paragraph about Leidos as part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role heading and include description of role and maybe company overview. But we should not repeat job title. - Then "Pay And Benefits" section repeats benefits; we already have benefits earlier. We'll need Benefits section. - Then "Securing Your Data" etc - scam warning boilerplate, remove. - Then "Commitment to Non-Discrimination" etc - EEO boilerplate, remove. Thus we need to extract: About the role: maybe combine introductory paragraph about Leidos team and role overview. Responsibilities: list from "Position Responsibilities Will Include" bullet points. Requirements: maybe combine Required Qualifications and Desired Qualifications? But we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings as examples; we need to decide what to put where. Typically Requirements could be mandatory qualifications; Qualifications could be desired; Skills could be technical skills. But we have both Required and Desired qualifications. We could put Required under Requirements, Desired under Qualifications, and technical skills under Skills. However the posting also lists many specific skills under Required Qualifications (experience with tools etc). Those could be considered Skills. But we need to preserve all info; we can split. Let's parse Required Qualifications: - Bachelor's Degree in Computer Science, Software Engineering, or Information Systems or a related field and at least 12+ years of related experience or Master’s Degree with at least 10+ years of relevant experience. Additional experience may be substituted for a Degree. - Security + Certification or will need to achieve within 90 days. - Must have an active Secret clearance and the ability to obtain a TS/SCI - Minimum of 12+ years of experience designing and developing large integrated classified systems. - Minimum of 10+ years of experience leading development teams. - Possess a solid understanding of secure systems architecture and development. - Proven professional experience analyzing code for weaknesses and errors, and overseeing plans to improve them. - Must be comfortable working on multiple systems and components simultaneously in various configurations. - Experience with code development software tools to include: JetBrains CLion, Visual Studio Code, Git and Gitlab Enterprise (repository hosting). - Experience with build and deployment (CI/CD) to include: GitLab Enterprise (CI/CD), CMake and vcpkg. - Experience with application software stacks to include: Qt/QML, C++17, SQLite, NNG and Google Protocol Buffers - Experience with Testing and Quality Assurance to include: Catch2, Clang-Format, CPPLint, FlawFinder, Valgrind and Clang-Tidy. - Experience with database management software, such as MySQL, Oracle RDBMS, and Microsoft SQL Server. - Scripting skills with knowledge of programming languages, such as Perl, Ruby, and Python. - Must be able to effectively plan and prioritize tasking and communicate clearly regarding technical options and trade-offs. - Must be capable of performing systems architecture activities in support of Agile/SCRUM teams. Desired Qualifications: - Good knowledge of networking protocols, such as TCP, IP, and OSI models. - Understanding of Cryptography - Familiarity with SKLs and ECUs Skills: maybe we can extract the specific tools etc as Skills. But we also have Benefits: list from intro: Paid Time Off, 11 paid Holidays, 401K with a 6% company match and immediate vesting, Flexible Schedules, Discounted Stock Purchase Plans, Technical Upskilling, Education and Training Support, Parental Paid Leave, and much more. Also Pay: range $131,300.00 - $237,350.00. Schedule: Option to work a 9/80 work schedule. Now we need to output HTML fragment with headings

and content using

for prose and

• for lists. We must not include empty sections. Let's craft:

  About the role

  Leidos is seeking a Sr. Software Architect for the INTEL Sector's Cyber & Analytics Business Area (CABA). The team works on Security Engineering, Computer Network Operations (CNO), Mission Software, Analytical Methods and Modeling, Signals Intelligence (SIGINT), and Cryptographic Key Management. Leidos offers competitive benefits including Paid Time Off, 11 paid Holidays, 401K with a 6% company match and immediate vesting, Flexible Schedules, Discounted Stock Purchase Plans, Technical Upskilling, Education and Training Support, Parental Paid Leave, and more. The Senior Software Architect will lead development of new capabilities for a complex, high‑performance system, oversee a team of developers, drive high‑level architectural decisions, manage the full software development process in an Agile environment, collaborate daily with program management, integration, testing, and information assurance teams, and serve as the technical expert for system design.

  But note we already have Benefits section separate; we might not repeat benefits in About the role to avoid duplication. However the instruction says preserve ALL substantive information; we can keep benefits in Benefits section and not duplicate. But we can keep a brief mention that benefits are offered; but better to avoid duplication. However the About the role paragraph could be just role overview without benefits. Let's keep About the role focusing on role and team. Thus:

  About the role

  Leidos is seeking a Sr. Software Architect for the INTEL Sector's Cyber & Analytics Business Area (CABA). The team works on Security Engineering, Computer Network Operations (CNO), Mission Software, Analytical Methods and Modeling, Signals Intelligence (SIGINT), and Cryptographic Key Management. The Senior Software Architect will lead the development of new capabilities for a complex, high‑performance system, oversee a team of developers, drive high‑level architectural decisions, manage the full software development process in an Agile environment, collaborate daily with program management, integration, testing, and information assurance teams, and serve as the technical expert for system design.

  Now Responsibilities: extract bullet points from "Position Responsibilities Will Include". Let's list each sentence as a bullet. Original text after that heading: "Designs, develops, documents, tests and debugs applications software and systems that contain logical and mathematical solutions. Conducts multidisciplinary research and collaborates with equipment designers and/or hardware engineers in the planning, design, development, and utilization of electronic data processing systems for product and commercial software. Determines computer user needs; analyzes system capabilities to resolve problems on program intent, output requirements, input data acquisition, programming techniques and controls; prepares operating instructions; designs and develops compilers and assemblers, utility programs, and operating systems. Formulate software designs that create solutions meeting various desired outcomes (both current and future) while balancing the goals and constraints on the solutions (i.e. customer environment, cybersecurity, continuous integration/continuous delivery (CI/CD), etc.). Manage change to the software architecture and control software complexity. Make software architecture and solutions as flexible as possible. Defend against, when appropriate, suggested changes to the software architecture that introduce undue complexity or future supportability issues. Assist with trade off analyses of increased complexity. Oversee and support the coaching and training of team members to ensure all necessary employees are confident in the use of software applications. Participate and lead discussions at customer meetings, working groups, and technical interchange meetings associated with the work performed in this project." We'll turn each line into
• . Now Requirements: we could put mandatory qualifications (Required Qualifications) as a list. But we also have Skills section for technical skills. Let's decide: - Requirements: education/experience, clearance, Security+, years experience leading teams, understanding of secure systems architecture, code analysis, comfort with multiple systems, planning/prioritization, Agile/SCRUM support. - Qualifications: maybe Desired Qualifications (networking protocols, cryptography, SKLs/ECUs). - Skills: specific tools/experience lists (code development tools, CI/CD, application stacks, testing/QA, database management, scripting languages). We need to ensure we don't lose any info. Let's extract Required Qualifications items: 1. Bachelor's Degree in Computer Science, Software Engineering, or Information Systems or a related field and at least 12+ years of related experience or Master’s Degree with at least 10+ years of relevant experience. Additional experience may be substituted for a Degree. 2. Security + Certification or will need to achieve within 90 days. 3. Must have an active Secret