Software Engineer Developer 4
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like application instructions, contact info? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove "How To Apply For Position Apply Now: ..." and contact email/phone. Also remove "Employment Terms This is a W2 contract position with CTS International. This role is not subcontracted (no C2C). No third-party or agency submissions." Might be considered metadata but maybe we can keep as short paragraph? It says "fold minor metadata into a short
or drop it." So we could include a short paragraph for employment terms. But we need to decide if we include a section for it. Probably not a separate heading; just a paragraph under maybe "About the role" or separate? The instruction: "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (summary), Responsibilities, Requirements, Qualifications, Skills. Benefits, Pay, Schedule only if present. The posting does not mention benefits, pay, schedule. So we omit those sections. We need to preserve all substantive information. Let's extract: Job description sentences: - "Secret Clearance Required To Start." - "Designs, develops, tests, and maintains non-embedded software throughout the end-to-end lifecycle that meets industry, customer, safety, and regulation standards." - "Reviews, analyzes, and translates customer requirements into initial design of software products." - "Develops, maintains, enhances and optimizes software products and functionalities for systems integrations." - "Develops, documents and maintains architectures, requirements, algorithms, interfaces and designs for software products." - "Debugs and resolves issues identified to ensure the reliability and efficiency of software products." - "Handles user inquiries, troubleshoots technical issues and user feedback analysis." - "Implements current and emerging technologies, tools, frameworks and changes in regulations relevant to software development." - "Develops, establishes, monitors and improves software processes, tools and key performance metrics that align projects with organizational goals and industry benchmarks." - "Executes and documents software research and development projects." - "Advises on software domains, system-specific issues, processes and regulations." - "Performs software project management activities and software supplier management functions." - "Tracks and evaluates software team and supplier performance to ensure product and process compliance to project plans and industry standards." - "Supporting the B-52 CERP out of OKC." Requirements: - "Required Experience: 4+ years of experience developing, documenting, and maintaining architectures, algorithms, interfaces, and designs for software systems" - "4+ years of experience in C, C++, C#, Python, Java, or Ada" - "Bach in STEM" (Bachelor in STEM) - "Preferred Experience programming in Ada" - "Agile/SAFe development experience" - "Proficient in ARINC 429 data bus protocol" - "Experience with DevOps tools, such as GitLab (CI/CD), Git Bash, Jira, and Artifactory" - "Ability to work effectively in a team environment and communicate with stakeholders of different backgrounds and skill levels" - "Experience working with Real-time Operating Systems (RTOS)" - "Strong written and verbal communication skills along with the ability and desire to work in a team environment" - "Education/experience typically acquired through advanced technical education from an accredited course of study in engineering, computer science, mathematics, physics or chemistry (e.g. Bachelor) and typically 9 or more years' related work experience or an equivalent combination of technical education and experience (e.g. PhD+4 years' related work experience, Master+7 years' related work experience)." - "In the USA, ABET accreditation is the preferred, although not required, accreditation standard." Employment Terms: - "This is a W2 contract position with CTS International." - "This role is not subcontracted (no C2C)." - "No third-party or agency submissions." We should not include application instructions. Now we need to decide sections. We could have:
About the role
with a paragraph summarizing the role: includes secret clearance, designing, developing, testing, maintaining non-embedded software, supporting B-52 CERP out of OKC.Responsibilities
with a- list of duties (the bullet points from design etc). Could combine many.
Requirements
with list of required experience (the required ones). Might separate required vs preferred? Could combine but maybe separate sections: Requirements and Preferred Qualifications? But we only have headings list: Requirements, Qualifications, Skills. Could map: Requirements = required experience; Qualifications = education/experience; Skills = technical skills, tools, etc. We need to avoid filler. Ensure we don't create sections with placeholder. Let's extract: Required Experience items: - 4+ years of experience developing, documenting, and maintaining architectures, algorithms, interfaces, and designs for software systems - 4+ years of experience in C, C++, C#, Python, Java, or Ada - Bachelor in STEM (Bach in STEM) Preferred Experience items (could go under Qualifications or Skills): - Programming in Ada - Agile/SAFe development experience - Proficient in ARINC 429 data bus protocol - Experience with DevOps tools, such as GitLab (CI/CD), Git Bash, Jira, and Artifactory - Ability to work effectively in a team environment and communicate with stakeholders of different backgrounds and skill levels - Experience working with Real-time Operating Systems (RTOS) - Strong written and verbal communication skills along with the ability and desire to work in a team environment Education/experience: - Education/experience typically acquired through advanced technical education from an accredited course of study in engineering, computer science, mathematics, physics or chemistry (e.g. Bachelor) and typically 9 or more years' related work experience or an equivalent combination of technical education and experience (e.g. PhD+4 years' related work experience, Master+7 years' related work experience). - In the USA, ABET accreditation is the preferred, although not required, accreditation standard. That could go under Qualifications. Skills could be: programming languages, tools, protocols, etc. But we already have many under preferred. Could separate: Skills = programming languages, tools, protocols, RTOS, ARINC 429, DevOps tools. But we need to avoid duplication. Let's think: We can have: - About the role (paragraph) - Responsibilities (list) - Requirements (list of required experience) - Qualifications (list of education/experience and preferred experience) - Skills (list of technical skills: languages, tools, protocols, RTOS, etc.) But we might be splitting too much. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content. Could include About the role, Responsibilities, Requirements (covering required experience, education, preferred). Could also include Skills if we have distinct technical skills not covered elsewhere. However many of the preferred items are skills. Could put them under Requirements as well. But we need to follow the headings list: we can use any of those headings; we are not required to use all. So we could have:About the role
...
Responsibilities
- ...
Requirements
- ...
under About the role or maybe a separate paragraph after About the role but before Responsibilities. The instruction: "fold minor metadata into a short
or drop it." So we can add a short paragraph after About the role maybe. Thus About the role paragraph could include: Secret clearance required to start. Designs, develops, tests, maintains non-embedded software throughout end-to-end lifecycle meeting standards. Supporting B-52 CERP out of OKC. Employment: W2 contract with CTS International, not subcontracted, no third-party agency submissions. Now Responsibilities: list all duty sentences. Requirements: list required experience (4+ years developing/documenting/maintaining architectures etc; 4+ years experience in C, C++, C#, Python, Java, or Ada; Bachelor in STEM). Also maybe include the education/experience equivalence? That could be considered qualifications but we can include under Requirements as well. However the education/experience statement is more about typical background; could be included under Requirements as well. But to avoid too many items, we could include it under Requirements as well. But we need to ensure we don't miss any substantive info: The education/experience statement: "Education/experience typically acquired through advanced technical education from an accredited course of study in engineering, computer science, mathematics, physics or chemistry (e.g. Bachelor) and typically 9 or more years' related work experience or an equivalent combination of technical education and experience (e.g. PhD+4 years' related work experience, Master+7 years' related work experience). In the USA, ABET accreditation is the preferred, although not required, accreditation standard." That is important. We'll include it under Requirements as bullet points. Now we must not include any fluff like "commensurate with experience". Not present. Now produce HTML. We must not include or . Just the fragment. Let's craft. About the role paragraph:
Secret clearance required to start. Designs, develops, tests, and maintains non-embedded software throughout the end-to-end lifecycle that meets industry, customer, safety, and regulation standards. Supports the B-52 CERP program out of Oklahoma City. This is a W2 contract position with CTS International; the role is not subcontracted (no C2C) and no third‑party agency submissions are accepted.
Responsibilities list: we need to convert each duty sentence into - . Let's list them: - Designs, develops, tests, and maintains non-embedded software throughout the end-to-end lifecycle that meets industry, customer, safety, and regulation standards. - Reviews, analyzes, and translates customer requirements into initial design of software products. - Develops, maintains, enhances and optimizes software products and functionalities for systems integrations. - Develops, documents and maintains architectures, requirements, algorithms, interfaces and designs for software products. - Debugs and resolves issues identified to ensure the reliability and efficiency of software products. - Handles user inquiries, troubleshoots technical issues and user feedback analysis. - Implements current and emerging technologies, tools, frameworks and changes in regulations relevant to software development. - Develops, establishes, monitors and improves software processes, tools and key performance metrics that align projects with organizational goals and industry benchmarks. - Executes and documents software research and development projects. - Advises on software domains, system-specific issues, processes and regulations. - Performs software project management activities and software supplier management functions. - Tracks and evaluates software team and supplier performance to ensure product and process compliance to project plans and industry standards. Note the first bullet duplicates the About the role sentence; but we can keep it in responsibilities as it's a duty. It