Business Development Executive - Huntsville

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Opportunity description (maybe About the role). Responsibilities list. Qualifications (Required and Desired). There's also "What You Can Expect" which could be Benefits? Actually it's culture description, not benefits. There's Pay Range. There's no explicit Benefits list, but there is mention of benefits in "What You Can Expect" and later: "Our broad and competitive mix of benefits options...". That is generic but mentions healthcare, wellness, financial, retirement, family support, continuing education, and time off benefits. That's specific enough? It lists types of benefits. Could include Benefits section. There's no Schedule info besides "Full time" and "Percentage of Travel Required: Up to 25%". Schedule could be "Full time". But schedule section only if posting actually states them. It does state "Time Type: Full time". That's schedule info. So we could include Schedule section with that. However we need to avoid filler like "commensurate with experience". Not relevant. We need to not repeat job title as heading. No Job ID. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should remove that. Also "CACI is an Equal Opportunity Employer..." remove. We need to include sections only when posting has real specific content. Let's extract: About the role: The paragraph after "Opportunity" maybe: "Lead business development efforts across the greater Huntsville, Alabama federal market. Support growth initiatives spanning all seven of CACI’s strategic markets. Build and expand customer relationships across Army, MDA, NASA, Space, Intelligence, and federal organizations. Identify, shape, and help capture new business opportunities aligned to customer mission priorities. Serve as a key representative for CACI within the Huntsville defense and aerospace ecosystem." That's substantive. Responsibilities: bullet list after "Responsibilities". We'll capture each line. Qualifications: There's "Qualifications Required" list and "Desired Qualifications". Could combine into Requirements? The spec says we can have sections: Requirements, Qualifications, Skills. We need to decide. Probably "Qualifications" section for required and desired. Could also split into Requirements (required) and Qualifications (desired). But we should not create thin sections. Maybe combine into one Qualifications section with both required and desired as sublists? But we need to follow instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading and list both required and desired under it. Could also have Requirements heading for required and Qualifications for desired? Might be okay but risk thin sections. The posting has both required and desired; we could put required under Requirements and desired under Qualifications. That seems logical. Let's do that. Skills: Not explicitly listed separate; but qualifications include skills like communication, etc. Could put under Skills? Might be thin. Better to not create Skills section if not explicit. The instruction: prefer a few substantive sections over many thin ones. So we can omit Skills. Benefits: There is description of benefits: "Our broad and competitive mix of benefits options is designed to support and protect employees and their families. At CACI, you will receive comprehensive benefits such as; healthcare, wellness, financial, retirement, family support, continuing education, and time off benefits." That's specific enough to list. We'll create Benefits section with ul list of those items. Pay: There's Pay Range: "$120,300 - $264,800". Also earlier "$120,300 - $264,800 USD yearly". We'll include Pay section with that. Schedule: There's "Time Type: Full time". Also "Percentage of Travel Required: Up to 25%" and "Type of Travel: Local". Travel could be part of schedule? Might be separate but we can include Schedule section with full time and travel info. However schedule section is for schedule; travel maybe not schedule but we could include as part of schedule. The instruction: include a section ONLY when posting has real, specific content for it. It does have schedule info (Full time). So we can include Schedule section with that. Travel info maybe also relevant but we could include in Schedule as bullet. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we don't repeat. Now produce HTML fragment:

  About the role

  Lead business development efforts across the greater Huntsville, Alabama federal market. Support growth initiatives spanning all seven of CACI’s strategic markets. Build and expand customer relationships across Army, MDA, NASA, Space, Intelligence, and federal organizations. Identify, shape, and help capture new business opportunities aligned to customer mission priorities. Serve as a key representative for CACI within the Huntsville defense and aerospace ecosystem.

  Responsibilities

  • Identify, qualify, and develop new business opportunities across the Huntsville market.
  • Build and maintain a multi-year pipeline aligned to growth objectives.
  • Develop and maintain relationships with government customers, industry partners, and key stakeholders.
  • Collaborate with operations, capture, proposal, pricing, contracts, and technical teams to pursue opportunities.
  • Monitor customer priorities, procurement forecasts, and acquisition trends.
  • Lead or support opportunity shaping activities including customer meetings, RFIs, white papers, and industry events.
  • Support capture activities including teaming strategies, competitive assessments, and win strategies.
  • Provide actionable market intelligence and customer insights to leadership teams.
  • Participate in milestone reviews, pipeline reviews, and strategic growth planning.
  • Coordinate across CACI business groups to align capabilities with customer mission needs.
  • Help strengthen CACI’s brand and presence within the Huntsville federal community.
  • Support growth on existing contracts and identify expansion opportunities.
  • Develop and maintain relationships with small business and industry teaming partners.
  • Communicate opportunity status, risks, and recommendations to executive leadership.
  • Represent CACI at customer engagements, conferences, and industry forums.

  Requirements

  • 10+ years of federal contracting business development, capture, or related growth experience.
  • Demonstrated experience supporting customers within the Huntsville federal market.
  • Proven ability to develop and manage a qualified opportunity pipeline.
  • Strong understanding of federal acquisition and procurement processes.
  • Experience collaborating across operational and functional teams to advance opportunities.
  • Proven ability to build and maintain customer and industry relationships.
  • Strong written and verbal communication skills.
  • Experience supporting defense, intelligence, space, missile defense, or federal civilian customers.
  • Bachelor’s degree or equivalent combination of education and experience.
  • US Citizen with the ability to obtain and maintain a U.S. Government security clearance.

  Qualifications

  • Existing customer relationships within Army, MDA, NASA, Space, or Intelligence organizations in Huntsville.
  • Experience supporting large and complex federal pursuits.
  • Familiarity with Shipley-based business development and capture processes.
  • Active Top Secret, or TS/SCI security clearance.
  • Experience supporting technology-focused solutions including cyber, software, AI/ML, cloud, or systems engineering.

  Benefits

  • Healthcare
  • Wellness
  • Financial
  • Retirement
  • Family support
  • Continuing education
  • Time off

  Pay

  $120,300 - $264,800 USD yearly

  Schedule

  Full time; up to 25% travel (local)

  Check for any duplicated content: We included "Opportunity" paragraph as About the role. Good. We removed EEO statement. We removed "What You Can Expect" culture description? Actually we omitted that; but is that substantive? It's about culture, integrity, trust, growth. Could be considered a section like "About the company" but not in allowed headings. Could be omitted as not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The culture description is substantive. But we don't have a heading for it; allowed headings are limited to those list. Could we put it under About the role? That might be mixing. Better to include a section like "About the role" already covers role description; culture could be separate but not in allowed headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. So we may need to incorporate culture description into existing sections, maybe under About the role or Benefits? But it's not benefits. Could be under About the role as additional prose. That would preserve the info. Let's add that paragraph to About the role after the opportunity description. Thus About the role will have two paragraphs: first about opportunity, second about culture/values. Let's extract culture paragraph: "What You Can Expect A culture of integrity. At CACI, we place character and innovation at the center of everything we do. As a valued team member, you’ll be part of a high-performing group dedicated to our customer’s missions and driven by a higher purpose – to ensure the safety of our nation. An environment of trust. CACI values the unique contributions that every employee brings to our company and our customers - every day. You’ll have the autonomy to take the time you need through a unique flexible time off benefit and have access to robust learning resources to make your ambitions a reality. A focus on continuous growth. Together, we will advance our nation's most critical missions, build on our lengthy track record of business success, and find opportunities to break new ground — in your career and in our legacy." We'll incorporate that as a second paragraph. Now ensure we didn't miss any other substantive info: "Minimum Clearance Required to Start: Top Secret" is covered in Requirements (US Citizen with ability to obtain and maintain clearance). Could also add explicit "Top Secret clearance required". But we have that in Requirements? Actually we have "US Citizen with the ability to obtain and maintain a U.S. Government security clearance." Not explicit Top Secret. The posting says Minimum Clearance Required to Start: Top Secret. We should include that. Add a line in Requirements: "Minimum clearance required to start: Top Secret". Or incorporate. Also "Job Category: Business Development and Marketing" maybe not needed. "Employee Type: Regular" maybe not needed. "Percentage of Travel Required: Up to 25% Type of Travel: Local" we included in Schedule. We should also include "Job Title: Business Development Executive - Huntsville" but we are told not to repeat job title as heading. Not needed. Now ensure we didn't include any boilerplate