Proposal Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove application instructions, privacy notice, etc. We need to parse the posting. Content: Intro: "Do you like working with different project teams in a fast-paced environment? Are you interested in joining an organization focused on making a positive impact? If so, we’d like to talk with you about growing with us. We are currently seeking a full-time Proposal Manager for the following EnSafe offices: Pensacola, FL, Tampa, FL, Jacksonville, FL, Atlanta, GA, Charleston, SC, Cincinnati, OH, Dallas, TX, Houston, TX, Huntsville, AL, Jackson, MS, Knoxville, TN, and Nashville, TN. This is an excellent opportunity to join and grow with EnSafe, getting involved in a variety of projects for a diverse range of clients across the globe. As a Proposal Manager, you will work on a wide range of projects in an environment that fosters creativity, collaboration at all levels, a culture of support, and professional growth. EnSafe emphasizes empowering staff to practice our profession passionately and without limitations. Our proposal managers are energetic, highly organized, meticulous individuals who help each other do remarkable things every day. We collaborate with our technical staff to help EnSafers shine in our proposals and marketing content. We face challenges together, and we win together." That's about the role. Then "Duties/Responsibilities In this role, you will: Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations, including: Scheduling to meet tight deadlinesLeading meetings, assigning tasks, and managing the performance of the proposal team.Writing and/or editing project descriptions, resumes, and highly technical informationComplying with client requirements and deadlinesIncorporating reviews/feedback before submission to meet EnSafe brand standards" We need to format as list. Then "Skills/Experience Minimum Skills and Requirements: A bachelor’s degree is required.Minimum 8 years of experience in the A/E/C industryProficiency in InDesignExperience writing proposals using AI/ChatGPT.Microsoft Office Suite and Adobe’s Creative Suite.Creative writing skills required.Ability to multi-task, prioritize requests, and set expectations.Competent in working in a challenging environment while prioritizing time management.Familiarity with the Shipley Review process.Graphics experience is a plus!" That's skills/experience. Then "Why Join EnSafe? Employee-Owned Advantage EnSafe is 100% employee-owned, with an ESOP (Employee Stock Ownership Plan) since 1997. That means when EnSafe succeeds, you succeed too, turning company growth directly into shared rewards.Commitment to Growth and Wellness The company supports personalized career development, mentorship, and employee wellness initiatives such as health tracking tools.Purpose‑Driven Work EnSafe’s mission focuses on impactful environmental, health, and safety consulting—making a real difference in communities and is backed by its long-standing technical credibility. Safety as a Value, Not Just a Service Safety is deeply embedded in our culture, prioritizing employee well-being in addition to helping clients maintain compliance. We stress that “safety is part of everything we do.”A Culture of Freedom & Ownership At EnSafe, our career philosophy is built on freedom. The freedom to take initiative, achieve your goals, and shape your own career path. Employees are encouraged to pursue growth in a flexible, entrepreneurial environment. Challenging, Creative Work Workdays at EnSafe are anything but ordinary: fast-paced, dynamic, and filled with opportunities to tackle projects in environmental consulting, health & safety, engineering, and technology. Every day calls for creativity, innovation, and agile problem-solving." That's benefits. Then "About EnSafe EnSafe began as a two-person firm in 1980, navigating complex regulatory compliance issues on behalf of our clients. We nurture our people with growth and development opportunities. We build enduring, trustful relationships with each of our clients, with a focus on high ethical and safety standards. We build this reputation by attracting high-quality people and retaining them for the long term. At EnSafe, we are dedicated to fostering a diverse and authentic workplace, so if you’re excited about this role but your experience doesn’t align perfectly with every qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles at our company." That's about company. We need sections: About the role (intro), Responsibilities (duties), Requirements (maybe combine skills/experience?), Qualifications (maybe education/experience?), Skills (maybe list of specific skills), Benefits (why join), Pay (none), Schedule (none). Since no pay or schedule info, we omit those sections. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. We need to use

for section headings. We need

• for any list of duties/requirements/benefits. We need

  for prose. We need to not repeat job title as heading. We need to not put Job ID. We need to remove boilerplate: EEO, privacy notice, etc. Also remove "Check us out on the web at www.ensafe.com Applicant Privacy Notice | AI use in Hiring". Also remove "EnSafe is committed to being an EEO employer..." etc. Also remove "About EnSafe" maybe we can keep as "About the company" but we have "About EnSafe" as a section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About EnSafe" could go under "About the role"? Actually "About the role" is for role description. "About EnSafe" could be under "About the role" or maybe we could create a separate section but not in list; but instruction says prefer a few substantive sections over many thin ones. Could combine company info into "About the role" or maybe "About the role" includes role and company overview. However they said "About the role" heading for section headings (e.g. About the role, Responsibilities...). So we should have an "About the role" section that includes the introductory paragraphs about role and maybe company overview. But we also have "About EnSafe" separate; we could incorporate that into About the role. Thus sections: - About the role: includes intro paragraphs about role, offices, opportunity, environment, etc., plus maybe the About EnSafe paragraph. - Responsibilities: list of duties. - Requirements: maybe education and years experience? Could be under Requirements. - Qualifications: maybe degree, experience, etc. But we might combine Requirements and Qualifications? The instruction says use those headings when there is real specific content. We have both "Minimum Skills and Requirements" and also "Skills/Experience". Could treat "Requirements" as education + years experience, and "Qualifications" as specific skills (InDesign, AI, etc.)? Or we could have "Skills" section for specific skills, and "Requirements" for education/experience. Let's decide: Requirements: Bachelor's degree required; Minimum 8 years experience in A/E/C industry. Qualifications: Proficiency in InDesign; Experience writing proposals using AI/ChatGPT; Microsoft Office Suite and Adobe Creative Suite; Creative writing skills; Ability to multi-task, prioritize requests, set expectations; Competent in challenging environment while prioritizing time management; Familiarity with Shipley Review process; Graphics experience is a plus. Skills: maybe same as qualifications? But we could treat "Skills" as the list of specific skills (InDesign, AI, etc.) and "Qualifications" as the broader competencies (multi-task, etc.). However the instruction says we can have sections like Skills, Requirements, Qualifications. We need to avoid thin sections. Perhaps combine Requirements and Qualifications into one "Requirements" section that includes education, experience, and skills. But then we would have no Qualifications section. That's okay if we don't have specific content for Qualifications. But we have content for both; we could split. Better: Use "Requirements" for education and years experience. Use "Skills" for technical skills (InDesign, AI, MS Office, Adobe Suite, Creative writing, Shipley Review, Graphics). Use "Qualifications" for soft skills/competencies (multi-task, prioritize, time management, etc.). But that may be thin. Alternatively, we could have "Requirements" (education + experience), "Skills" (technical skills), and "Benefits" (why join). That seems reasonable. We also need "About the role" section. We must not create Pay or Schedule sections. Now we need to extract lists. Responsibilities list: - Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations, including: - Scheduling to meet tight deadlines - Leading meetings, assigning tasks, and managing the performance of the proposal team. - Writing and/or editing project descriptions, resumes, and highly technical information - Complying with client requirements and deadlines - Incorporating reviews/feedback before submission to meet EnSafe brand standards We need to preserve the leading sentence maybe as part of list item? The original: "Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations, including:" then list. We could make first item: "Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations, including:" then subitems? But we need flat list. Could combine: "Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations, including scheduling to meet tight deadlines, leading meetings, assigning tasks, managing the performance of the proposal team, writing and/or editing project descriptions, resumes, and highly technical information, complying with client requirements and deadlines, incorporating reviews/feedback before submission to meet EnSafe brand standards." But that loses structure. Better to keep as list items: first item: "Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations" then separate items for each subpoint. However the subpoints are part of that sentence. We could treat the leading phrase as a list item and then each subsequent as separate items. That's okay. Thus list: - Understand how to lead and manage the development of complex proposals and other responses for federal and commercial solicitations - Scheduling to meet tight deadlines - Leading meetings, assigning tasks, and managing the performance of the proposal team - Writing and/or editing project descriptions, resumes, and highly technical information - Complying with client requirements and deadlines - Incorporating reviews/feedback before submission to meet EnSafe brand standards Now Requirements: Bachelor's degree required; Minimum 8 years of experience in the A/E/C industry. We could list as: - Bachelor’s degree required - Minimum 8 years of experience in the A/E/C industry Skills: technical skills: - Proficiency in InDesign - Experience writing proposals using AI/ChatGPT - Microsoft Office Suite - Adobe Creative Suite - Creative writing skills - Familiarity with the Shipley Review process - Graphics experience is a plus Qualifications (soft skills/competencies): - Ability to multi-task, prioritize requests, and set expectations - Competent in working in a challenging environment while prioritizing time management We could also include "Ability to multi-task, prioritize requests, and set expectations." and "Competent in working in a challenging environment while prioritizing time management." Now Benefits: Why Join EnSafe? We have several bullet-like paragraphs but not explicit list. We could turn into list: - Employee-Owned Advantage: EnSafe is 100% employee-owned, with an ESOP since 1997; when EnSafe succeeds, you succeed too. - Commitment to Growth and Wellness: Supports personalized career