General Interdisciplinary Engineer- Journeyman
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
4. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
5. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
6. Prefer a few substantive sections over many thin ones
7. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting starts with company description about Torch Technologies (employee-owned, Great Place to Work, etc.) - this could be "About the role" or "About the company" section.
Then there's a description of the opportunity: "Torch Technologies has an exciting opportunity for a General/Interdisciplinary Engineer providing support to the Air Force Life Cycle Management Center/Airborne Warning and Control System (AFLCMC/HBS/WIW)." This is about the role.
Then there's a description of the AWACS Division mission.
Then "This is a full time Hybrid position located at Tinker AFB, OK." - this is schedule/location info.
Then "Duties Include, But Not Limited To" with three subsections:
- Design & Architectures (multiple bullet points)
- Acquisition (multiple bullet points)
- Technical Management (multiple bullet points)
Then "Preferred Qualifications" with three items:
- U.S. Citizenship
- Bachelor's Degree... experience requirements
- Must have and maintain an Active Secret Clearance
Then "Technical Skills" with multiple bullet points
Then "Interpersonal Skills" with multiple bullet points
Then "Additional Information" with:
- Location: Tinker AFB, OK
- Travel: 20% (Hanscom, Seattle)
- Relocation Assistance Available: No
- Position Contingent Upon Award of Contract: No
- Salary Range $100,000-$110,000 (with explanation)
Then "Benefits" section with list of benefits
Then "Applying To Torch Technologies" with boilerplate about interviews, background check, EEO, E-Verify, accommodations - this should be removed as per instructions.
Now I need to structure this into HTML with appropriate sections.
Sections I'll create:
1. About the role (company description + role description)
2. Responsibilities (the three duty categories)
3. Qualifications (Preferred Qualifications)
4. Skills (Technical Skills + Interpersonal Skills)
4. Additional Information (location, travel, relocation, contract contingency)
5. Pay (salary range)
6. Benefits (benefits list)
I should not create a Schedule section unless there's specific schedule info. The posting says "full time Hybrid position" - that's schedule info. But the instructions say only create Schedule section if posting actually states them. It does state "full time Hybrid position". I could include that in Additional Information or create a Schedule section. Since it's mentioned, I'll include it in Additional Information or maybe a small Schedule section. But the instructions say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (full time Hybrid). But also location is stated. I'll include schedule in Additional Information.
Let me structure:
- About the role: company intro + role description + AWACS mission description
- Responsibilities: three subsections (Design & Architectures, Acquisition, Technical Management) each with ul/li
- Qualifications: Preferred Qualifications as ul/li
- Skills: Technical Skills and Interpersonal Skills as two ul lists (maybe separate subsections or combined)
- Additional Information: location, travel, relocation, contract contingency
- Pay: salary range with explanation
- Benefits: benefits list
I need to use
for section headings. For subsections within Responsibilities, I could use but the instructions only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I could use for subsections like Design & Architectures, Acquisition, Technical Management. But the instructions don't forbid other heading levels. However, to be safe, I'll use for main sections and maybe for subsections. But the output should be semantic HTML. I think using for subsections is fine.
But the instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. I'll use for main sections and for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for company description and role description.
Then
Responsibilities
with three subsections and - for each duty.
Then
Qualifications
with - for preferred qualifications.
Then
Skills
with two subsections: Technical Skills and Interpersonal Skills, each with - .
Then
Additional Information
with - for location, travel, relocation, contract contingency.
Then
Pay
with for salary range and explanation.
Then
Benefits
with - for benefits list.
Make sure not to include any filler. The salary range is specific: $100,000-$110,000 with explanation. That's real content.
Benefits list is specific.
Now, I need to ensure I preserve ALL substantive information. So I must include all bullet points exactly as they appear, but formatted as
- .
Let me extract the bullet points:
Design & Architectures:
- The Contractor shall provide engineering support in the design, operation, and sustainment of systems and components that cover tasks throughout the acquisition life cycle (requirements analysis through system disposal). Tasks may also include supporting Foreign Military Sales.
- Conduct and support all engineering and technical activities required during the material solution analysis, technology, engineering, and manufacturing development, production and deployment, and operation and support phases of the systems acquisition process.
- Develop/prepare engineering and technical documentation inherently part of the activities listed above (e.g. Analysis of Alternatives (AoA), Systems Engineering Plan (SEP)…), systems review and analysis with written reporting, briefing, and artifact development as required for all of the technical specialty areas defined in this section; and the planning and execution of all necessary technical reviews, assessments, and interchange meetings (e.g. Critical Design Review(CDR), Manufacturing Readiness Assessment (MRA), Reliability Technical Interchange Meeting (TIM)) and associated artifacts (e.g. Critical Design Review entry and exit criteria).
- Conduct systems architectural analyses to include system design/design feasibility and state-of-the-art assessment
- Produce architectures, document planned and existing systems, determine deficiencies, develop alternatives, recommend solutions, and support development of a plan to implement the chosen solution per acquisition and sustainment system engineering processes. This may include traditional architecture development or Model Based Systems Engineering processes.
- Track and ensure system architecture and interoperability requirements for the baselined system is maintained.
- Detail operational requirements and functional interactions within the system and with other systems, considering life cycle costs, logistics supportability, human factors, et al, to determine if the basic building blocks of the system are defined in sufficient detail to support a development program effort.
- Translate DoW user requirements into system requirements for designing, developing, testing and evaluating systems and subsystems using USAF and DoW approved acquisition methods.
- Provide engineering analysis of system training, training equipment and simulator requirements; prepare technical documentation; and provide engineering evaluation of equipment and simulator designs.
Acquisition:
- Understand and implement robust DoW acquisition and sustainment systems engineering processes to address the life-cycle requirements of each product support area
- Prepare and review program specifications for items, processes and materials. Develop and utilize analytical, simulation, MBSE and digital engineering analysis techniques to optimize system performance and/or system effectiveness; establish system sensitivities, define system parameters, evaluate hardware and validate flight test results in terms of overall system relationships and applications.
- Develop, prepare, review, and integrate selected milestone review documentation, periodic reports, and certifications as identified in current DoW and AF acquisition policy.
- Review, evaluate and monitor acquisition Contractor drawings for completeness, currency, technical accuracy and conformance to requirements, specifications, regulations and quality control to ensure compliance with ASME technical Data Package format and requirements.
Technical Management:
- Complete and support requirements definition and analysis, architecture design, implementation, integration, verification and validation, transition, decision analysis, requirements management, risk management, interface management, and configuration management
- Facilitate the transfer of information, lessons learned and best practices across all customers and contractors serviced under this task order within constraints of proprietary rights
- Perform market research and trade studies to assess current and future systems to ensure they that meet mission needs/requirements.
- Conduct, define and evaluate system cost, schedule, and technical performance.
- Perform reviews, studies (including root cause analysis), audits, evaluations and analyses and provide technical recommendations to the Government.
- Conduct engineering performance, effectiveness, cost effectiveness, cost performance, life cycle cost, producibility, reliability and maintainability, risk and scheduling trade-off studies
- Develop USAF approved Test and Evaluation Master Plans (TEMP), test plans and procedures, prepare test readiness reviews and associated test documentation using DoW and USAF standard processes, execute developmental tests and assist in operational test planning/execution, and evaluate tests in support of acquisition and sustainment programs.
- Participate in integrated logistics support efforts, provisioning and source coding, maintenance data collection, technical order management, configuration management, evaluation of quality deficiency reports, and/or identification of alternate sources of supply for diminishing manufacturing/materiel sources preferred.
Preferred Qualifications:
- U.S. Citizenship.
- Bachelor’s Degree in a related field and 3 years of experience in the respective technical/professional discipline being performed, 3 of which must be in the DoW OR 7 years of directly related experience, 5 of which must be in the DoW.
- Must have and maintain an Active Secret Clearance.
Technical Skills:
- Develop and prepare technical documentation recommending system and subsystem characteristics, including engineering analyses and corrective action plans.
- Create management reports and technical presentations supporting planning, implementation, and sustainment activities.
- Apply engineering theories, principles, and economy concepts to evaluate system performance, cost, risk, and life‑cycle considerations.
- Perform requirements analysis, architecture development, integration, verification/validation, and configuration management across the acquisition life cycle.
- Conduct trade studies, market research, root‑cause analyses, audits, evaluations, and technical reviews, providing recommendations to government stakeholders.
- Support test
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 4. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 5. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them 6. Prefer a few substantive sections over many thin ones 7. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting starts with company description about Torch Technologies (employee-owned, Great Place to Work, etc.) - this could be "About the role" or "About the company" section. Then there's a description of the opportunity: "Torch Technologies has an exciting opportunity for a General/Interdisciplinary Engineer providing support to the Air Force Life Cycle Management Center/Airborne Warning and Control System (AFLCMC/HBS/WIW)." This is about the role. Then there's a description of the AWACS Division mission. Then "This is a full time Hybrid position located at Tinker AFB, OK." - this is schedule/location info. Then "Duties Include, But Not Limited To" with three subsections: - Design & Architectures (multiple bullet points) - Acquisition (multiple bullet points) - Technical Management (multiple bullet points) Then "Preferred Qualifications" with three items: - U.S. Citizenship - Bachelor's Degree... experience requirements - Must have and maintain an Active Secret Clearance Then "Technical Skills" with multiple bullet points Then "Interpersonal Skills" with multiple bullet points Then "Additional Information" with: - Location: Tinker AFB, OK - Travel: 20% (Hanscom, Seattle) - Relocation Assistance Available: No - Position Contingent Upon Award of Contract: No - Salary Range $100,000-$110,000 (with explanation) Then "Benefits" section with list of benefits Then "Applying To Torch Technologies" with boilerplate about interviews, background check, EEO, E-Verify, accommodations - this should be removed as per instructions. Now I need to structure this into HTML with appropriate sections. Sections I'll create: 1. About the role (company description + role description) 2. Responsibilities (the three duty categories) 3. Qualifications (Preferred Qualifications) 4. Skills (Technical Skills + Interpersonal Skills) 4. Additional Information (location, travel, relocation, contract contingency) 5. Pay (salary range) 6. Benefits (benefits list) I should not create a Schedule section unless there's specific schedule info. The posting says "full time Hybrid position" - that's schedule info. But the instructions say only create Schedule section if posting actually states them. It does state "full time Hybrid position". I could include that in Additional Information or create a Schedule section. Since it's mentioned, I'll include it in Additional Information or maybe a small Schedule section. But the instructions say "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule (full time Hybrid). But also location is stated. I'll include schedule in Additional Information. Let me structure: - About the role: company intro + role description + AWACS mission description - Responsibilities: three subsections (Design & Architectures, Acquisition, Technical Management) each with ul/li - Qualifications: Preferred Qualifications as ul/li - Skills: Technical Skills and Interpersonal Skills as two ul lists (maybe separate subsections or combined) - Additional Information: location, travel, relocation, contract contingency - Pay: salary range with explanation - Benefits: benefits list I need to use
for section headings. For subsections within Responsibilities, I could use but the instructions only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I could use for subsections like Design & Architectures, Acquisition, Technical Management. But the instructions don't forbid other heading levels. However, to be safe, I'll use for main sections and maybe for subsections. But the output should be semantic HTML. I think using for subsections is fine.
But the instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. I'll use for main sections and for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention subsections. I could use for subsections like Design & Architectures, Acquisition, Technical Management. But the instructions don't forbid other heading levels. However, to be safe, I'll use for main sections and maybe for subsections. But the output should be semantic HTML. I think using for subsections is fine.
But the instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. I'll use for main sections and for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for subsections like Design & Architectures, Acquisition, Technical Management. But the instructions don't forbid other heading levels. However, to be safe, I'll use for main sections and maybe for subsections. But the output should be semantic HTML. I think using for subsections is fine.
But the instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. I'll use for main sections and for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for subsections. But the output should be semantic HTML. I think using for subsections is fine.
But the instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. I'll use for main sections and for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. I'll use for main sections and for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for subsections within Responsibilities.
Now, I need to remove boilerplate: the "Applying To Torch Technologies" section is boilerplate (interview process, background check, EEO, E-Verify, accommodations). Remove that.
Also remove "Thank you for your interest in employment with Torch Technologies." at the beginning? That's part of company intro. I'll keep the company description.
Now, let's write the HTML.
I'll start with About the role
then
for company description and role description. Then
Responsibilities
with three subsections and - for each duty.
Then
Qualifications
with - for preferred qualifications.
Then
Skills
with two subsections: Technical Skills and Interpersonal Skills, each with - .
Then
Additional Information
with - for location, travel, relocation, contract contingency.
Then
Pay
with for salary range and explanation.
Then
Benefits
with - for benefits list.
Make sure not to include any filler. The salary range is specific: $100,000-$110,000 with explanation. That's real content.
Benefits list is specific.
Now, I need to ensure I preserve ALL substantive information. So I must include all bullet points exactly as they appear, but formatted as
- .
Let me extract the bullet points:
Design & Architectures:
- The Contractor shall provide engineering support in the design, operation, and sustainment of systems and components that cover tasks throughout the acquisition life cycle (requirements analysis through system disposal). Tasks may also include supporting Foreign Military Sales.
- Conduct and support all engineering and technical activities required during the material solution analysis, technology, engineering, and manufacturing development, production and deployment, and operation and support phases of the systems acquisition process.
- Develop/prepare engineering and technical documentation inherently part of the activities listed above (e.g. Analysis of Alternatives (AoA), Systems Engineering Plan (SEP)…), systems review and analysis with written reporting, briefing, and artifact development as required for all of the technical specialty areas defined in this section; and the planning and execution of all necessary technical reviews, assessments, and interchange meetings (e.g. Critical Design Review(CDR), Manufacturing Readiness Assessment (MRA), Reliability Technical Interchange Meeting (TIM)) and associated artifacts (e.g. Critical Design Review entry and exit criteria).
- Conduct systems architectural analyses to include system design/design feasibility and state-of-the-art assessment
- Produce architectures, document planned and existing systems, determine deficiencies, develop alternatives, recommend solutions, and support development of a plan to implement the chosen solution per acquisition and sustainment system engineering processes. This may include traditional architecture development or Model Based Systems Engineering processes.
- Track and ensure system architecture and interoperability requirements for the baselined system is maintained.
- Detail operational requirements and functional interactions within the system and with other systems, considering life cycle costs, logistics supportability, human factors, et al, to determine if the basic building blocks of the system are defined in sufficient detail to support a development program effort.
- Translate DoW user requirements into system requirements for designing, developing, testing and evaluating systems and subsystems using USAF and DoW approved acquisition methods.
- Provide engineering analysis of system training, training equipment and simulator requirements; prepare technical documentation; and provide engineering evaluation of equipment and simulator designs.
Acquisition:
- Understand and implement robust DoW acquisition and sustainment systems engineering processes to address the life-cycle requirements of each product support area
- Prepare and review program specifications for items, processes and materials. Develop and utilize analytical, simulation, MBSE and digital engineering analysis techniques to optimize system performance and/or system effectiveness; establish system sensitivities, define system parameters, evaluate hardware and validate flight test results in terms of overall system relationships and applications.
- Develop, prepare, review, and integrate selected milestone review documentation, periodic reports, and certifications as identified in current DoW and AF acquisition policy.
- Review, evaluate and monitor acquisition Contractor drawings for completeness, currency, technical accuracy and conformance to requirements, specifications, regulations and quality control to ensure compliance with ASME technical Data Package format and requirements.
Technical Management:
- Complete and support requirements definition and analysis, architecture design, implementation, integration, verification and validation, transition, decision analysis, requirements management, risk management, interface management, and configuration management
- Facilitate the transfer of information, lessons learned and best practices across all customers and contractors serviced under this task order within constraints of proprietary rights
- Perform market research and trade studies to assess current and future systems to ensure they that meet mission needs/requirements.
- Conduct, define and evaluate system cost, schedule, and technical performance.
- Perform reviews, studies (including root cause analysis), audits, evaluations and analyses and provide technical recommendations to the Government.
- Conduct engineering performance, effectiveness, cost effectiveness, cost performance, life cycle cost, producibility, reliability and maintainability, risk and scheduling trade-off studies
- Develop USAF approved Test and Evaluation Master Plans (TEMP), test plans and procedures, prepare test readiness reviews and associated test documentation using DoW and USAF standard processes, execute developmental tests and assist in operational test planning/execution, and evaluate tests in support of acquisition and sustainment programs.
- Participate in integrated logistics support efforts, provisioning and source coding, maintenance data collection, technical order management, configuration management, evaluation of quality deficiency reports, and/or identification of alternate sources of supply for diminishing manufacturing/materiel sources preferred.
Preferred Qualifications:
- U.S. Citizenship.
- Bachelor’s Degree in a related field and 3 years of experience in the respective technical/professional discipline being performed, 3 of which must be in the DoW OR 7 years of directly related experience, 5 of which must be in the DoW.
- Must have and maintain an Active Secret Clearance.
Technical Skills:
- Develop and prepare technical documentation recommending system and subsystem characteristics, including engineering analyses and corrective action plans.
- Create management reports and technical presentations supporting planning, implementation, and sustainment activities.
- Apply engineering theories, principles, and economy concepts to evaluate system performance, cost, risk, and life‑cycle considerations.
- Perform requirements analysis, architecture development, integration, verification/validation, and configuration management across the acquisition life cycle.
- Conduct trade studies, market research, root‑cause analyses, audits, evaluations, and technical reviews, providing recommendations to government stakeholders.
- Support test
Qualifications
with- for preferred qualifications.
Then
Skills
with two subsections: Technical Skills and Interpersonal Skills, each with- .
Then
Additional Information
with- for location, travel, relocation, contract contingency.
Then
Pay
withfor salary range and explanation. Then
Benefits
with- for benefits list. Make sure not to include any filler. The salary range is specific: $100,000-$110,000 with explanation. That's real content. Benefits list is specific. Now, I need to ensure I preserve ALL substantive information. So I must include all bullet points exactly as they appear, but formatted as
- . Let me extract the bullet points: Design & Architectures: - The Contractor shall provide engineering support in the design, operation, and sustainment of systems and components that cover tasks throughout the acquisition life cycle (requirements analysis through system disposal). Tasks may also include supporting Foreign Military Sales. - Conduct and support all engineering and technical activities required during the material solution analysis, technology, engineering, and manufacturing development, production and deployment, and operation and support phases of the systems acquisition process. - Develop/prepare engineering and technical documentation inherently part of the activities listed above (e.g. Analysis of Alternatives (AoA), Systems Engineering Plan (SEP)…), systems review and analysis with written reporting, briefing, and artifact development as required for all of the technical specialty areas defined in this section; and the planning and execution of all necessary technical reviews, assessments, and interchange meetings (e.g. Critical Design Review(CDR), Manufacturing Readiness Assessment (MRA), Reliability Technical Interchange Meeting (TIM)) and associated artifacts (e.g. Critical Design Review entry and exit criteria). - Conduct systems architectural analyses to include system design/design feasibility and state-of-the-art assessment - Produce architectures, document planned and existing systems, determine deficiencies, develop alternatives, recommend solutions, and support development of a plan to implement the chosen solution per acquisition and sustainment system engineering processes. This may include traditional architecture development or Model Based Systems Engineering processes. - Track and ensure system architecture and interoperability requirements for the baselined system is maintained. - Detail operational requirements and functional interactions within the system and with other systems, considering life cycle costs, logistics supportability, human factors, et al, to determine if the basic building blocks of the system are defined in sufficient detail to support a development program effort. - Translate DoW user requirements into system requirements for designing, developing, testing and evaluating systems and subsystems using USAF and DoW approved acquisition methods. - Provide engineering analysis of system training, training equipment and simulator requirements; prepare technical documentation; and provide engineering evaluation of equipment and simulator designs. Acquisition: - Understand and implement robust DoW acquisition and sustainment systems engineering processes to address the life-cycle requirements of each product support area - Prepare and review program specifications for items, processes and materials. Develop and utilize analytical, simulation, MBSE and digital engineering analysis techniques to optimize system performance and/or system effectiveness; establish system sensitivities, define system parameters, evaluate hardware and validate flight test results in terms of overall system relationships and applications. - Develop, prepare, review, and integrate selected milestone review documentation, periodic reports, and certifications as identified in current DoW and AF acquisition policy. - Review, evaluate and monitor acquisition Contractor drawings for completeness, currency, technical accuracy and conformance to requirements, specifications, regulations and quality control to ensure compliance with ASME technical Data Package format and requirements. Technical Management: - Complete and support requirements definition and analysis, architecture design, implementation, integration, verification and validation, transition, decision analysis, requirements management, risk management, interface management, and configuration management - Facilitate the transfer of information, lessons learned and best practices across all customers and contractors serviced under this task order within constraints of proprietary rights - Perform market research and trade studies to assess current and future systems to ensure they that meet mission needs/requirements. - Conduct, define and evaluate system cost, schedule, and technical performance. - Perform reviews, studies (including root cause analysis), audits, evaluations and analyses and provide technical recommendations to the Government. - Conduct engineering performance, effectiveness, cost effectiveness, cost performance, life cycle cost, producibility, reliability and maintainability, risk and scheduling trade-off studies - Develop USAF approved Test and Evaluation Master Plans (TEMP), test plans and procedures, prepare test readiness reviews and associated test documentation using DoW and USAF standard processes, execute developmental tests and assist in operational test planning/execution, and evaluate tests in support of acquisition and sustainment programs. - Participate in integrated logistics support efforts, provisioning and source coding, maintenance data collection, technical order management, configuration management, evaluation of quality deficiency reports, and/or identification of alternate sources of supply for diminishing manufacturing/materiel sources preferred. Preferred Qualifications: - U.S. Citizenship. - Bachelor’s Degree in a related field and 3 years of experience in the respective technical/professional discipline being performed, 3 of which must be in the DoW OR 7 years of directly related experience, 5 of which must be in the DoW. - Must have and maintain an Active Secret Clearance. Technical Skills: - Develop and prepare technical documentation recommending system and subsystem characteristics, including engineering analyses and corrective action plans. - Create management reports and technical presentations supporting planning, implementation, and sustainment activities. - Apply engineering theories, principles, and economy concepts to evaluate system performance, cost, risk, and life‑cycle considerations. - Perform requirements analysis, architecture development, integration, verification/validation, and configuration management across the acquisition life cycle. - Conduct trade studies, market research, root‑cause analyses, audits, evaluations, and technical reviews, providing recommendations to government stakeholders. - Support test
- for location, travel, relocation, contract contingency.
Then
- .
Then