Cybersecurity Trainer, (1099 Contractor)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content.
Job posting includes: "Job Requirements At Fearless, we are seeking a 1099 contractor to serve as a Cybersecurity Trainer for a 24-week, hands-on workforce development program..." That's about the role. Then "Your Responsibilities In This Role" list. Then "Work Experience Project Skill and Experience Requirements" (maybe Requirements). Then "Preferred Experience". Then "Physical Requirements". Then "Benefits Life at Fearless" (some description). Then "Compensation & Engagement Details" (Pay). Then "Independent Contractor Requirements" (maybe not needed). Then "Reasonable Accommodations". Then "So, What's Next?" (application instructions) - we must remove application instructions. Also "Where You Can Partner with Fearless" (maybe not needed). Also "Life at Fearless" etc.
We need to preserve substantive info, remove boilerplate like EEO, equal opportunity, scam warning, cookie/navigation/legal. The posting includes "We're proud to be an equal opportunity organization." That's EEO boilerplate; remove. Also "Reasonable Accommodations" maybe keep? It's not boilerplate? It's about accommodations; could be considered substantive? Might keep but it's more about process. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So "Reasonable Accommodations" is not EEO; it's about accommodations for disabilities; could be considered part of application process? Might be considered boilerplate? Not sure. Safer to keep? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Reasonable Accommodations is related to ADA; might be considered EEO? Might be considered boilerplate. I'd remove it to be safe.
Also "Independent Contractor Requirements" includes documentation needed; that's part of engagement details, maybe keep under Requirements or a separate section? Could be part of Requirements. But we have limited headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the role: description of role, program, duration, remote, hours.
- Responsibilities: list of duties.
- Requirements: includes Work Experience, Skill and Experience Requirements (minimum 5 years, etc.) plus maybe Preferred Experience? Could be separate Qualifications? But we can combine Requirements and Qualifications? The instruction: Use headings for those categories if content exists. We can have both Requirements and Qualifications if distinct. But we have "Work Experience Project Skill and Experience Requirements" and "Preferred Experience". Could treat "Requirements" as mandatory, "Qualifications" as preferred? Or "Skills" as skills list. Let's decide:
We have many skill statements: Strong knowledge in IAM, PAM, NIST RMF, AWS, APIs, etc. Those could go under Skills.
We have "Minimum of 5 years of experience..." that's Experience requirement.
We have "Demonstrated experience explaining complex technical concepts..." etc.
We have "Proven capability independently conducting technical demonstrations..."
We have "Strong knowledge in Identity and Access Management..." etc.
We have "Strong knowledge in NIST Risk Management Framework..." etc.
We have "Strong knowledge in AWS, APIs, system integration, automation, troubleshooting, or DevSecOps and security operations."
Thus we can put those under Skills.
We have "Preferred Experience Experience supporting cybersecurity systems in federal or other highly regulated environments. Vendor certifications in Qmulos, CyberArk, or SailPoint." That could go under Qualifications (preferred).
We have "Physical Requirements" maybe not needed as a heading; could be omitted because not in allowed headings. Could drop.
We have Benefits: "Life at Fearless" description about culture, Purple Culture, etc. That's substantive. Also "Compensation & Engagement Details" about competitive contract rates, final rates based on experience, etc. That's Pay.
We have Schedule: "This is a fully remote 1099 contractor engagement requiring approximately 15–20 hours per week, with work performed between 9:00 a.m. and 5:00 p.m. EST". That's schedule.
Thus we will output sections: About the role, Responsibilities, Requirements (maybe we combine experience and skill?), Skills, Qualifications (preferred), Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID.
We must use for headings, - for lists,
for prose.
We need to preserve all substantive info, not invent or summarize away detail. Must not include filler like "commensurate with experience". The Pay section currently says "Fearless is committed to offering competitive contract rates that reflect the expertise, experience, and value our independent contractors bring to client engagements. Final rates are determined based on experience, qualifications, project requirements, and market considerations." That's not a specific number; it's vague but still substantive? It's not a specific number but it's not filler like "commensurate with experience". It's a statement about how rates determined. It's okay to include.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state them.
Now we need to extract the exact text for each section, preserving details.
Let's gather:
About the role:
"At Fearless, we are seeking a 1099 contractor to serve as a Cybersecurity Trainer for a 24-week, hands-on workforce development program designed to advance federal cybersecurity personnel from foundational knowledge through operational proficiency. The program focuses on enterprise identity and access management, privileged access management, and continuous security monitoring platforms. The trainer will deliver live, instructor-led sessions using a pre-designed curriculum, translating complex cybersecurity technologies into structured learning experiences through hands-on labs, scenario-based exercises, and practical skills validation. This is a fully remote 1099 contractor engagement requiring approximately 15–20 hours per week, with work performed between 9:00 a.m. and 5:00 p.m. EST"
But schedule part we might move to Schedule section. However About the role could include the remote and duration; schedule details maybe separate. We'll keep About the role without schedule? The instruction: include a section only when posting has real specific content. We have schedule info; we can put schedule in its own section. So About the role could exclude schedule sentence. Let's split:
About the role: "At Fearless, we are seeking a 1099 contractor to serve as a Cybersecurity Trainer for a 24-week, hands-on workforce development program designed to advance federal cybersecurity personnel from foundational knowledge through operational proficiency. The program focuses on enterprise identity and access management, privileged access management, and continuous security monitoring platforms. The trainer will deliver live, instructor-led sessions using a pre-designed curriculum, translating complex cybersecurity technologies into structured learning experiences through hands-on labs, scenario-based exercises, and practical skills validation."
Schedule: "This is a fully remote 1099 contractor engagement requiring approximately 15–20 hours per week, with work performed between 9:00 a.m. and 5:00 p.m. EST."
Now Responsibilities: list from "Your Responsibilities In This Role" bullet points (they are sentences separated by periods). We need to convert to
- . Let's extract each responsibility sentence:
- Deliver engaging instructor-led virtual cybersecurity training sessions aligned to Government-approved curriculum, learning objectives, and proficiency requirements.
- Develop and maintain course materials including instructor guides, student guides, presentations, demonstrations, lab exercises, assessments, and technical documentation.
- Configure, validate, and test training lab environments and sandbox systems before each cohort to ensure successful hands-on exercise completion.
- Facilitate realistic operational scenarios involving administration, configuration, troubleshooting, security operations, integration, and recovery activities.
- Provide instruction supporting Qmulos Q-Compliance and Q-BA², CyberArk Privileged Access Management, and SailPoint IdentityIQ platforms.
- Administer baseline, formative, and post-training assessments and evaluate participant performance against defined learning objectives and competency thresholds.
- Monitor attendance, participation, lab completion, assessment results, and skill progression and provide required information for LMS and program reporting.
- Identify participants requiring additional assistance and provide targeted coaching, remediation, office hours, or supplemental exercises as appropriate.
- Coordinate with the Program Manager, stakeholders, technical SMEs, LMS personnel, and other instructors to maintain consistent delivery across cohorts.
- Capture lessons learned and participant feedback and recommend curriculum, lab, pacing, or instructional improvements for subsequent cohorts.
- Ensure instructional materials and delivery comply with applicable security, privacy, accessibility, and Section 508 requirements.
Now Requirements: The mandatory experience/skill requirements. The section "Work Experience Project Skill and Experience Requirements" includes:
"Minimum of 5 years of experience in cybersecurity engineering, administration, operations, technical training, or closely related discipline.
Demonstrated experience explaining complex technical concepts to audiences with varying levels of technical proficiency.
Practical experience administering, engineering, implementing, or supporting enterprise cybersecurity technologies.
Proven capability independently conducting technical demonstrations, facilitating hands-on labs, diagnosing student lab issues, and evaluating practical competency."
We could treat these as requirements. Also there is "Strong knowledge in Identity and Access Management, Identity Governance and Administration, Privileged Access Management, or security compliance and continuous monitoring." etc. Those are knowledge statements; could be Skills.
Thus Requirements section will contain the four bullet points above.
Skills section: list of strong knowledge statements:
- Strong knowledge in Identity and Access Management, Identity Governance and Administration, Privileged Access Management, or security compliance and continuous monitoring.
- Strong knowledge in NIST Risk Management Framework, security control implementation and assessment, logging and SIEM, or cloud security.
- Strong knowledge in AWS, APIs, system integration, automation, troubleshooting, or DevSecOps and security operations.
We could also include "Practical experience administering, engineering, implementing, or supporting enterprise cybersecurity technologies." but that's already in Requirements. We'll keep as is.
Qualifications (Preferred): "Experience supporting cybersecurity systems in federal or other highly regulated environments. Vendor certifications in Qmulos, CyberArk, or SailPoint."
Benefits: The "Life at Fearless" paragraph(s). Let's extract:
"Life at Fearless We're a digital integration consultancy on a mission to build a better tomorrow. At Fearless, we combine technology, people, and organizational development to solve meaningful problems. Through iterative development, we deliver smart, user-friendly solutions that make technology work better—for everyone. But great technology is only part of the story. What truly sets Fearless apart is our Purple Culture and our commitment to building meaningful partnerships with the people who help us deliver exceptional results. What Makes Us Purple? Whether you're a team member, contractor, or partner, our Purple Culture influences how we collaborate, communicate, and solve problems together. Being Purple Means You Contribute to work that creates meaningful impactCollaborate with people who value curiosity, innovation, and continuous improvementBring your expertise to challenging and rewarding projectsWork with transparency, trust, and mutual respectHelp create solutions that improve the lives of the people who use themJoin a community committed to equity, inclusion, and belonging"
We need to preserve all substantive info; we can keep as paragraphs. Might need to add spaces where missing (like "impactCollaborate" should be spaced). But we must not invent or summarize away detail; we can keep as is but maybe add a space for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing content, just formatting? Might be okay but safer to keep original text exactly. However original text missing spaces; we could keep as is. It's okay.
We could split into multiple
for readability but not required.
Pay section: "Fearless is committed to offering competitive contract rates that reflect the expertise, experience, and value our independent contractors bring to client engagements. Final rates are determined based
- for lists,
for prose. We need to preserve all substantive info, not invent or summarize away detail. Must not include filler like "commensurate with experience". The Pay section currently says "Fearless is committed to offering competitive contract rates that reflect the expertise, experience, and value our independent contractors bring to client engagements. Final rates are determined based on experience, qualifications, project requirements, and market considerations." That's not a specific number; it's vague but still substantive? It's not a specific number but it's not filler like "commensurate with experience". It's a statement about how rates determined. It's okay to include. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state them. Now we need to extract the exact text for each section, preserving details. Let's gather: About the role: "At Fearless, we are seeking a 1099 contractor to serve as a Cybersecurity Trainer for a 24-week, hands-on workforce development program designed to advance federal cybersecurity personnel from foundational knowledge through operational proficiency. The program focuses on enterprise identity and access management, privileged access management, and continuous security monitoring platforms. The trainer will deliver live, instructor-led sessions using a pre-designed curriculum, translating complex cybersecurity technologies into structured learning experiences through hands-on labs, scenario-based exercises, and practical skills validation. This is a fully remote 1099 contractor engagement requiring approximately 15–20 hours per week, with work performed between 9:00 a.m. and 5:00 p.m. EST" But schedule part we might move to Schedule section. However About the role could include the remote and duration; schedule details maybe separate. We'll keep About the role without schedule? The instruction: include a section only when posting has real specific content. We have schedule info; we can put schedule in its own section. So About the role could exclude schedule sentence. Let's split: About the role: "At Fearless, we are seeking a 1099 contractor to serve as a Cybersecurity Trainer for a 24-week, hands-on workforce development program designed to advance federal cybersecurity personnel from foundational knowledge through operational proficiency. The program focuses on enterprise identity and access management, privileged access management, and continuous security monitoring platforms. The trainer will deliver live, instructor-led sessions using a pre-designed curriculum, translating complex cybersecurity technologies into structured learning experiences through hands-on labs, scenario-based exercises, and practical skills validation." Schedule: "This is a fully remote 1099 contractor engagement requiring approximately 15–20 hours per week, with work performed between 9:00 a.m. and 5:00 p.m. EST." Now Responsibilities: list from "Your Responsibilities In This Role" bullet points (they are sentences separated by periods). We need to convert to
- . Let's extract each responsibility sentence:
- Deliver engaging instructor-led virtual cybersecurity training sessions aligned to Government-approved curriculum, learning objectives, and proficiency requirements.
- Develop and maintain course materials including instructor guides, student guides, presentations, demonstrations, lab exercises, assessments, and technical documentation.
- Configure, validate, and test training lab environments and sandbox systems before each cohort to ensure successful hands-on exercise completion.
- Facilitate realistic operational scenarios involving administration, configuration, troubleshooting, security operations, integration, and recovery activities.
- Provide instruction supporting Qmulos Q-Compliance and Q-BA², CyberArk Privileged Access Management, and SailPoint IdentityIQ platforms.
- Administer baseline, formative, and post-training assessments and evaluate participant performance against defined learning objectives and competency thresholds.
- Monitor attendance, participation, lab completion, assessment results, and skill progression and provide required information for LMS and program reporting.
- Identify participants requiring additional assistance and provide targeted coaching, remediation, office hours, or supplemental exercises as appropriate.
- Coordinate with the Program Manager, stakeholders, technical SMEs, LMS personnel, and other instructors to maintain consistent delivery across cohorts.
- Capture lessons learned and participant feedback and recommend curriculum, lab, pacing, or instructional improvements for subsequent cohorts.
- Ensure instructional materials and delivery comply with applicable security, privacy, accessibility, and Section 508 requirements.
Now Requirements: The mandatory experience/skill requirements. The section "Work Experience Project Skill and Experience Requirements" includes:
"Minimum of 5 years of experience in cybersecurity engineering, administration, operations, technical training, or closely related discipline.
Demonstrated experience explaining complex technical concepts to audiences with varying levels of technical proficiency.
Practical experience administering, engineering, implementing, or supporting enterprise cybersecurity technologies.
Proven capability independently conducting technical demonstrations, facilitating hands-on labs, diagnosing student lab issues, and evaluating practical competency."
We could treat these as requirements. Also there is "Strong knowledge in Identity and Access Management, Identity Governance and Administration, Privileged Access Management, or security compliance and continuous monitoring." etc. Those are knowledge statements; could be Skills.
Thus Requirements section will contain the four bullet points above.
Skills section: list of strong knowledge statements:
- Strong knowledge in Identity and Access Management, Identity Governance and Administration, Privileged Access Management, or security compliance and continuous monitoring.
- Strong knowledge in NIST Risk Management Framework, security control implementation and assessment, logging and SIEM, or cloud security.
- Strong knowledge in AWS, APIs, system integration, automation, troubleshooting, or DevSecOps and security operations.
We could also include "Practical experience administering, engineering, implementing, or supporting enterprise cybersecurity technologies." but that's already in Requirements. We'll keep as is.
Qualifications (Preferred): "Experience supporting cybersecurity systems in federal or other highly regulated environments. Vendor certifications in Qmulos, CyberArk, or SailPoint."
Benefits: The "Life at Fearless" paragraph(s). Let's extract:
"Life at Fearless We're a digital integration consultancy on a mission to build a better tomorrow. At Fearless, we combine technology, people, and organizational development to solve meaningful problems. Through iterative development, we deliver smart, user-friendly solutions that make technology work better—for everyone. But great technology is only part of the story. What truly sets Fearless apart is our Purple Culture and our commitment to building meaningful partnerships with the people who help us deliver exceptional results. What Makes Us Purple? Whether you're a team member, contractor, or partner, our Purple Culture influences how we collaborate, communicate, and solve problems together. Being Purple Means You Contribute to work that creates meaningful impactCollaborate with people who value curiosity, innovation, and continuous improvementBring your expertise to challenging and rewarding projectsWork with transparency, trust, and mutual respectHelp create solutions that improve the lives of the people who use themJoin a community committed to equity, inclusion, and belonging"
We need to preserve all substantive info; we can keep as paragraphs. Might need to add spaces where missing (like "impactCollaborate" should be spaced). But we must not invent or summarize away detail; we can keep as is but maybe add a space for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing content, just formatting? Might be okay but safer to keep original text exactly. However original text missing spaces; we could keep as is. It's okay.
We could split into multiple
for readability but not required. Pay section: "Fearless is committed to offering competitive contract rates that reflect the expertise, experience, and value our independent contractors bring to client engagements. Final rates are determined based
- . Let's extract each responsibility sentence:
- Deliver engaging instructor-led virtual cybersecurity training sessions aligned to Government-approved curriculum, learning objectives, and proficiency requirements.
- Develop and maintain course materials including instructor guides, student guides, presentations, demonstrations, lab exercises, assessments, and technical documentation.
- Configure, validate, and test training lab environments and sandbox systems before each cohort to ensure successful hands-on exercise completion.
- Facilitate realistic operational scenarios involving administration, configuration, troubleshooting, security operations, integration, and recovery activities.
- Provide instruction supporting Qmulos Q-Compliance and Q-BA², CyberArk Privileged Access Management, and SailPoint IdentityIQ platforms.
- Administer baseline, formative, and post-training assessments and evaluate participant performance against defined learning objectives and competency thresholds.
- Monitor attendance, participation, lab completion, assessment results, and skill progression and provide required information for LMS and program reporting.
- Identify participants requiring additional assistance and provide targeted coaching, remediation, office hours, or supplemental exercises as appropriate.
- Coordinate with the Program Manager, stakeholders, technical SMEs, LMS personnel, and other instructors to maintain consistent delivery across cohorts.
- Capture lessons learned and participant feedback and recommend curriculum, lab, pacing, or instructional improvements for subsequent cohorts.
- Ensure instructional materials and delivery comply with applicable security, privacy, accessibility, and Section 508 requirements.
Now Requirements: The mandatory experience/skill requirements. The section "Work Experience Project Skill and Experience Requirements" includes:
"Minimum of 5 years of experience in cybersecurity engineering, administration, operations, technical training, or closely related discipline.
Demonstrated experience explaining complex technical concepts to audiences with varying levels of technical proficiency.
Practical experience administering, engineering, implementing, or supporting enterprise cybersecurity technologies.
Proven capability independently conducting technical demonstrations, facilitating hands-on labs, diagnosing student lab issues, and evaluating practical competency."
We could treat these as requirements. Also there is "Strong knowledge in Identity and Access Management, Identity Governance and Administration, Privileged Access Management, or security compliance and continuous monitoring." etc. Those are knowledge statements; could be Skills.
Thus Requirements section will contain the four bullet points above.
Skills section: list of strong knowledge statements:
- Strong knowledge in Identity and Access Management, Identity Governance and Administration, Privileged Access Management, or security compliance and continuous monitoring.
- Strong knowledge in NIST Risk Management Framework, security control implementation and assessment, logging and SIEM, or cloud security.
- Strong knowledge in AWS, APIs, system integration, automation, troubleshooting, or DevSecOps and security operations.
We could also include "Practical experience administering, engineering, implementing, or supporting enterprise cybersecurity technologies." but that's already in Requirements. We'll keep as is.
Qualifications (Preferred): "Experience supporting cybersecurity systems in federal or other highly regulated environments. Vendor certifications in Qmulos, CyberArk, or SailPoint."
Benefits: The "Life at Fearless" paragraph(s). Let's extract:
"Life at Fearless We're a digital integration consultancy on a mission to build a better tomorrow. At Fearless, we combine technology, people, and organizational development to solve meaningful problems. Through iterative development, we deliver smart, user-friendly solutions that make technology work better—for everyone. But great technology is only part of the story. What truly sets Fearless apart is our Purple Culture and our commitment to building meaningful partnerships with the people who help us deliver exceptional results. What Makes Us Purple? Whether you're a team member, contractor, or partner, our Purple Culture influences how we collaborate, communicate, and solve problems together. Being Purple Means You Contribute to work that creates meaningful impactCollaborate with people who value curiosity, innovation, and continuous improvementBring your expertise to challenging and rewarding projectsWork with transparency, trust, and mutual respectHelp create solutions that improve the lives of the people who use themJoin a community committed to equity, inclusion, and belonging"
We need to preserve all substantive info; we can keep as paragraphs. Might need to add spaces where missing (like "impactCollaborate" should be spaced). But we must not invent or summarize away detail; we can keep as is but maybe add a space for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Adding a space is not inventing content, just formatting? Might be okay but safer to keep original text exactly. However original text missing spaces; we could keep as is. It's okay.
We could split into multiple