Senior Software/Systems Engineer/Analyst
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to extract substantive info.
Let's parse the posting:
Intro: "Torch Technologies Thank you for your interest in employment with Torch Technologies. We are a 100% employee-owned, Certified Great Place To Work and named Best Places to Work in Huntsville/Madison County, headquartered in Huntsville, AL. Our team provides superior research, development, and engineering services to the Federal Government and Department of War. As one of the nation’s top 100 defense companies, the services we provide directly support the men and women who serve our country. Our corporate mission sums up the pride our employee-owners take in the work we do: “Lighting the Pathway of Freedom”. And, as a Certified Evergreen ESOP, we have made the commitment to grow and sustain our company for the next 100 years! Come grow with us!"
That's company overview; could be "About the role"? Actually "About the role" heading is for role description. But we could use "About the role" for description of the position. The intro about company could be placed maybe as part of "About the role"? But guidelines: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role (description of role), Responsibilities (list of duties), Requirements (maybe required qualifications), Qualifications (maybe desired?), Skills (desired skills), Benefits, Pay, Schedule.
We need to decide mapping.
The posting includes: "Torch Technologies is seeking a highly motivated Senior Software/Systems Engineer/Analyst to support advanced defense and engineering programs. This role involves developing and applying analytical tools, performing system-level evaluations, and contributing to mission-critical solutions in a fast-paced, technical environment.The ideal candidate has a strong foundation in software engineering including programming in C++, Python, and Java; agile development, and requirements analysis. The candidate will also have the ability to collaborate across multidisciplinary teams, work with customer organizations, and recommend solutions for complex engineering challenges."
That's more about role and ideal candidate.
Then: "As a Software/Systems Engineer/Analyst, your duties will include, but are not limited to:" followed by bullet list of duties.
Then "Required Qualifications" list.
Then "Desired Skills" list.
Then "Schedule: M-F; 8-5 Work Location: Customer- site: No telework option available Travel: Yes, 0-10% Relocation Assistance Available: No Position Contingent Upon Award of Contract: No"
Then "Benefits Torch Technologies is proud to offer a stable and professional work environment, a competitive salary, and an excellent, comprehensive benefit package including: ESOP participation, 401(k) match, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, Health Saving Accounts and Health Reimbursement Accounts, EAP, education assistance, paid time off, and holidays."
Pay: Not explicitly stated; they say "competitive salary" but no number. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, they didn't give a specific number or range, just "competitive salary". That's vague; maybe we should not include Pay section because it's not specific. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." They did state Schedule (M-F; 8-5). So include Schedule. Benefits they listed specifics, so include Benefits. Pay: they said competitive salary but no specifics; might be considered not specific enough; better to omit Pay section.
Now we need to decide sections: About the role (maybe combine company overview and role description). Responsibilities (list of duties). Requirements (maybe required qualifications). Qualifications (maybe desired skills? Actually they have Required Qualifications and Desired Skills. Could map Required Qualifications to Requirements, Desired Skills to Skills. Qualifications maybe not needed; but we could have Qualifications for required qualifications and Skills for desired skills. However they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications if content exists. But we need to avoid filler. We have Required Qualifications (list). That's specific. Desired Skills (list). That's specific. So we could put Required Qualifications under Requirements heading, and Desired Skills under Skills heading. Qualifications heading maybe we could omit if no distinct content beyond Requirements. But we could also put Required Qualifications under Qualifications and Desired Skills under Skills, leaving Requirements empty? Better to follow typical: Requirements = required qualifications, Skills = desired skills. Qualifications maybe not needed. But we have both headings available; we can include Requirements and Skills, and optionally Qualifications if we have something else like "Bachelor's degree..." but that's already in Required Qualifications. So we can skip Qualifications to avoid thin section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Now we need to extract content.
About the role: Should include company overview and role description? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So About the role section should contain description of the role and maybe company context. We'll combine the introductory paragraphs about Torch Technologies and the role description: "Torch Technologies is seeking a highly motivated Senior Software/Systems Engineer/Analyst to support advanced defense and engineering programs. This role involves developing and applying analytical tools, performing system-level evaluations, and contributing to mission-critical solutions in a fast-paced, technical environment.The ideal candidate has a strong foundation in software engineering including programming in C++, Python, and Java; agile development, and requirements analysis. The candidate will also have the ability to collaborate across multidisciplinary teams, work with customer organizations, and recommend solutions for complex engineering challenges."
We could also include the company overview sentences before that. But that might be considered "About the company" not role. However it's still substantive info about employer; could be included. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep company overview as well. We'll put it in About the role section.
Thus About the role paragraph(s): combine the company overview and role description.
Now Responsibilities: list of duties from "As a Software/Systems Engineer/Analyst, your duties will include, but are not limited to:" then bullet list.
We need to output - for each duty.
List:
- Developing and reviewing plans and reports to ensure system and software operations comply with requirements and design specifications.
- Develop and maintain tools using Python and Bash scripts to support data analysis and system evaluation.
- Perform system-level analysis to identify performance issues and optimization opportunities.
- Perform detailed performance analyses, generating actionable insights, and recommending architectural or algorithmic improvements.
- Evaluate technical requirements for ambiguity, completeness and testability.
- Analyze large datasets to identify trends, bottlenecks, and system inefficiencies.
- Collaborate with cross-functional engineering teams to improve system performance and reliability.
- Support troubleshooting efforts across distributed systems and infrastructure.
- Contribute to technical documentation, reports, and customer deliverables.
- Assist in planning and executing engineering tasks to meet program deadlines.
Make sure each
- ends with a period? Keep as is.
Now Requirements: Required Qualifications list.
List:
- US Citizenship.
- Bachelor’s degree in Computer Science, Software Engineering, Computer Engineering, Electrical Engineering or a related field.
- 8+ years of relevant engineering experience.
- Ability to work with two or more of Ada, C, C++, Python, and Java.
- Strong analytical and problem-solving skills.
- Ability to work effectively in a team-oriented, fast-paced environment.
- Strong written and verbal communication skills.
- Experience supporting system testing, validation, and/or verification efforts.
- Ability to participate in customer meetings, document findings, and remediate issues.
- Must have a current secret clearance.
Now Skills: Desired Skills list.
List:
- Knowledge of DOORS, Requirements Analysis processes, and/or Systems Engineering.
- Experience with the Linux, Windows, and VxWorks operating systems.
- Experience with system analysis, data processing, and/or radar/sensor systems.
- Experience in missile defense or aerospace systems.
- Experience working with distributed systems or server-based architecture.
Now Benefits: list from benefits paragraph.
Benefits: "ESOP participation, 401(k) match, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, Health Saving Accounts and Health Reimbursement Accounts, EAP, education assistance, paid time off, and holidays."
We need to output as
- each item.
Now Schedule: "Schedule: M-F; 8-5 Work Location: Customer- site: No telework option available Travel: Yes, 0-10% Relocation Assistance Available: No Position Contingent Upon Award of Contract: No"
We need to include schedule specifics. The schedule is M-F; 8-5. The rest is work location, travel, relocation, contingency. Should we include all? The instruction: include a section ONLY when the posting has real, specific content for it. So schedule section should contain schedule info. We could also include work location etc. but they are not schedule. However we could include them in schedule section as extra details; but better to keep schedule only about schedule. The rest could be omitted? But they are substantive info; maybe we could include them in a separate section like "Work Location" but not in allowed headings. Since only allowed headings are those listed, we could fold minor metadata into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold work location, travel, relocation, contingency into a short
maybe under About the role or separate
without heading? But we must output only HTML fragment; we can include a
for that metadata without heading. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other
without heading. So we can add a
for work location/travel etc.
Thus after Schedule section we can add a
with: Work Location: Customer-site: No telework option available. Travel: Yes, 0-10%. Relocation Assistance Available: No. Position Contingent Upon Award of Contract: No.
Now ensure we don't include boilerplate like EEO etc. We removed that.
Now produce HTML:
About the role
Torch Technologies Thank you for your interest in employment with Torch Technologies. We are a 100% employee-owned, Certified Great Place To Work and named Best Places to Work in Huntsville/Madison County, headquartered in Huntsville, AL. Our team provides superior research, development, and engineering services to the Federal Government and Department of War. As one of the nation’s top 100 defense companies, the services we provide directly support the men and women who serve our country. Our corporate mission sums up the pride our employee-owners take in the work we do: “Lighting the Pathway of Freedom”. And, as a Certified Evergreen ESOP, we have made the commitment to grow and sustain our company for the next 100 years! Come grow with us! Torch Technologies is seeking a highly motivated Senior Software/Systems Engineer/Analyst to support advanced defense and engineering programs. This role involves developing and applying analytical
- for each duty. List: - Developing and reviewing plans and reports to ensure system and software operations comply with requirements and design specifications. - Develop and maintain tools using Python and Bash scripts to support data analysis and system evaluation. - Perform system-level analysis to identify performance issues and optimization opportunities. - Perform detailed performance analyses, generating actionable insights, and recommending architectural or algorithmic improvements. - Evaluate technical requirements for ambiguity, completeness and testability. - Analyze large datasets to identify trends, bottlenecks, and system inefficiencies. - Collaborate with cross-functional engineering teams to improve system performance and reliability. - Support troubleshooting efforts across distributed systems and infrastructure. - Contribute to technical documentation, reports, and customer deliverables. - Assist in planning and executing engineering tasks to meet program deadlines. Make sure each
- ends with a period? Keep as is.
Now Requirements: Required Qualifications list.
List:
- US Citizenship.
- Bachelor’s degree in Computer Science, Software Engineering, Computer Engineering, Electrical Engineering or a related field.
- 8+ years of relevant engineering experience.
- Ability to work with two or more of Ada, C, C++, Python, and Java.
- Strong analytical and problem-solving skills.
- Ability to work effectively in a team-oriented, fast-paced environment.
- Strong written and verbal communication skills.
- Experience supporting system testing, validation, and/or verification efforts.
- Ability to participate in customer meetings, document findings, and remediate issues.
- Must have a current secret clearance.
Now Skills: Desired Skills list.
List:
- Knowledge of DOORS, Requirements Analysis processes, and/or Systems Engineering.
- Experience with the Linux, Windows, and VxWorks operating systems.
- Experience with system analysis, data processing, and/or radar/sensor systems.
- Experience in missile defense or aerospace systems.
- Experience working with distributed systems or server-based architecture.
Now Benefits: list from benefits paragraph.
Benefits: "ESOP participation, 401(k) match, medical, dental, vision, life insurance, short-term disability, long-term disability, flexible spending accounts, Health Saving Accounts and Health Reimbursement Accounts, EAP, education assistance, paid time off, and holidays."
We need to output as
- each item.
Now Schedule: "Schedule: M-F; 8-5 Work Location: Customer- site: No telework option available Travel: Yes, 0-10% Relocation Assistance Available: No Position Contingent Upon Award of Contract: No"
We need to include schedule specifics. The schedule is M-F; 8-5. The rest is work location, travel, relocation, contingency. Should we include all? The instruction: include a section ONLY when the posting has real, specific content for it. So schedule section should contain schedule info. We could also include work location etc. but they are not schedule. However we could include them in schedule section as extra details; but better to keep schedule only about schedule. The rest could be omitted? But they are substantive info; maybe we could include them in a separate section like "Work Location" but not in allowed headings. Since only allowed headings are those listed, we could fold minor metadata into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold work location, travel, relocation, contingency into a short
maybe under About the role or separate
without heading? But we must output only HTML fragment; we can include a
for that metadata without heading. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other
without heading. So we can add a
for work location/travel etc. Thus after Schedule section we can add a
with: Work Location: Customer-site: No telework option available. Travel: Yes, 0-10%. Relocation Assistance Available: No. Position Contingent Upon Award of Contract: No. Now ensure we don't include boilerplate like EEO etc. We removed that. Now produce HTML:
About the role
Torch Technologies Thank you for your interest in employment with Torch Technologies. We are a 100% employee-owned, Certified Great Place To Work and named Best Places to Work in Huntsville/Madison County, headquartered in Huntsville, AL. Our team provides superior research, development, and engineering services to the Federal Government and Department of War. As one of the nation’s top 100 defense companies, the services we provide directly support the men and women who serve our country. Our corporate mission sums up the pride our employee-owners take in the work we do: “Lighting the Pathway of Freedom”. And, as a Certified Evergreen ESOP, we have made the commitment to grow and sustain our company for the next 100 years! Come grow with us! Torch Technologies is seeking a highly motivated Senior Software/Systems Engineer/Analyst to support advanced defense and engineering programs. This role involves developing and applying analytical
- each item.
Now Schedule: "Schedule: M-F; 8-5 Work Location: Customer- site: No telework option available Travel: Yes, 0-10% Relocation Assistance Available: No Position Contingent Upon Award of Contract: No"
We need to include schedule specifics. The schedule is M-F; 8-5. The rest is work location, travel, relocation, contingency. Should we include all? The instruction: include a section ONLY when the posting has real, specific content for it. So schedule section should contain schedule info. We could also include work location etc. but they are not schedule. However we could include them in schedule section as extra details; but better to keep schedule only about schedule. The rest could be omitted? But they are substantive info; maybe we could include them in a separate section like "Work Location" but not in allowed headings. Since only allowed headings are those listed, we could fold minor metadata into a short