Reliability and Maintainability Engineer, Journeyman
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have 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 boilerplate, duplicated lines, application instructions). Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Salary Type Annually and description of salary range etc. It says "Salary Type Annually The salary range, if referenced, represents a good faith estimate..." So there is some pay info. So we can include a Pay section with that info. Benefits: they list comprehensive benefits. So include Benefits section. Schedule: they mention Work Arrangement On Site: 100%, Position Type Full-Time/Regular. So schedule info: full-time, on-site. So we can include Schedule section.
We need sections: About the role (maybe a brief description). Responsibilities (list of duties). Requirements (maybe required experience). Qualifications (maybe preferred qualifications). Skills (maybe Microsoft Office proficiency). Benefits, Pay, Schedule.
We must not repeat job title. Must not include tracking code etc. Must drop duplicated lines. Must not include EEO boilerplate. Must not include "COLSA Corporation is an Equal Opportunity Employer..." etc. Must not include "Applicant selected will be subject to a government security investigation..." maybe that's part of requirements? It's about clearance. Could be included in Requirements or Qualifications. But we must preserve all substantive info. So we need to include that info somewhere.
Let's parse the posting:
- Tracking Code UID 806.0 Posted Date 9/21/2026 Job Location Oklahoma City, Oklahoma Location of Position Oklahoma City, Oklahoma Work Arrangement On Site: 100% Position Type Full-Time/Regular Clearance Required? Ability to Qualify Level of Clearance Required Secret
- Principal Duties And Responsibilities: list of duties (multiple sentences). We'll turn into - .
- At COLSA, people are our most valuable resource... Learn about our employee-centric culture and benefits here: https://www.colsa.com/culture_benefits (this is a link to benefits; we can include in Benefits section maybe).
- Required Experience: BA/BS degree in an ABET-accredited engineering discipline and ten (10) years of experience in the respective technical/professional discipline being performed, three (3) of which must be in the DoD Independently demonstrate proficiency in the use of Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint, etc.) & Adobe Acrobat U.S. Citizenship required; Ability to obtain/maintain a Secret clearance required.
- Preferred Qualifications: Knowledge in the R&M process which aligns with program acquisition, sustainment, and disposal scope and strategy, and be clearly evident within the IMP/IMS. The R&M process shall clearly show the application of the integrity approach to reliable and maintainable design, and the tasks of the IMP/IMS shall identify incremental R&M achievement verification at all significant program milestones. Knowledge of Failure Reporting, Analysis, and Corrective Action System (FRACAS) and reliability standard reports. Ability to work with G081 database to check failure reporting from the field; and assist with handling all DRs ensuring proper classification and adequate detail for resolution. Applicant selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information.
- Salary Type Annually The salary range, if referenced, represents a good faith estimate. COLSA considers various factors when determining base salary offers, but not limited to, location, the role, function and associated responsibilities, a candidate’s particular combination of education, knowledge, skills, competencies, and experience, as well as contract-specific affordability and organizational requirements.
- COLSA offers a comprehensive and customizeable benefits program which includes Medical, Dental, Vision, Life Insurance, Short-Term Disability, Long-Term Disability, Accidental Death & Dismemberment, Supplemental Income Protection Programs, 401(k) with company match, Flexible Spending Accounts, Employee Assistance Program, Education & Certification Reimbursement, Employee Discount Program, Paid Time Off and Holidays.
- This position will be posted for a minimum of 3 business days... (application instruction) - we must remove application instructions.
We need to output only HTML fragment.
Let's decide sections:
- About the role: maybe a brief paragraph summarizing the role: applying DoD/AF engineering principles to improve performance and sustainability of weapon systems, assisting in material solution analyses, etc. Could be derived from first part of duties? But we have a Responsibilities section for duties. About the role could be a short overview: "This position supports the improvement and sustainability of Air Force and joint service weapon systems through engineering analysis, documentation, testing, and reliability/maintainability processes." We must not invent or summarize away detail; we must preserve ALL substantive information; but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details, but we can rephrase? Probably we should keep the details as they are, but we can group them. However, we must not invent or summarize away detail. So we need to include all the substantive info from the posting. If we create an About the role section, we must ensure we don't leave out any details that belong elsewhere. It's safer to put the substantive info in appropriate sections (Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). About the role could be optional; we only include if there is real specific content. The posting does have a paragraph about COLSA culture and benefits link; but that's more about benefits. There's no explicit "About the role" paragraph besides the duties. So maybe we skip About the role section to avoid thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit About the role if not needed.
We need to include sections only when posting has real, specific content for it.
Thus we can have:
- Responsibilities (
Responsibilities
) with - each duty.
- Requirements (
Requirements
) with required experience, education, citizenship, clearance, Microsoft Office proficiency.
- Qualifications (Qualifications
) with preferred qualifications (R&M process knowledge, FRACAS, G081 database, security investigation).
- Skills (Skills
) maybe Microsoft Office proficiency? But that's already in Requirements. Could combine. But we could put Skills as Microsoft Office proficiency etc. However we must not duplicate. Perhaps we can put Skills as "Proficiency in Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint) and Adobe Acrobat." That's a skill. But it's also in Requirements. To avoid duplication, we could move it to Skills and keep Requirements focused on education/experience/citizenship/clearance. But the instruction says preserve ALL substantive information; duplication is not prohibited but we should avoid duplicated lines. The posting includes "Independently demonstrate proficiency in the use of Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint, etc.) & Adobe Acrobat" under Required Experience. So we can treat that as a skill. We'll put it under Skills.
- Benefits (Benefits
) with list.
- Pay (Pay
) with salary type annually and description.
- Schedule (Schedule
) with Work Arrangement On Site: 100%, Position Type Full-Time/Regular.
We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines (like location repeated). Also remove "Tracking Code UID 806.0 Posted Date 9/21/2026 Job Location Oklahoma City, Oklahoma Location of Position Oklahoma City, Oklahoma Work Arrangement On Site: 100% Position Type Full-Time/Regular Clearance Required? Ability to Qualify Level of Clearance Required Secret". We'll extract needed info: location (Oklahoma City, Oklahoma), work arrangement (On Site: 100%), position type (Full-Time/Regular), clearance required (Secret). We'll put location maybe not needed as heading; but we could include location in About the role? But we decided to skip About the role. Could we include location in Schedule? Not typical. Could add a short paragraph under Schedule? But schedule section is for schedule info; location maybe not needed. However we must preserve ALL substantive information; location is substantive. Where to put it? Could add a brief before sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid a leading paragraph. But we should follow the heading rules: use
for section headings. We can have a
for prose. So we could include a short paragraph with location and work arrangement before sections. But we also have Schedule section for schedule. Could include location in that paragraph.
Better: include a
with location and work arrangement (On Site: 100%) and position type (Full-Time/Regular). Then Schedule section could be omitted? But schedule info is covered there. However we need to decide if we need a Schedule section. The posting explicitly states Work Arrangement On Site: 100% Position Type Full-Time/Regular. That's schedule info. So we could put that in Schedule section. But location is separate. Could we put location in a
before sections? That would preserve it. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold minor metadata (like tracking code, posted date) into a short
or drop it. Location is not minor metadata? It's important but could be placed in a short
. The instruction says "fold minor metadata into a short
or drop it." Location might be considered metadata but it's substantive. However we could still include it in a short
as part of the preamble. That seems acceptable.
Thus we can have:
Location: Oklahoma City, Oklahoma. Work Arrangement: On Site: 100%. Position Type: Full-Time/Regular. Clearance Required: Secret.
Then sections.
Now we need to ensure we don't include any boilerplate like "At COLSA, people are our most valuable resource..." that's a fluff but maybe we can keep as part of Benefits? Actually that sentence is about culture and benefits link. We could incorporate that into Benefits section as a preamble: "At COLSA, people are our most valuable resource and centered at our core value. We invite you to unite your talents with opportunity and be a part of our “Family of Professionals!” Learn about our employee-centric culture and benefits here: https://www.colsa.com/culture_benefits". That's not boilerplate; it's specific to COLSA. We can include it in Benefits section as a before the list.
Now we need to list duties. Let's extract each duty sentence from "Principal Duties And Responsibilities":
1. Apply an understanding of DoD, AF, and common engineering/scientific principles, processes, and procedures to improve performance and sustainability of existing and future AF and joint service weapon systems.
2. Assist in performing material solution analyses leading up to design reviews.
3. Assist in producing or supporting development of draft documentation and presentation materials as requested or necessitated by programmatic limits based on cost, schedule, and performance.
4. Assist in developing and collecting technical data and inputs for staff summary packages and executive briefings to support coordination and signature of all associated documents for milestone approvals.
5. Assist in translating production and operational requirements into design, fabrication and testing objectives.
6. Provide analysis and recommendations to systems suitability for installation, functionality
Responsibilities
) with- each duty.
- Requirements (
Requirements
) with required experience, education, citizenship, clearance, Microsoft Office proficiency. - Qualifications (Qualifications
) with preferred qualifications (R&M process knowledge, FRACAS, G081 database, security investigation). - Skills (Skills
) maybe Microsoft Office proficiency? But that's already in Requirements. Could combine. But we could put Skills as Microsoft Office proficiency etc. However we must not duplicate. Perhaps we can put Skills as "Proficiency in Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint) and Adobe Acrobat." That's a skill. But it's also in Requirements. To avoid duplication, we could move it to Skills and keep Requirements focused on education/experience/citizenship/clearance. But the instruction says preserve ALL substantive information; duplication is not prohibited but we should avoid duplicated lines. The posting includes "Independently demonstrate proficiency in the use of Microsoft Office Applications (Outlook, Word, Excel, PowerPoint, SharePoint, etc.) & Adobe Acrobat" under Required Experience. So we can treat that as a skill. We'll put it under Skills. - Benefits (Benefits
) with list. - Pay (Pay
) with salary type annually and description. - Schedule (Schedule
) with Work Arrangement On Site: 100%, Position Type Full-Time/Regular. We must not include boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines (like location repeated). Also remove "Tracking Code UID 806.0 Posted Date 9/21/2026 Job Location Oklahoma City, Oklahoma Location of Position Oklahoma City, Oklahoma Work Arrangement On Site: 100% Position Type Full-Time/Regular Clearance Required? Ability to Qualify Level of Clearance Required Secret". We'll extract needed info: location (Oklahoma City, Oklahoma), work arrangement (On Site: 100%), position type (Full-Time/Regular), clearance required (Secret). We'll put location maybe not needed as heading; but we could include location in About the role? But we decided to skip About the role. Could we include location in Schedule? Not typical. Could add a short paragraph under Schedule? But schedule section is for schedule info; location maybe not needed. However we must preserve ALL substantive information; location is substantive. Where to put it? Could add a briefbefore sections? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't forbid a leading paragraph. But we should follow the heading rules: use
for section headings. We can have a
for prose. So we could include a short paragraph with location and work arrangement before sections. But we also have Schedule section for schedule. Could include location in that paragraph. Better: include a
with location and work arrangement (On Site: 100%) and position type (Full-Time/Regular). Then Schedule section could be omitted? But schedule info is covered there. However we need to decide if we need a Schedule section. The posting explicitly states Work Arrangement On Site: 100% Position Type Full-Time/Regular. That's schedule info. So we could put that in Schedule section. But location is separate. Could we put location in a
before sections? That would preserve it. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold minor metadata (like tracking code, posted date) into a short
or drop it. Location is not minor metadata? It's important but could be placed in a short
. The instruction says "fold minor metadata into a short
or drop it." Location might be considered metadata but it's substantive. However we could still include it in a short
as part of the preamble. That seems acceptable. Thus we can have:
Location: Oklahoma City, Oklahoma. Work Arrangement: On Site: 100%. Position Type: Full-Time/Regular. Clearance Required: Secret.
Then sections. Now we need to ensure we don't include any boilerplate like "At COLSA, people are our most valuable resource..." that's a fluff but maybe we can keep as part of Benefits? Actually that sentence is about culture and benefits link. We could incorporate that into Benefits section as a preamble: "At COLSA, people are our most valuable resource and centered at our core value. We invite you to unite your talents with opportunity and be a part of our “Family of Professionals!” Learn about our employee-centric culture and benefits here: https://www.colsa.com/culture_benefits". That's not boilerplate; it's specific to COLSA. We can include it in Benefits section as abefore the list. Now we need to list duties. Let's extract each duty sentence from "Principal Duties And Responsibilities": 1. Apply an understanding of DoD, AF, and common engineering/scientific principles, processes, and procedures to improve performance and sustainability of existing and future AF and joint service weapon systems. 2. Assist in performing material solution analyses leading up to design reviews. 3. Assist in producing or supporting development of draft documentation and presentation materials as requested or necessitated by programmatic limits based on cost, schedule, and performance. 4. Assist in developing and collecting technical data and inputs for staff summary packages and executive briefings to support coordination and signature of all associated documents for milestone approvals. 5. Assist in translating production and operational requirements into design, fabrication and testing objectives. 6. Provide analysis and recommendations to systems suitability for installation, functionality