Senior Business Development Manager

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to extract substantive info. Let's parse the posting: First paragraph: "Technology Service Corporation (TSC) is seeking a Senior Business Development Manager to support and grow our thriving company. This role is designed for an experienced business development professional with deep knowledge in federal contracting, business capture, and customer engagement within the Defense and Intelligence markets. The successful candidate will identify key areas to focus on strategic growth, opportunity shaping, and capture. They will support programs and pursuits in line with these technology areas: precision weapons solutions, radar and fire control systems and modeling, multi-intelligence analytic and engineering support, space systems, active and passive surveillance software and hardware, intelligence community activities, counter-UAS, Counter C5ISR-T, position, navigation, and timing (PNT), machine learning/artificial intelligence (ML/AI) and multi-domain solutions. They will have the responsibility for supporting and leading business capture efforts and winning new opportunities. This position requires someone who can independently manage business development portfolios, build executive-level customer relationships, and bring in significant new work through disciplined capture and proposal execution. The Senior Business Development Manager will travel as needed to customer sites and TSC offices in the National Capital Region and Huntsville, AL, with flexibility for remote work. They will collaborate directly with corporate executives, P&L owners, program managers, and technical leaders to position TSC for long-term growth." That's about the role. Then "Key Responsibilities" list bullet points. Then "Required Qualifications" bullet points. Then "Preferred Qualifications" bullet points. Then "TSC Benefits" paragraph. Then "Applying To TSC" etc which is application instructions and boilerplate; we should drop. Also there is EEO statement etc; drop. We need sections: About the role (maybe we can call it About the role). Responsibilities. Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe we can combine some skills from qualifications? But we have no explicit Skills section; we could omit if no specific content. However we could extract skills from qualifications: e.g., "Deep knowledge of the competitive landscape...", "Expertise in RF-based technologies...", "Strong history of influencing requirements...". But the instruction: include a section ONLY when the posting has real, specific content for it. We have content for Skills? The posting does not have a separate "Skills" heading, but we could create a Skills section if we can extract skill-related statements. However the rule says: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid creating a Skills section if we have content. But we must not create a section with filler/placeholder. We have skill-related content in Required and Preferred qualifications. Could we split them into Requirements (required qualifications) and Qualifications (preferred qualifications) and Skills (maybe extract skill statements). However the posting already has Required Qualifications and Preferred Qualifications; we could map Required Qualifications to Requirements section, Preferred Qualifications to Qualifications section. Then Skills maybe we could omit if no distinct skill list beyond those. But we could still include Skills if we pull out skill statements like "Deep knowledge of the competitive landscape...", "Expertise in RF-based technologies...", "Strong history of influencing requirements...". However those are already in qualifications. Might be redundant. Safer to follow the headings given: About the role, Responsibilities, Requirements, Qualifications, Benefits. Possibly also Skills if we have content. Pay and Schedule: we have no specific pay or schedule info (only mention flexible work schedules, remote work flexibility, travel 20-30%). Schedule: we have "Flexible Work Schedules" mentioned in benefits, and travel 20-30% mentioned under Preferred Qualifications. Could we create a Schedule section with that info? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state flexible work schedules and travel expectations. So we could include a Schedule section with that info. Benefits section we have: "TSC offers a stable work environment, a competitive salary, and a comprehensive benefit package; including Employee Stock Option Plan (ESOP) participation, 401k Plan, Flexible Work Schedules, Tuition Reimbursement, Co-Sponsored Health Plan, Paid Leave and much more." So we have Benefits content. Pay: they mention "competitive salary" but no specific numbers. That's vague; but it's still stating competitive salary. However the rule says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. "competitive salary" is somewhat vague but it's a statement. Is that considered filler? It's not a specific number, but it's still a statement. The rule about filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive salary" is not in that list, but it's still vague. However we might still include Pay section with that line? Might be considered not substantive enough. Safer to omit Pay section because no concrete figure. Schedule: we have "Flexible Work Schedules" and "travel 20-30%". That's specific enough. Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits, Schedule. We could also include Skills if we want, but we might skip to avoid thin sections. Now we need to format: use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Thus we need to copy the prose for About the role exactly as given (maybe minor editing to remove fluff? But we must preserve all substantive info; we can keep it as is, but we can break into paragraphs. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we will not include the "Applying To TSC" paragraph, nor the EEO statements, nor the "Only those candidates invited for an interview will be contacted." etc. We also need to drop duplicated lines: maybe there are none. Now craft HTML. First, About the role: we can put the introductory paragraph(s) into

  . Might be multiple sentences; we can keep as one

  . Then Responsibilities: heading

  Responsibilities

  then
  with each bullet. Responsibilities bullet points from posting: - Lead business development and capture activities across TSC’s core technology areas, from opportunity identification through proposal submission and award. - Develop and execute strategic account plans to expand business in targeted agencies and mission areas. - Shape opportunities in early stages by engaging customers with white papers, technical exchanges, and solution demonstrations. - Leverage established customer relationships within DoD, the Intelligence Community, and industry partners to identify and secure new business. - Provide leadership in proposal development, including win theme creation, competitive analysis, and customer-focused messaging. - Lead customer engagements and represent TSC at industry events, conferences, and forums. - Drive program expansion by identifying adjacent opportunities and securing new contract vehicles. We need to preserve exactly. Then Requirements: heading

  Requirements

  then
  with Required Qualifications bullet points: - Bachelor’s degree in engineering, aeronautics, business, or related technical discipline and 10–12 years of experience in business development, capture management, or related roles within the Defense or Intelligence Community markets. - Demonstrated track record of leading captures and winning new business valued in the multi-million-dollar range. - U.S. citizenship with the ability to obtain and maintain a DoD security clearance. - Deep knowledge of the competitive landscape in Missile Programs, Intelligence Community Space, ISR, EW, and/or SIGINT solutions, with established senior-level customer and partner relationships. Note: The bullet includes "and/or". Keep as is. Then Qualifications: heading

  Qualifications

  then
  with Preferred Qualifications bullet points: - Expertise in RF-based technologies such as RF/microwave technologies, integrated defense electronics, proximity, height-of-burst (HOB), unmanned RF payloads, or seeker sensors for missile, rocket, Electronic Warfare (EW), and/or gun-launched munition platforms. - Demonstrated capture experience with Intelligence Community, Navy R&D, and/or Space R&D customers. - Master’s degree in engineering, aeronautics, business, or a related technical discipline. - Experience leading cross-functional and geographically dispersed teams to deliver winning proposals and capture results. - Strong history of influencing requirements, shaping RFPs, and securing early positioning with key customers. - Excellent communication, leadership, and negotiation skills. - Based in the National Capital Region or Huntsville, AL, or willing to travel 20–30%. Note: The last bullet includes travel expectation; we might also move travel to Schedule section. But it's part of Preferred Qualifications. We could keep it there, but also we might create Schedule section with travel and flexible work schedules. However we must not duplicate content. The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. If we move it to Schedule, we would be removing from Qualifications; that would be summarizing away detail (removing). So we should keep it in Qualifications. Then Schedule section can include flexible work schedules from Benefits? Actually flexible work schedules is in Benefits paragraph. We could also keep it there. But we might create Schedule section with "Flexible Work Schedules" and "travel 20-30%" but that would duplicate. Duplication is not prohibited explicitly but we should avoid duplicated lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should not duplicate lines. So we should not repeat the same sentence in two places. So we need to decide where to place travel and flexible schedule info. Since they appear in Preferred Qualifications (travel) and Benefits (flexible work schedules). We could keep them in those sections and not create a separate Schedule section. However the instruction says we should include a section ONLY when the posting has real, specific content for it. It does not require us to create Schedule section if we already have that content elsewhere. So we can omit Schedule section. Similarly Benefits section we have content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now Benefits: we need to extract the benefits paragraph: "TSC offers a stable work environment, a competitive salary, and a comprehensive benefit package; including Employee Stock Option Plan (ESOP) participation, 401k Plan, Flexible Work Schedules, Tuition Reimbursement, Co-Sponsored Health Plan, Paid Leave and much more." We should format as
  • for list of benefits. The sentence includes a list after semicolon. We can break into list items: Employee Stock Option Plan (ESOP) participation, 401k Plan, Flexible Work Schedules, Tuition Reimbursement, Co-Sponsored Health Plan, Paid Leave and much more. The "and much more" is vague; but it's part of the posting. We should preserve it as a list item maybe "and much more". Could be considered filler? It's not in the filler list. We'll keep it. We could also include "stable work environment" and "competitive salary" as separate items? The sentence: "TSC offers a stable work environment,