Sr Proposal Manager
govconcareershub.com · Englewood, CO · 1 mo ago
OTHR$165k–$227k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro paragraph before responsibilities. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have content for About the role (intro paragraph). Responsibilities (list). Qualifications (must have and preferred). Skills maybe separate? The posting includes qualifications with many bullet-like sentences; we can treat as Requirements/Qualifications. Benefits: mention SNC offers generous benefit package, including medical, dental, vision, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more. Also annual incentive pay based upon performance that is commensurate with level (but that's vague). Pay: we have salary range $165,010 - $226,889 USD yearly and also Estimated Starting Salary Range: $165,010.21 - $226,889.04. So we can include Pay section with that range. Schedule: not mentioned. So omit Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions (like "This posting will be open for application for a minimum of 5 days...") - that's application instructions? It's about posting duration; maybe consider as boilerplate? It's not exactly application instructions but could be considered metadata; but we can drop it as not substantive. Also "Important Notice" about security clearance is substantive (must have). Should we include that in Qualifications? It's a requirement: ability to obtain and maintain Secret US Security Clearance, US Citizenship required. So include in Qualifications/Requirements.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities list items exactly as given, but we can format as
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have content for About the role (intro paragraph). Responsibilities (list). Qualifications (must have and preferred). Skills maybe separate? The posting includes qualifications with many bullet-like sentences; we can treat as Requirements/Qualifications. Benefits: mention SNC offers generous benefit package, including medical, dental, vision, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more. Also annual incentive pay based upon performance that is commensurate with level (but that's vague). Pay: we have salary range $165,010 - $226,889 USD yearly and also Estimated Starting Salary Range: $165,010.21 - $226,889.04. So we can include Pay section with that range. Schedule: not mentioned. So omit Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, cookie, legal, application instructions (like "This posting will be open for application for a minimum of 5 days...") - that's application instructions? It's about posting duration; maybe consider as boilerplate? It's not exactly application instructions but could be considered metadata; but we can drop it as not substantive. Also "Important Notice" about security clearance is substantive (must have). Should we include that in Qualifications? It's a requirement: ability to obtain and maintain Secret US Security Clearance, US Citizenship required. So include in Qualifications/Requirements.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities list items exactly as given, but we can format as - . Must not lose any detail.
We need to decide sections: About the role (intro paragraph). Responsibilities (list). Qualifications (maybe split into Required and Preferred? But we only have Qualifications heading; we can include both Must Have and Qualifications We Prefer under same section, maybe using
for each. Could also have Requirements and Qualifications separate but we have only one Qualifications heading allowed; but we can also have Requirements heading if we have content. The posting has "Qualifications You Must Have" and "Qualifications We Prefer". So we could have two sections: Requirements (for Must Have) and Qualifications (for Preferred). But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections. That seems appropriate.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. (Schedule omitted). Skills: we have some skill mentions in qualifications (e.g., proficiency in proposal management software, APMP certification, Adobe Creative Suite, MS Word). Could treat as Skills section. But we already have qualifications covering many skill-like items. However we can still create Skills section for those specific skill items: proficiency in proposal management software and tools, APMP certification, Adobe Creative Suite, MS Word formatting etc. But we must not duplicate content; we need to preserve all substantive info. If we split, we need to ensure we don't lose any info. Could keep qualifications as is (including education, experience, etc.) and then Skills section for specific technical skills. However the qualifications already include many skill items; moving them to Skills might be okay as long as we keep them somewhere. But we must not invent or summarize away detail; we can rephrase? We should preserve exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't require exact wording, but we should not lose detail. We can rephrase as long as we keep the info. Safer to keep qualifications section with all qualification details (including education, experience, security clearance, etc.) and then Skills section for the specific skill items like proficiency in proposal management software, APMP certification, Adobe Creative Suite, MS Word. However some of those appear also in qualifications (e.g., "Demonstrated success in managing high-value proposals." etc.) Might be overlapping. To avoid duplication, we could keep qualifications as is and not create Skills section unless there is distinct skill content not already covered. The posting includes: "Strong proficiency in proposal management software and tools." (under Qualifications We Prefer). Also "Association for Proposal Management Professionals (APMP) Certification." "Understanding of one or more of Adobe Creative Suite applications: InDesign, Illustrator, Photoshop, Acrobat." "Skills in the use of MS Word, i.e., formatting, outlining, graphics integration, for the use of proposals." Those are skill-like. Could put them in Skills section. Meanwhile the Must Have includes many other qualifications like education, experience, security clearance, etc. So we can split.
Thus sections: About the role, Responsibilities, Requirements (Must Have), Qualifications (Preferred), Skills, Benefits, Pay.
Now we need to craft HTML.
We'll output:
About the role
... intro paragraph ...
Then Responsibilities: Responsibilities
- ... each responsibility ...
We need to extract responsibilities list from the posting. The responsibilities paragraph is a long sentence with many items separated by periods. We need to split into list items preserving each duty. Let's parse:
"As an integral member of the Company’s Business Development organization and Proposal Center, the Senior Proposal Manager manages the proposal development center and oversees the center’s staff in the development and submission of task order and project proposals for both government and commercial customers."
That's one duty.
"Responsible for planning, organizing, facilitating and executing IDIQ proposals (both Prime and subcontractor role), and for assuring the company’s proposal development process is clearly disseminated and efficiently implemented and administered."
Second.
"Provide direct and indirect management of the company's overall bid and proposal efforts and direct management of the Proposal Center."
Third.
"Directly or through others, ensure proposal preparation activities are timely and proposals submitted are professional to include writing, editing, graphics, formatting, estimating/pricing, data call coordination, production and submission of all technical and cost volumes."
Fourth.
"Coordinate and guide proposal management activities and workflow such as creating and distributing all documents required for proposal development including proposal template, compliance matrix, schedule, and color review sheets; leading internal proposal status meetings and reviews; serving as the main POC for subcontractor proposal input; and acting as color reviewer on task order and project proposals managed by the Proposal Center staff."
Fifth.
"Exercise ownership of proposal processes and take responsibility for quality and compliance of all proposals supported by the Proposal Center."
Sixth.
"Direct the work of Proposal Center staff to ensure development of proposal products in accordance with RFP compliance and company business development goals."
Seventh.
"Participate in capture discussions to ensure understanding of bid strategy."
Eighth.
"Directly manage proposals and act as a color reviewer on proposals managed by other staff."
Ninth.
"Supervise Proposal Center staff, including Proposal Managers, Proposal Analysts and Proposal Writers."
Tenth.
"Responsible for the overall direction, coordination, and evaluation of all."
Eleventh? Actually "Responsible for the overall direction, coordination, and evaluation of all." seems incomplete; maybe it's "Responsible for the overall direction, coordination, and evaluation of all." We'll keep as is.
"Carries out supervisory responsibilities in accordance with the company’s policies and applicable law."
Twelfth.
"Other responsibilities include interviewing, hiring, planning employees’ training, assigning and directing work; appraising performance; rewarding and disciplining employees; addressing complaints and resolving problems."
Thirteenth.
We'll keep each as - .
Now Requirements (Must Have) list:
- Bachelor’s degree in a related field.
- 8+ years of experience in related field
- Relevant experience can be considered as a substitute for the required educational qualifications. In the absence of a degree, a minimum of 12 years of related experience is required.
- Higher level relevant degree may substitute for experience.
- Demonstrated success in managing high-value proposals.
- Expertise utilizing proposal management software and AI tools.
- Advanced experience with simultaneously managing multiple proposals of all sizes from proposal planning to delivery.
- Extensive technical, proposal writing and proposal management experience with emphasis in technical products and logistics services.
- Excellent written and oral communication skills and the ability to motivate/work with others.
- Ability to work successfully in a highly collaborative, fast-paced environment.
- Understanding of program management to include, scheduling, organization and technical management/system engineering concepts.
- Full understanding of Pricing Volumes to include work breakdown structure (WBS) and Basis of Estimate (BOE), including government contracting proposal processes and procedures.
- Prior experience in a Lead role; the ability to mentor, train, guide and inspect the work of team members and coordinate project tasks to ensure milestones are met.
- Strong communication skills, including the ability to clearly express technical concepts in verbal and written forms; ability to tailor conversations to adapt to technical vs. non-technical audiences.
- Background in the Aerospace and Defense Industry, the US Department of Defense or US Military.
- The ability to obtain and maintain a Secret U.S. Security Clearance is required
- U.S. Citizenship status is required as this position needs an active U.S. Security Clearance for employment. Non-U.S. citizens may not be eligible to obtain a security clearance. (This is from Important Notice but it's a requirement.)
We need to preserve all; we can combine citizenship requirement as part of Requirements.
Now Qualifications (Preferred) list:
- Strong proficiency in proposal management software and tools.
- Self-starter and a problem solver; must have the ability to see the big picture and implement changes as required.
- Association for Proposal Management Professionals (APMP) Certification.
- Understanding of one or more of Adobe Creative Suite applications: InDesign, Illustrator, Photoshop, Acrobat.
- Skills in the use of MS Word, i.e., formatting, outlining, graphics integration, for the use of proposals.
Now Skills section: maybe we can put the preferred qualifications here? But we already have Qualifications (Preferred). Could rename Qualifications to Preferred Qualifications and Skills to something else? But we have both headings allowed. Let's make Qualifications = Preferred Qualifications, and Skills = maybe technical skills like APMP, Adobe, MS Word. However the preferred list already includes those. To avoid duplication, we could make Qualifications = Preferred Qualifications (including all preferred items) and omit Skills section. But we need to decide if we want Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So better to not create Skills if we can incorporate those details elsewhere. We could put the preferred items under Qualifications section. That seems fine. Then we don't need Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Now Benefits: we have "SNC offers annual incentive pay based upon performance that is commensurate with the level of the position. SNC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more."
We need to include Benefits section with that info. Also note annual incentive pay is also compensation but we already have Pay section; we can mention incentive pay in Benefits or Pay. We'll keep Benefits as the benefit package; Pay as salary range.
Now Pay: we have salary range $165,010 - $226,889 USD yearly and also Estimated Starting Salary Range: $165,010.21 - $226,889.04. We'll include both maybe as a
- for each. Could also have Requirements and Qualifications separate but we have only one Qualifications heading allowed; but we can also have Requirements heading if we have content. The posting has "Qualifications You Must Have" and "Qualifications We Prefer". So we could have two sections: Requirements (for Must Have) and Qualifications (for Preferred). But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections. That seems appropriate.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. (Schedule omitted). Skills: we have some skill mentions in qualifications (e.g., proficiency in proposal management software, APMP certification, Adobe Creative Suite, MS Word). Could treat as Skills section. But we already have qualifications covering many skill-like items. However we can still create Skills section for those specific skill items: proficiency in proposal management software and tools, APMP certification, Adobe Creative Suite, MS Word formatting etc. But we must not duplicate content; we need to preserve all substantive info. If we split, we need to ensure we don't lose any info. Could keep qualifications as is (including education, experience, etc.) and then Skills section for specific technical skills. However the qualifications already include many skill items; moving them to Skills might be okay as long as we keep them somewhere. But we must not invent or summarize away detail; we can rephrase? We should preserve exact wording? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't require exact wording, but we should not lose detail. We can rephrase as long as we keep the info. Safer to keep qualifications section with all qualification details (including education, experience, security clearance, etc.) and then Skills section for the specific skill items like proficiency in proposal management software, APMP certification, Adobe Creative Suite, MS Word. However some of those appear also in qualifications (e.g., "Demonstrated success in managing high-value proposals." etc.) Might be overlapping. To avoid duplication, we could keep qualifications as is and not create Skills section unless there is distinct skill content not already covered. The posting includes: "Strong proficiency in proposal management software and tools." (under Qualifications We Prefer). Also "Association for Proposal Management Professionals (APMP) Certification." "Understanding of one or more of Adobe Creative Suite applications: InDesign, Illustrator, Photoshop, Acrobat." "Skills in the use of MS Word, i.e., formatting, outlining, graphics integration, for the use of proposals." Those are skill-like. Could put them in Skills section. Meanwhile the Must Have includes many other qualifications like education, experience, security clearance, etc. So we can split.
Thus sections: About the role, Responsibilities, Requirements (Must Have), Qualifications (Preferred), Skills, Benefits, Pay.
Now we need to craft HTML.
We'll output:
- ... each responsibility ...
- . Now Requirements (Must Have) list: - Bachelor’s degree in a related field. - 8+ years of experience in related field - Relevant experience can be considered as a substitute for the required educational qualifications. In the absence of a degree, a minimum of 12 years of related experience is required. - Higher level relevant degree may substitute for experience. - Demonstrated success in managing high-value proposals. - Expertise utilizing proposal management software and AI tools. - Advanced experience with simultaneously managing multiple proposals of all sizes from proposal planning to delivery. - Extensive technical, proposal writing and proposal management experience with emphasis in technical products and logistics services. - Excellent written and oral communication skills and the ability to motivate/work with others. - Ability to work successfully in a highly collaborative, fast-paced environment. - Understanding of program management to include, scheduling, organization and technical management/system engineering concepts. - Full understanding of Pricing Volumes to include work breakdown structure (WBS) and Basis of Estimate (BOE), including government contracting proposal processes and procedures. - Prior experience in a Lead role; the ability to mentor, train, guide and inspect the work of team members and coordinate project tasks to ensure milestones are met. - Strong communication skills, including the ability to clearly express technical concepts in verbal and written forms; ability to tailor conversations to adapt to technical vs. non-technical audiences. - Background in the Aerospace and Defense Industry, the US Department of Defense or US Military. - The ability to obtain and maintain a Secret U.S. Security Clearance is required - U.S. Citizenship status is required as this position needs an active U.S. Security Clearance for employment. Non-U.S. citizens may not be eligible to obtain a security clearance. (This is from Important Notice but it's a requirement.) We need to preserve all; we can combine citizenship requirement as part of Requirements. Now Qualifications (Preferred) list: - Strong proficiency in proposal management software and tools. - Self-starter and a problem solver; must have the ability to see the big picture and implement changes as required. - Association for Proposal Management Professionals (APMP) Certification. - Understanding of one or more of Adobe Creative Suite applications: InDesign, Illustrator, Photoshop, Acrobat. - Skills in the use of MS Word, i.e., formatting, outlining, graphics integration, for the use of proposals. Now Skills section: maybe we can put the preferred qualifications here? But we already have Qualifications (Preferred). Could rename Qualifications to Preferred Qualifications and Skills to something else? But we have both headings allowed. Let's make Qualifications = Preferred Qualifications, and Skills = maybe technical skills like APMP, Adobe, MS Word. However the preferred list already includes those. To avoid duplication, we could make Qualifications = Preferred Qualifications (including all preferred items) and omit Skills section. But we need to decide if we want Skills section. The instruction: "Prefer a few substantive sections over many thin ones." So better to not create Skills if we can incorporate those details elsewhere. We could put the preferred items under Qualifications section. That seems fine. Then we don't need Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: we have "SNC offers annual incentive pay based upon performance that is commensurate with the level of the position. SNC offers a generous benefit package, including medical, dental, and vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, tuition reimbursement, and more." We need to include Benefits section with that info. Also note annual incentive pay is also compensation but we already have Pay section; we can mention incentive pay in Benefits or Pay. We'll keep Benefits as the benefit package; Pay as salary range. Now Pay: we have salary range $165,010 - $226,889 USD yearly and also Estimated Starting Salary Range: $165,010.21 - $226,889.04. We'll include both maybe as a
About the role
... intro paragraph ...
Then Responsibilities: