Sr Software Developer

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "About Us" maybe? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. Given posting: - Estimated Starting Salary Range: USD $127,650.00/Yr. - USD $212,750.00/Yr. Salary to be determined by education, experience, knowledge, skills, and abilities of the applicant, internal equity, and alignment with market data. - Description: Designing, developing, and deploying a continually evolving line of products capable of producing synthetic scenarios within Live, Virtual, and Constructive (LVC) environments to drive the simulation of systems during training, testing, and analysis; Leading a team of SW developers and sit on-site alongside team and government personnel; FILLING THIS POSITION IS CONTINGENT UPON AWARD - Requirements: Bachelor's degree in computer science, computer engineering, software engineering, or systems engineering and 12 years of SW development experience; Eight or more years of experience leading teams of SW developers; Nine or more years of experience writing code in Java and JavaScript and C++; Four or more years of experience deploying and managing VMs in VMware ESXi; TS/SCI clearance - Desired Skills: Experience using Jira, Confluence, Bitbucket, Artifactory, and Jenkins; Experience performing software engineering production across the complete DevSecOps lifecycle of a project; Experience providing obsolescence-engineering support to provide replacement EoL/EoS COTS, FOSS, and GOTS SW; Experience in creating and maintaining Software Design Description (SDD), Software Requirements Specification (SRS), Interface Design Description (IDD), and Interface Requirements Specification (IRS) documentation; Experience in Information Operations (IO)/Information Warfare (IW)/Signal Intelligence (SIGINT); Experience leading a team of developers on an SCI project - Clearance Information: SRC IS A CONTRACTOR FOR THE U.S. GOVERNMENT, THIS POSITION WILL REQUIRE U.S. CITIZENSHIP AS WELL AS, A U.S. GOVERNMENT SECURITY CLEARANCE AT THE TOP SECRET / SCI LEVEL - Travel Requirements: N/A (should not include because it's N/A) - About Us: Scientific Research Corporation is an advanced information technology and engineering company that provides innovative products and services to government and private industry, as well as independent institutions. At the core of our capabilities is a seasoned team of highly skilled engineers and scientists with multidisciplinary backgrounds. This team is challenged daily to provide cutting edge technology solutions to our clients. SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick paid time off accruals with amounts increasing based on role and years of service, 11 paid holidays, tuition reimbursement, and a work environment that encourages excellence and more. For positions requiring a security clearance, selected applicants will be subject to a government security investigation and must meet eligibility requirements for access to classified information. - EEO boilerplate etc to remove. We need to decide sections: - About the role: Could be description (Designing, developing, deploying... leading team... contingent upon award). That's the role description. - Responsibilities: Might be same as description? Could separate responsibilities: designing, developing, deploying products; leading team; sit on-site; contingent upon award. But we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine description and responsibilities into one section maybe "About the role". Or we could have "Responsibilities" separate if we have distinct bullet list. Let's see: The posting includes description paragraph and then bullet-like statements: "Designing, developing, and deploying a continually evolving line of products capable of producing synthetic scenarios within Live, Virtual, and Constructive (LVC) environments to drive the simulation of systems during training, testing, and analysis" and "Leading a team of SW developers and sit on-site alongside team and government personnel" and "FILLING THIS POSITION IS CONTINGENT UPON AWARD". Those could be responsibilities. Thus we could have:

About the role

Designing, developing, and deploying a continually evolving line of products capable of producing synthetic scenarios within Live, Virtual, and Constructive (LVC) environments to drive the simulation of systems during training, testing, and analysis. Leading a team of SW developers and sitting on-site alongside team and government personnel. Filling this position is contingent upon award.

Alternatively, we could have Responsibilities as a

• list. But we need to avoid thin sections. Let's decide: Use About the role for overview, Responsibilities for bullet list of duties, Requirements for education/experience, Qualifications maybe for clearance? Actually Qualifications often includes education/experience; but we have Requirements already. Could treat Requirements as qualifications. But we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for: - About the role: maybe a brief summary (the description paragraph). Could be the first sentence. - Responsibilities: bullet list of duties (designing..., leading team..., sit on-site..., contingent upon award). - Requirements: education and experience (Bachelor's degree..., 12 years SW dev..., 8+ years leading teams..., 9+ years Java/JS/C++, 4+ years VMware ESXi, TS/SCI clearance). Also US citizenship maybe. - Qualifications: maybe clearance and citizenship? But we already have clearance in Requirements. Could treat Qualifications as "TS/SCI clearance, US citizenship". However we need to avoid duplication. Perhaps we can put clearance under Requirements and not have Qualifications. But we must only include sections when posting has real specific content. If we don't have distinct content for Qualifications, we should omit it. - Skills: desired skills list (Jira, Confluence, Bitbucket, Artifactory, Jenkins; DevSecOps lifecycle; obsolescence-engineering support; SDD/SRS/IDD/IRS documentation; IO/IW/SIGINT; leading team on SCI project). - Benefits: from About Us: medical, dental, vision plans; 401(k) with company match; life insurance; vacation and sick paid time off accruals increasing based on role and years of service; 11 paid holidays; tuition reimbursement; work environment encourages excellence. - Pay: salary range: $127,650 - $212,750 per year; determined by education, experience, etc. - Schedule: not provided (no schedule info). Travel Requirements N/A, but schedule not given. So we should omit Schedule section. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't include boilerplate like EEO, About Us (except benefits). We extracted benefits from About Us but removed the rest. We need to preserve all substantive information: ensure we didn't lose any. Let's list all substantive info from posting: - Estimated Starting Salary Range: USD $127,650.00/Yr. - USD $212,750.00/Yr. Salary to be determined by the education, experience, knowledge, skills, and abilities of the applicant, internal equity, and alignment with market data. - Description: Designing, developing, and deploying a continually evolving line of products capable of producing synthetic scenarios within Live, Virtual, and Constructive (LVC) environments to drive the simulation of systems during training, testing, and analysis - Leading a team of SW developers and sit on-site alongside team and government personnel - FILLING THIS POSITION IS CONTINGENT UPON AWARD - Requirements: Bachelor's degree in computer science, computer engineering, software engineering, or systems engineering and 12 years of SW development experience - Eight or more years of experience leading teams of SW developers - Nine or more years of experience writing code in Java and JavaScript and C++ - Four or more years of experience deploying and managing VMs in VMware ESXi - TS/SCI clearance - Desired Skills: Experience using Jira, Confluence, Bitbucket, Artifactory, and Jenkins - Experience performing software engineering production across the complete DevSecOps lifecycle of a project - Experience providing obsolescence-engineering support to provide replacement EoL/EoS COTS, FOSS, and GOTS SW - Experience in creating and maintaining Software Design Description (SDD), Software Requirements Specification (SRS), Interface Design Description (IDD), and Interface Requirements Specification (IRS) documentation - Experience in Information Operations (IO)/Information Warfare (IW)/Signal Intelligence (SIGINT) - Experience leading a team of developers on an SCI project - Clearance Information: SRC IS A CONTRACTOR FOR THE U.S. GOVERNMENT, THIS POSITION WILL REQUIRE U.S. CITIZENSHIP AS WELL AS, A U.S. GOVERNMENT SECURITY CLEARANCE AT THE TOP SECRET / SCI LEVEL - Travel Requirements: N/A (ignore) - About Us: Scientific Research Corporation is an advanced information technology and engineering company that provides innovative products and services to government and private industry, as well as independent institutions. At the core of our capabilities is a seasoned team of highly skilled engineers and scientists with multidisciplinary backgrounds. This team is challenged daily to provide cutting edge technology solutions to our clients. SRC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with a company match, life insurance, vacation and sick paid time off accruals with amounts increasing based on role and years of service, 11 paid holidays, tuition reimbursement, and a work environment that encourages excellence and more. For positions requiring a security clearance, selected applicants will be subject to a government security investigation and must meet eligibility requirements for access to classified information. We need to preserve all substantive info. So we need to include the company description? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed as boilerplate, but it's generic company description. Might be considered boilerplate? However it contains substantive info about benefits. The benefits are part of About Us. We need to preserve benefits. The company description itself may be considered boilerplate but it's not explicitly prohibited. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove "About Us". So we could keep a brief About the company? But we have a section "About the role" not "About Us". The instruction says use headings for sections like About the role, Responsibilities, etc. So we should not create an "About Us" heading. Instead we can incorporate the company description into Benefits or maybe a brief note. But we need to preserve all substantive information; the company description about being an advanced IT company etc may be considered substantive but not required for sections. However we could incorporate it into a paragraph under About the role? Might be okay. But we need to avoid creating sections with filler. If we include a paragraph about the company under About the role, that might be okay. Better: Keep About the role as description of role (designing..., leading team..., contingent). Keep Responsibilities maybe not needed if we already covered. But we could split: About the role = brief overview; Responsibilities = bullet list of duties. Let's decide to have:

  About the role

  Designing, developing, and deploying a continually evolving line of products capable of