Configuration Manager
AV · Jessup, MD · 3 wk ago
On-siteEngineering$102k–$145k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting.
Let's parse.
Job Title: Configuration Manager (not to be repeated as heading). Overview: "Worker Type Regular Overview Job Description AV is seeking a Configuration Manager to be responsible for configuration management (CM) of developmental and operational systems for a high-priority Federal Intelligence Program."
We can have an "About the role" section with that prose.
Responsibilities: list of key responsibilities: "work on developmental and operational teams to create and maintain configuration baselines (development, test, production, etc.) supporting developmental and operational systems; use or recommends automated CM tools to implement CM policies and procedures; Develop or modify CM plans, policies, and procedures tailored to the complexity and scope of the developmental or operational system; implement CM discipline for the entire life cycle of systems from initial requirements/capabilities baselines to system end-of-life; and perform change control and configuration audits."
Also there is a "You’d Like To Do This" section with many bullet-like sentences. Those are also responsibilities/desired tasks. We should combine them into responsibilities list.
Requirements: "You're Required To Have This TS//SCI with Polygraph 6 years of relevant experience with Bachelor’s degree; or +10 years of relevant experience with high school diploma. One year of experience using a source code control system for a developmental program of similar scope and complexity is required."
Also maybe "Qualifications" could be same as requirements? But we can have Requirements section.
Skills: maybe mention using automated CM tools, DOORS, Eclipse, source code control, hardware/software version control, etc. Could be a Skills section.
Pay: Salary Range: $102,000 – $145,000. Also note compensation & benefits notice but we should not include filler like "commensurate with experience". The salary range is specific, so we can include Pay section.
Benefits: "Benefits: AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also link to benefits page. So Benefits section.
Schedule: The 9/80 work schedule is mentioned under benefits, but could be schedule. However schedule is a separate section if we have explicit schedule info. The posting mentions "a 9/80 work schedule". That's schedule info. Could be placed under Benefits or Schedule. Since we have a Benefits section already, we could include schedule there, but we could also make a Schedule section with "9/80 work schedule". The rule: prefer few substantive sections over many thin ones. So maybe include schedule within Benefits. But we could also have Benefits and Schedule separate if both have content. However schedule is just a mention; we could include it under Benefits. Let's keep Benefits includes medical, dental, vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown.
We should not include boilerplate like EEO, ITAR, etc. Remove those.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all responsibilities sentences exactly? We can rephrase slightly but must preserve meaning. Better to copy sentences as list items.
Let's extract responsibilities:
From "Key responsibilities will include:" list:
- work on developmental and operational teams to create and maintain configuration baselines (development, test, production, etc.) supporting developmental and operational systems
- use or recommends automated CM tools to implement CM policies and procedures
- Develop or modify CM plans, policies, and procedures tailored to the complexity and scope of the developmental or operational system
- implement CM discipline for the entire life cycle of systems from initial requirements/capabilities baselines to system end-of-life
- perform change control and configuration audits
Then "You’d Like To Do This" list (many sentences). Let's break them into distinct items:
- Assist in implementing hardware and software version control processes, policies, and procedures.
- Assist in the use of configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items.
- Understand basic concepts and assist in documenting hardware and software configuration management processes and procedures.
- Implement hardware and software version control processes, policies, and procedures.
- Understand basic concepts, assist in maintaining and developing the environment for hardware and software product build, staging, testing and integration.
- Assist in defining and implementing hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrating those scripts with the hardware and software build process.
- Utilize configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items.
- Maintain the CM environment for hardware and software product build, staging, testing and integration
- Develop hardware and software version control processes, policies and procedures and ensure that they are followed on hardware and software development projects.
- Apply concepts and define and implement hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrate those scripts with the hardware and software build process.
- Serve as an advisor to (or non-voting member of) Government Change Control Board (CCB).
Some duplicates: "Assist in the use of configuration management tools..." and "Utilize configuration management tools..." similar. We could keep both but maybe combine to avoid duplication. However rule: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove duplicated lines. So we should deduplicate.
Let's list unique responsibilities:
From key responsibilities:
1. Work on developmental and operational teams to create and maintain configuration baselines (development, test, production, etc.) supporting developmental and operational systems.
2. Use or recommend automated CM tools to implement CM policies and procedures.
3. Develop or modify CM plans, policies, and procedures tailored to the complexity and scope of the developmental or operational system.
4. Implement CM discipline for the entire life cycle of systems from initial requirements/capabilities baselines to system end-of-life.
5. Perform change control and configuration audits.
From You’d Like To Do This (deduplicate):
- Assist in implementing hardware and software version control processes, policies, and procedures.
- Assist in the use of configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items.
- Understand basic concepts and assist in documenting hardware and software configuration management processes and procedures.
- Implement hardware and software version control processes, policies, and procedures.
- Understand basic concepts, assist in maintaining and developing the environment for hardware and software product build, staging, testing and integration.
- Assist in defining and implementing hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrating those scripts with the hardware and software build process.
- Maintain the CM environment for hardware and software product build, staging, testing and integration.
- Develop hardware and software version control processes, policies and procedures and ensure that they are followed on hardware and software development projects.
- Apply concepts and define and implement hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrate those scripts with the hardware and software build process.
- Serve as an advisor to (or non-voting member of) Government Change Control Board (CCB).
Note some overlap: "Assist in the use of configuration management tools..." and "Utilize configuration management tools..." are similar but not identical; one says assist in the use, the other utilize. Could be considered duplicate? Might be considered similar but not exact. Safer to keep both? The instruction says remove duplicated lines. If they are not exactly same line, maybe keep. But we could combine to avoid redundancy. However risk of summarizing away detail. I'd keep both as separate items because they convey slightly different nuance (assist vs utilize). But they are very similar. I'd keep one maybe "Assist in the use/utilize configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items." Could combine. But that would be summarizing. I'd keep both to be safe.
Now Requirements section:
- TS//SCI with Polygraph clearance.
- 6 years of relevant experience with Bachelor’s degree; or +10 years of relevant experience with high school diploma.
- One year of experience using a source code control system for a developmental program of similar scope and complexity is required.
We could also note "You're Required To Have This TS//SCI with Polygraph". That's a requirement.
Skills section: maybe list specific skills: configuration management, automated CM tools (DOORS, Eclipse), source code control, hardware/software version control, CM plans/policies/procedures, change control, configuration audits, product build scripts, hardware/software build process integration, Government Change Control Board advisory.
But we might not need a separate Skills section if responsibilities cover them. However we can include Skills to highlight tools and methodologies.
But rule: prefer few substantive sections over many thin ones. So maybe we combine Skills into Responsibilities or Requirements. However we already have Responsibilities and Requirements. Adding Skills may be thin. Could omit Skills.
Pay section: Salary Range: $102,000 – $145,000.
Benefits section: medical, dental, vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown.
We should not include the link to benefits page? That's substantive? It's a reference; could be included as a link within Benefits. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive. So we can include Benefits information within the Benefits paragraph.
Also we have "Principals only need apply. NO agencies please." That's application instruction, should be removed.
"We also encourage you to review our company website..." that's also boilerplate? Might be considered navigation? Probably remove.
"We are proud to be an EEO/AA Equal Opportunity Employer..." remove.
Now produce HTML.
Structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to extract content from posting.
Let's parse.
Job Title: Configuration Manager (not to be repeated as heading). Overview: "Worker Type Regular Overview Job Description AV is seeking a Configuration Manager to be responsible for configuration management (CM) of developmental and operational systems for a high-priority Federal Intelligence Program."
We can have an "About the role" section with that prose.
Responsibilities: list of key responsibilities: "work on developmental and operational teams to create and maintain configuration baselines (development, test, production, etc.) supporting developmental and operational systems; use or recommends automated CM tools to implement CM policies and procedures; Develop or modify CM plans, policies, and procedures tailored to the complexity and scope of the developmental or operational system; implement CM discipline for the entire life cycle of systems from initial requirements/capabilities baselines to system end-of-life; and perform change control and configuration audits."
Also there is a "You’d Like To Do This" section with many bullet-like sentences. Those are also responsibilities/desired tasks. We should combine them into responsibilities list.
Requirements: "You're Required To Have This TS//SCI with Polygraph 6 years of relevant experience with Bachelor’s degree; or +10 years of relevant experience with high school diploma. One year of experience using a source code control system for a developmental program of similar scope and complexity is required."
Also maybe "Qualifications" could be same as requirements? But we can have Requirements section.
Skills: maybe mention using automated CM tools, DOORS, Eclipse, source code control, hardware/software version control, etc. Could be a Skills section.
Pay: Salary Range: $102,000 – $145,000. Also note compensation & benefits notice but we should not include filler like "commensurate with experience". The salary range is specific, so we can include Pay section.
Benefits: "Benefits: AV offers an excellent benefits package including medical, dental vision, 401K with company matching, a 9/80 work schedule and a paid holiday shutdown." Also link to benefits page. So Benefits section.
Schedule: The 9/80 work schedule is mentioned under benefits, but could be schedule. However schedule is a separate section if we have explicit schedule info. The posting mentions "a 9/80 work schedule". That's schedule info. Could be placed under Benefits or Schedule. Since we have a Benefits section already, we could include schedule there, but we could also make a Schedule section with "9/80 work schedule". The rule: prefer few substantive sections over many thin ones. So maybe include schedule within Benefits. But we could also have Benefits and Schedule separate if both have content. However schedule is just a mention; we could include it under Benefits. Let's keep Benefits includes medical, dental, vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown.
We should not include boilerplate like EEO, ITAR, etc. Remove those.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all responsibilities sentences exactly? We can rephrase slightly but must preserve meaning. Better to copy sentences as list items.
Let's extract responsibilities:
From "Key responsibilities will include:" list:
- work on developmental and operational teams to create and maintain configuration baselines (development, test, production, etc.) supporting developmental and operational systems
- use or recommends automated CM tools to implement CM policies and procedures
- Develop or modify CM plans, policies, and procedures tailored to the complexity and scope of the developmental or operational system
- implement CM discipline for the entire life cycle of systems from initial requirements/capabilities baselines to system end-of-life
- perform change control and configuration audits
Then "You’d Like To Do This" list (many sentences). Let's break them into distinct items:
- Assist in implementing hardware and software version control processes, policies, and procedures.
- Assist in the use of configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items.
- Understand basic concepts and assist in documenting hardware and software configuration management processes and procedures.
- Implement hardware and software version control processes, policies, and procedures.
- Understand basic concepts, assist in maintaining and developing the environment for hardware and software product build, staging, testing and integration.
- Assist in defining and implementing hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrating those scripts with the hardware and software build process.
- Utilize configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items.
- Maintain the CM environment for hardware and software product build, staging, testing and integration
- Develop hardware and software version control processes, policies and procedures and ensure that they are followed on hardware and software development projects.
- Apply concepts and define and implement hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrate those scripts with the hardware and software build process.
- Serve as an advisor to (or non-voting member of) Government Change Control Board (CCB).
Some duplicates: "Assist in the use of configuration management tools..." and "Utilize configuration management tools..." similar. We could keep both but maybe combine to avoid duplication. However rule: preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove duplicated lines. So we should deduplicate.
Let's list unique responsibilities:
From key responsibilities:
1. Work on developmental and operational teams to create and maintain configuration baselines (development, test, production, etc.) supporting developmental and operational systems.
2. Use or recommend automated CM tools to implement CM policies and procedures.
3. Develop or modify CM plans, policies, and procedures tailored to the complexity and scope of the developmental or operational system.
4. Implement CM discipline for the entire life cycle of systems from initial requirements/capabilities baselines to system end-of-life.
5. Perform change control and configuration audits.
From You’d Like To Do This (deduplicate):
- Assist in implementing hardware and software version control processes, policies, and procedures.
- Assist in the use of configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items.
- Understand basic concepts and assist in documenting hardware and software configuration management processes and procedures.
- Implement hardware and software version control processes, policies, and procedures.
- Understand basic concepts, assist in maintaining and developing the environment for hardware and software product build, staging, testing and integration.
- Assist in defining and implementing hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrating those scripts with the hardware and software build process.
- Maintain the CM environment for hardware and software product build, staging, testing and integration.
- Develop hardware and software version control processes, policies and procedures and ensure that they are followed on hardware and software development projects.
- Apply concepts and define and implement hardware and software configuration management processes and procedures, such as creating product build scripts and procedures, and integrate those scripts with the hardware and software build process.
- Serve as an advisor to (or non-voting member of) Government Change Control Board (CCB).
Note some overlap: "Assist in the use of configuration management tools..." and "Utilize configuration management tools..." are similar but not identical; one says assist in the use, the other utilize. Could be considered duplicate? Might be considered similar but not exact. Safer to keep both? The instruction says remove duplicated lines. If they are not exactly same line, maybe keep. But we could combine to avoid redundancy. However risk of summarizing away detail. I'd keep both as separate items because they convey slightly different nuance (assist vs utilize). But they are very similar. I'd keep one maybe "Assist in the use/utilize configuration management tools (e.g. DOORS, Eclipse) to store, track, and manage configuration items." Could combine. But that would be summarizing. I'd keep both to be safe.
Now Requirements section:
- TS//SCI with Polygraph clearance.
- 6 years of relevant experience with Bachelor’s degree; or +10 years of relevant experience with high school diploma.
- One year of experience using a source code control system for a developmental program of similar scope and complexity is required.
We could also note "You're Required To Have This TS//SCI with Polygraph". That's a requirement.
Skills section: maybe list specific skills: configuration management, automated CM tools (DOORS, Eclipse), source code control, hardware/software version control, CM plans/policies/procedures, change control, configuration audits, product build scripts, hardware/software build process integration, Government Change Control Board advisory.
But we might not need a separate Skills section if responsibilities cover them. However we can include Skills to highlight tools and methodologies.
But rule: prefer few substantive sections over many thin ones. So maybe we combine Skills into Responsibilities or Requirements. However we already have Responsibilities and Requirements. Adding Skills may be thin. Could omit Skills.
Pay section: Salary Range: $102,000 – $145,000.
Benefits section: medical, dental, vision, 401K with company matching, 9/80 work schedule, paid holiday shutdown.
We should not include the link to benefits page? That's substantive? It's a reference; could be included as a link within Benefits. The instruction: preserve ALL substantive information; do not invent or summarize away detail. The link is substantive. So we can include Benefits information within the Benefits paragraph.
Also we have "Principals only need apply. NO agencies please." That's application instruction, should be removed.
"We also encourage you to review our company website..." that's also boilerplate? Might be considered navigation? Probably remove.
"We are proud to be an EEO/AA Equal Opportunity Employer..." remove.
Now produce HTML.
Structure:
About the role
AV is seeking a Configuration Manager to be responsible for configuration management (CM) of developmental and operational systems for a high-priority Federal Intelligence Program.
Responsibilities
- ... ...
Requirements
- TS//SCI with Polygraph clearance.
- 6 years of relevant experience with Bachelor’s degree; or 10+ years of relevant experience with high school diploma.
- One year of experience using a source code control system for a developmental program of similar scope and complexity is required.
Pay
Salary range: $102,000 – $145,000.
Benefits
AV offers an excellent benefits package including medical, dental, vision, 401K with company matching, a 9/80 work schedule, and a paid holiday shutdown. For more information, see AV benefits.
We should not include Schedule separate. Check for any other substantive content: "Who We Are" and "What We Do" sections about company description. That's substantive? It's about the company, could be considered "About the company". But we already have About the role. The instruction: "Prefer a few substantive sections over many thin ones." The company description may be considered boilerplate? It's not required but could be considered "About the company". However the instruction says do not repeat job title as heading, but we can include About the role. The company description may be considered extra but still substantive. However many job postings include that; but we might treat it as "About the company" which