Operations Lead
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: EEO etc. Also remove navigation/cookie etc. We need to preserve all substantive information.
We have content: About Concept Plus (company description). Should we include that? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also have other sections if content exists. The "About Concept Plus" is company overview; maybe we can include as a section "About the Company" but not in list. However instruction says use those examples; not strictly limited. But we should include sections only when posting has real specific content. The posting includes "About Concept Plus" paragraph. It's substantive. Should we include? Probably yes, as it's about the company. Could be a section "About the Company". Not in examples but okay. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are typical headings; we can also use others if needed. Safer to include "About the Company" as . Also "About The Role" heading.
We need to extract responsibilities (What You'll Do) with bullet points. Those are many bullet-like paragraphs. We'll turn each bullet into
- . The responsibilities are grouped under headings: Operational Sustainment & Continuity, Incident & Operational Coordination, Cross-Functional Integration, Operational Reporting & Governance, Process Improvement & Modernization Support. We could either keep those as subheadings (
? but only allowed for section headings). We could keep them as
bold? But instruction: Use
- for any list of duties/requirements/benefits. So we can flatten all duties into a single list under a "Responsibilities" heading. Or we could have multiple lists under subheadings but subheadings not allowed? Might be okay to use
for each subheading? But they said use for section headings (e.g. About the role, Responsibilities, Requirements...). It doesn't forbid other headings, but to be safe we can just have one Responsibilities section with a flat list of all duties. However we risk losing grouping nuance but still preserve all info. The instruction: "Prefer a few substantive sections over many thin ones." So better to have few sections: About the Company, About the Role, Responsibilities, Qualifications (maybe combine Required and Preferred), Benefits (if any). Benefits: The posting mentions "We offer competitive pay, comprehensive health, dental, and vision insurance, paid life insurance, paid time off, 11 paid holidays, performance bonuses, tuition reimbursement, unlimited training, and the opportunity to thrive in a collaborative, flexible, and innovative environment." That's benefits. So we need a Benefits section with list.
Pay: Not specified exact numbers, just "competitive pay". That's vague; we should not create Pay section unless posting actually states them. It says "competitive pay" which is not a specific number; but it's still mention of pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive pay". That is a statement about pay, albeit vague. Should we include Pay section? It says "competitive pay". That's a statement. I'd include a Pay section with that sentence. However they also said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is not exactly filler; it's a qualifier. Might be okay. But to be safe, maybe we can incorporate pay into Benefits section as part of compensation. But they said Benefits section for benefits; Pay separate. I'd include Pay section with that sentence.
Schedule: Not mentioned. So no Schedule section.
Qualifications: We have Required Qualifications and Preferred Qualifications. We'll combine into Qualifications section with two sublists? Could split into Required and Preferred as subheadings (? but not allowed). Could just list all qualifications with indication? Better to have two subsections: Required Qualifications and Preferred Qualifications as each? That would be many sections but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." Having two qualification sections may be okay. Could also have one Qualifications section with two lists: Required and Preferred. We'll do that: Qualifications
then
Required:
... then Preferred:
... That keeps one section.
Skills: Not explicitly separate; qualifications cover skills. Could omit Skills section.
Now we need to remove boilerplate: EEO statement, navigation, etc. Also remove "For more information, visit www.conceptplus.com." That's maybe not substantive? It's a link; could be considered boilerplate but it's info about company. Might keep? It's not essential; but it's not boilerplate like legal. Might keep as part of About Concept Plus paragraph. But we can drop it as it's not essential. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The website link is not those; it's just a reference. Might keep.
Now produce HTML.
Structure:
About the Company
Concept Plus is a mission-focused technology solutions provider that transforms IT concepts into impactful solutions for federal agencies. Headquartered in Fairfax, VA, we bring the agility, responsiveness, and customer intimacy of a small business combined with the quality and infrastructure of a larger firm. Recognized as an award-winning Oracle partner, we have delivered innovative solutions across Defense, Intelligence, Civilian, Health IT, and Tribal sectors. Our highly certified experts build systems that drive efficiency, accelerate modernization, and ensure mission outcomes with certainty. We offer competitive pay, comprehensive health, dental, and vision insurance, paid life insurance, paid time off, 11 paid holidays, performance bonuses, tuition reimbursement, unlimited training, and the opportunity to thrive in a collaborative, flexible, and innovative environment. For more information, visit www.conceptplus.com.
About the Role
Concept Plus is seeking an Operations Lead to support operational sustainment, continuity, and service delivery for a client program. This role is responsible for leading and coordinating day-to-day operational execution across infrastructure, cybersecurity, database administration, testing, development support, configuration management, and business support functions to ensure stable, responsive, and uninterrupted mission operations. This position requires a strong understanding of client IT operational processes and enterprise technology environments, including DevSecOps CI/CD ecosystems, Cloud One environments, Oracle-based systems, and Java application stacks operating across classified and unclassified DISA and cloud-hosted environments. The Operations Lead serves as the central operational coordination lead responsible for integrating sustainment activities across the Operations Support Team while collaborating closely with Agile development teams, Platform/DevSecOps teams, and client stakeholders. This role ensures operational issues, deployments, environment changes, service requests, and sustainment activities are effectively coordinated, communicated, and aligned with program priorities and mission objectives. The ideal candidate possesses strong operational leadership capabilities, enterprise systems awareness, incident coordination experience, and the ability to maintain operational stability within a fast-paced, mission-critical environment undergoing ongoing modernization and DevSecOps transformation.
Responsibilities
- Lead daily operational support activities to maintain REMIS system stability, availability, and continuity of service
- Coordinate sustainment activities across the Operations Support Team including: Database Administration, Systems Administration, Cybersecurity / IA, Testing & Validation, Development Support, Business Intelligence / Functional Support, Configuration Management & Documentation
- Ensure operational support aligns with contractual service expectations, operational procedures, and mission requirements
- Support continuity of operations during transition, onboarding, release, and modernization activities
- Lead operational incident coordination, issue triage, escalation management, and service restoration activities
- Coordinate cross-functional resolution efforts for operational issues and production-impacting events
- Monitor operational risks, recurring issues, and service performance trends
- Support root cause analysis and corrective action coordination for operational failures or degraded service conditions
- Serve as the operational integration point between: Operations support teams, Agile development teams, Platform/DevSecOps teams, Government stakeholders
- Coordinate operational readiness activities associated with deployments, releases, environment changes, and sustainment initiatives
- Ensure operational impacts and dependencies are communicated across teams
- Maintain visibility into operational status, risks, issues, escalations, and support activities
- Support operational reporting activities including dashboards, metrics, AIR logs, and status reporting
- Provide timely communication and operational transparency to Program Management and Government stakeholders
- Assist in maintaining operational procedures, support documentation, and sustainment processes
- Identify opportunities to improve operational efficiency, automation, monitoring, and support responsiveness
- Support adoption of Agile, DevSecOps, and CI/CD operational practices where applicable
- Collaborate with engineering and platform teams to improve operational readiness and deployment quality
- Contribute to lessons learned, continuous improvement initiatives, and operational maturity efforts
Qualifications
Required:
- Secret – Fully Cleared Only, must confirm clearance is active
- DoD 8140 intermediate certification or DoD 8570 IAM Level II certifications or higher
- US Citizens Only
- Bachelor’s degree in Information Technology, Computer Science, Engineering, Information Systems, or related discipline (or equivalent experience)
- 5+ years of experience supporting enterprise operational environments, production support, or IT sustainment activities
- Experience coordinating operational support activities across multiple technical disciplines
- Experience supporting mission-critical or high-availability systems
- Strong understanding of operational support processes, issue management, and sustainment coordination
- Experience working within Agile or hybrid Agile delivery environments
- Strong communication, organizational, and coordination skills
- Ability to manage competing priorities in fast-paced operational environments
Preferred:
- Experience working with Agile development teams of 20+ FTEs and be familiar with Agile methodologies
- Prior Department of Defense (DoD) or Air Force support experience
- Experience supporting enterprise systems within secure cloud or hybrid environments
- Familiarity with DevSecOps, CI/CD, or modern operational support models
- Experience using Jira, Confluence, Service Management, or operational tracking platforms
- Experience supporting operational transitions or onboarding efforts
- ITIL, Scrum, Agile, Security+, or related certifications preferred
- Experience supporting data-intensive or enterprise maintenance systems preferred
Benefits
- Competitive pay
- Comprehensive health, dental, and vision insurance
- Paid life insurance
- Paid time off
- 11 paid holidays
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: EEO etc. Also remove navigation/cookie etc. We need to preserve all substantive information. We have content: About Concept Plus (company description). Should we include that? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also have other sections if content exists. The "About Concept Plus" is company overview; maybe we can include as a section "About the Company" but not in list. However instruction says use those examples; not strictly limited. But we should include sections only when posting has real specific content. The posting includes "About Concept Plus" paragraph. It's substantive. Should we include? Probably yes, as it's about the company. Could be a section "About the Company". Not in examples but okay. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies those are typical headings; we can also use others if needed. Safer to include "About the Company" as . Also "About The Role" heading.
We need to extract responsibilities (What You'll Do) with bullet points. Those are many bullet-like paragraphs. We'll turn each bullet into
. Also "About The Role" heading. We need to extract responsibilities (What You'll Do) with bullet points. Those are many bullet-like paragraphs. We'll turn each bullet into
? but only allowed for section headings). We could keep them as
bold? But instruction: Use
- for any list of duties/requirements/benefits. So we can flatten all duties into a single list under a "Responsibilities" heading. Or we could have multiple lists under subheadings but subheadings not allowed? Might be okay to use
for each subheading? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements...). It doesn't forbid other headings, but to be safe we can just have one Responsibilities section with a flat list of all duties. However we risk losing grouping nuance but still preserve all info. The instruction: "Prefer a few substantive sections over many thin ones." So better to have few sections: About the Company, About the Role, Responsibilities, Qualifications (maybe combine Required and Preferred), Benefits (if any). Benefits: The posting mentions "We offer competitive pay, comprehensive health, dental, and vision insurance, paid life insurance, paid time off, 11 paid holidays, performance bonuses, tuition reimbursement, unlimited training, and the opportunity to thrive in a collaborative, flexible, and innovative environment." That's benefits. So we need a Benefits section with list. Pay: Not specified exact numbers, just "competitive pay". That's vague; we should not create Pay section unless posting actually states them. It says "competitive pay" which is not a specific number; but it's still mention of pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive pay". That is a statement about pay, albeit vague. Should we include Pay section? It says "competitive pay". That's a statement. I'd include a Pay section with that sentence. However they also said "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is not exactly filler; it's a qualifier. Might be okay. But to be safe, maybe we can incorporate pay into Benefits section as part of compensation. But they said Benefits section for benefits; Pay separate. I'd include Pay section with that sentence. Schedule: Not mentioned. So no Schedule section. Qualifications: We have Required Qualifications and Preferred Qualifications. We'll combine into Qualifications section with two sublists? Could split into Required and Preferred as subheadings (
? but not allowed). Could just list all qualifications with indication? Better to have two subsections: Required Qualifications and Preferred Qualifications as
each? That would be many sections but still substantive. The instruction: "Prefer a few substantive sections over many thin ones." Having two qualification sections may be okay. Could also have one Qualifications section with two lists: Required and Preferred. We'll do that:
Qualifications
thenRequired:
- ... then
- Lead daily operational support activities to maintain REMIS system stability, availability, and continuity of service
- Coordinate sustainment activities across the Operations Support Team including: Database Administration, Systems Administration, Cybersecurity / IA, Testing & Validation, Development Support, Business Intelligence / Functional Support, Configuration Management & Documentation
- Ensure operational support aligns with contractual service expectations, operational procedures, and mission requirements
- Support continuity of operations during transition, onboarding, release, and modernization activities
- Lead operational incident coordination, issue triage, escalation management, and service restoration activities
- Coordinate cross-functional resolution efforts for operational issues and production-impacting events
- Monitor operational risks, recurring issues, and service performance trends
- Support root cause analysis and corrective action coordination for operational failures or degraded service conditions
- Serve as the operational integration point between: Operations support teams, Agile development teams, Platform/DevSecOps teams, Government stakeholders
- Coordinate operational readiness activities associated with deployments, releases, environment changes, and sustainment initiatives
- Ensure operational impacts and dependencies are communicated across teams
- Maintain visibility into operational status, risks, issues, escalations, and support activities
- Support operational reporting activities including dashboards, metrics, AIR logs, and status reporting
- Provide timely communication and operational transparency to Program Management and Government stakeholders
- Assist in maintaining operational procedures, support documentation, and sustainment processes
- Identify opportunities to improve operational efficiency, automation, monitoring, and support responsiveness
- Support adoption of Agile, DevSecOps, and CI/CD operational practices where applicable
- Collaborate with engineering and platform teams to improve operational readiness and deployment quality
- Contribute to lessons learned, continuous improvement initiatives, and operational maturity efforts
- Secret – Fully Cleared Only, must confirm clearance is active
- DoD 8140 intermediate certification or DoD 8570 IAM Level II certifications or higher
- US Citizens Only
- Bachelor’s degree in Information Technology, Computer Science, Engineering, Information Systems, or related discipline (or equivalent experience)
- 5+ years of experience supporting enterprise operational environments, production support, or IT sustainment activities
- Experience coordinating operational support activities across multiple technical disciplines
- Experience supporting mission-critical or high-availability systems
- Strong understanding of operational support processes, issue management, and sustainment coordination
- Experience working within Agile or hybrid Agile delivery environments
- Strong communication, organizational, and coordination skills
- Ability to manage competing priorities in fast-paced operational environments
- Experience working with Agile development teams of 20+ FTEs and be familiar with Agile methodologies
- Prior Department of Defense (DoD) or Air Force support experience
- Experience supporting enterprise systems within secure cloud or hybrid environments
- Familiarity with DevSecOps, CI/CD, or modern operational support models
- Experience using Jira, Confluence, Service Management, or operational tracking platforms
- Experience supporting operational transitions or onboarding efforts
- ITIL, Scrum, Agile, Security+, or related certifications preferred
- Experience supporting data-intensive or enterprise maintenance systems preferred
- Competitive pay
- Comprehensive health, dental, and vision insurance
- Paid life insurance
- Paid time off
- 11 paid holidays
Preferred:
- ... That keeps one section.
Skills: Not explicitly separate; qualifications cover skills. Could omit Skills section.
Now we need to remove boilerplate: EEO statement, navigation, etc. Also remove "For more information, visit www.conceptplus.com." That's maybe not substantive? It's a link; could be considered boilerplate but it's info about company. Might keep? It's not essential; but it's not boilerplate like legal. Might keep as part of About Concept Plus paragraph. But we can drop it as it's not essential. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The website link is not those; it's just a reference. Might keep.
Now produce HTML.
Structure:
About the Company
Concept Plus is a mission-focused technology solutions provider that transforms IT concepts into impactful solutions for federal agencies. Headquartered in Fairfax, VA, we bring the agility, responsiveness, and customer intimacy of a small business combined with the quality and infrastructure of a larger firm. Recognized as an award-winning Oracle partner, we have delivered innovative solutions across Defense, Intelligence, Civilian, Health IT, and Tribal sectors. Our highly certified experts build systems that drive efficiency, accelerate modernization, and ensure mission outcomes with certainty. We offer competitive pay, comprehensive health, dental, and vision insurance, paid life insurance, paid time off, 11 paid holidays, performance bonuses, tuition reimbursement, unlimited training, and the opportunity to thrive in a collaborative, flexible, and innovative environment. For more information, visit www.conceptplus.com.
About the Role
Concept Plus is seeking an Operations Lead to support operational sustainment, continuity, and service delivery for a client program. This role is responsible for leading and coordinating day-to-day operational execution across infrastructure, cybersecurity, database administration, testing, development support, configuration management, and business support functions to ensure stable, responsive, and uninterrupted mission operations. This position requires a strong understanding of client IT operational processes and enterprise technology environments, including DevSecOps CI/CD ecosystems, Cloud One environments, Oracle-based systems, and Java application stacks operating across classified and unclassified DISA and cloud-hosted environments. The Operations Lead serves as the central operational coordination lead responsible for integrating sustainment activities across the Operations Support Team while collaborating closely with Agile development teams, Platform/DevSecOps teams, and client stakeholders. This role ensures operational issues, deployments, environment changes, service requests, and sustainment activities are effectively coordinated, communicated, and aligned with program priorities and mission objectives. The ideal candidate possesses strong operational leadership capabilities, enterprise systems awareness, incident coordination experience, and the ability to maintain operational stability within a fast-paced, mission-critical environment undergoing ongoing modernization and DevSecOps transformation.
Responsibilities
Qualifications
Required:
Preferred:
Benefits