Senior Manager, Business Development, Aerospace & Defense

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content: description includes "What You'll Do" (responsibilities), "What You Bring" (requirements/qualifications/skills), "Why This Opportunity?" (maybe benefits? but not explicit benefits). Also salary range given: $115,000 - $175,000 USD yearly. So Pay section present. No explicit Benefits listed beyond "Why This Opportunity?" which is more about impact; but we could treat as Benefits? The instruction: include a section ONLY when posting has real, specific content for it. Benefits: we have "Why This Opportunity?" which lists impact, innovation, network, growth. That's more like benefits but not explicit benefits like health insurance. Might still be considered benefits? Safer to not create Benefits section unless explicit benefits like health, 401k, etc. So we skip Benefits. Schedule: not mentioned. So skip. Pay: we have salary range, so include Pay section. We need headings: About the role (maybe intro paragraph). Responsibilities (What You'll Do). Requirements (What You Bring includes experience, education). Qualifications maybe overlapping; but we can combine? The instruction: prefer few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But we have headings list; we can choose to include only those with content. Could do About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. However many sections may be thin. Let's see content: About the role: introductory paragraph before responsibilities. Responsibilities: bullet list. Requirements: experience, education, etc. Qualifications: maybe education? Actually "What You Bring" includes experience, understanding, demonstrated success, existing relationships, familiarity, skills, travel, citizenship, education. That's both requirements and qualifications. Skills: communication, negotiation, etc. Could separate. But to avoid many thin sections, we could combine Requirements and Qualifications into one section titled "Requirements & Qualifications". However instruction says use headings exactly as given (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we must use exactly those headings if we include them; but we should use those headings for sections we include. It didn't forbid combining? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests those are the allowed headings. We can choose subset. So we can include About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. That's six sections. Now we need to preserve all substantive information, not invent or summarize away detail. Use

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

  for prose. We need to extract lists. Let's parse: Intro: "Build the Future of Space & Defense Technology Are you a strategic business development professional with a passion for aerospace, defense, and cutting-edge technology? This is an exciting opportunity to help drive growth in a high-impact electronic components business, connecting innovative solutions with customers shaping the future of space exploration, satellite communications, and defense systems. We're looking for a Manager, Business Development who thrives on building relationships, identifying new opportunities, and turning strategic partnerships into meaningful business growth. In this role, you'll help expand our presence across commercial, government, and international markets while working with high-reliability microelectronic components used in mission-critical space and defense applications. If you're a relationship builder, strategic thinker, and motivated sales professional who enjoys winning new business, this could be your opportunity to make a lasting impact." That's About the role. Responsibilities: bullet list under "What You'll Do". Items: - Drive Business Growth: Identify, qualify, and secure new business opportunities across commercial, government, defense, and space markets. - Build Strategic Partnerships: Leverage your industry connections to establish trusted relationships with key customers, OEMs, prime contractors, and government organizations. - Shape the Future of Space: Develop relationships with spacecraft, launch vehicle, satellite, and subsystem manufacturers. - Lead Market Expansion: Create and execute strategic account plans targeting both established and emerging space exploration and observation programs. - Win New Business: Lead or support capture strategies, proposal development, and negotiations for high-value business opportunities. - Collaborate Across Teams: Partner with engineering, program management, quality, marketing, and finance teams to deliver solutions aligned with customer needs. - Stay Ahead of the Market: Monitor customer acquisition strategies, program funding, contracting processes, and competitive trends to uncover new opportunities. - Represent the Business: Attend industry trade shows, conferences, and customer meetings to showcase the electronic components portfolio and strengthen customer relationships. - Influence Strategy: Share customer insights to help shape marketing campaigns, industry event participation, and long-term business development initiatives. - Track Results: Maintain visibility into sales opportunities, pipeline growth, and business development performance. We need to keep each as

• . The leading bold label can stay inside li. Requirements: from "What You Bring". Items: - 5+ years of experience in business development, sales, or program capture within aerospace, electronics, defense, or related technology industries. - Strong understanding of EEE components, including integrated circuits, diodes, transistors, connectors, and other critical electronic components. - Demonstrated success building customer relationships, managing complex sales cycles, and closing multi-million-dollar opportunities. - Existing relationships within aerospace, defense, space, OEM, prime contractor, or government customer organizations are highly preferred. - Familiarity with DoD procurement processes, government contracting, and international export compliance (ITAR and EAR). - Excellent communication, negotiation, presentation, and relationship-building skills. - Ability to travel domestically and internationally as needed. - Must be a U.S. Citizen and eligible for a U.S. Secret clearance. Education: Bachelor's degree in engineering, business, or a related field. Master's degree or MBA preferred. We could treat education as part of Requirements or Qualifications. Since we have separate Qualifications heading, we could put education there. Qualifications: Bachelor's degree in engineering, business, or a related field. Master's degree or MBA preferred. Skills: maybe we already listed communication etc under Requirements; but we could separate skills: Excellent communication, negotiation, presentation, and relationship-building skills. Ability to travel... maybe also skill. But we already have that in Requirements. To avoid duplication, we could put skills separate: Excellent communication, negotiation, presentation, and relationship-building skills. Ability to travel domestically and internationally as needed. Must be a U.S. Citizen and eligible for a U.S. Secret clearance. However those are also requirements. Might be okay to duplicate? Better to keep them under Requirements and not have Skills section if it's thin. But we need to decide. Given instruction: prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications and Skills into one Requirements section. But we have headings list; we could still include only Requirements and maybe Pay and About the role and Responsibilities. That would be fewer sections. Let's see: Requirements could include experience, education, skills, citizenship, travel. That covers all. Then we don't need Qualifications or Skills separate. Thus sections: About the role, Responsibilities, Requirements, Pay. Check if any other content: "Why This Opportunity?" could be considered Benefits but it's more about impact; we could treat as Benefits? But it's not explicit benefits like health, 401k. Might be considered Benefits but it's more like "Why join". The instruction: include a section ONLY when posting has real, specific content for it. It does have content: "Make an Impact: Contribute to technologies supporting critical space, defense, and aerospace applications. Drive Innovation: Help bring advanced electronic component solutions to new customers and emerging markets. Build Your Network: Engage with industry leaders, strategic customers, and key government and commercial partners. Own Your Growth: Play a meaningful role in expanding business opportunities and shaping long-term market strategy." That's specific content. Could be considered Benefits. However the heading "Benefits" is in list; we could use it. But we already have many sections; adding Benefits would increase sections but still okay. However we want few substantive sections; adding Benefits may be okay if it's substantive. It is substantive (four bullet points). So we could include Benefits section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Now we need to format. Pay: "$115,000 - $175,000 USD yearly". We'll put in

  . Now ensure we don't include boilerplate: remove EEO, drug-free workplace, equal opportunity, etc. Also remove "Additional Requirements" about drug screening etc. That's boilerplate? It's about drug-free workplace; likely considered boilerplate/legal; we should remove. Also remove "The employer is an Equal Opportunity Employer..." etc. Remove "Ready to take your business development career..." etc (application instruction). Also remove location line? Location is metadata; we can fold into short

  or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Location is minor metadata; we can include a short p maybe under About the role? Could add a paragraph with location. But we already have About the role paragraph; we could append location there. However we must preserve ALL substantive information; location is substantive? It's location of job. It's not boilerplate; we should keep it. So we can include location in About the role paragraph. Thus About the role paragraph: include the intro plus location. Let's craft:

  Build the Future of Space & Defense Technology Are you a strategic business development professional with a passion for aerospace, defense, and cutting-edge technology? This is an exciting opportunity to help drive growth in a high-impact electronic components business, connecting innovative solutions with customers shaping the future of space exploration, satellite communications, and defense systems. We're looking for a Manager, Business Development who thrives on building relationships, identifying new opportunities, and turning strategic partnerships into meaningful business growth. In this role, you'll help expand our presence across commercial, government, and international markets while working with high-reliability microelectronic components used in mission-critical space and defense applications. If you're a relationship builder, strategic thinker, and motivated sales professional who enjoys winning new business, this could be your opportunity to make a lasting impact. Location: Cypress, CA (Hybrid).

  Now Responsibilities:

  Responsibilities

  ...
  Requirements: combine experience, education, skills, citizenship, travel. Let's list as
• items. Items: - 5+ years of experience in business development, sales, or program capture within aerospace, electronics, defense, or related technology industries. - Strong understanding of EEE components, including integrated circuits, diodes, transistors, connectors, and other critical electronic components. - Demonstrated success building customer relationships, managing complex sales cycles, and closing multi-million-dollar opportunities. - Existing relationships within aerospace, defense, space, OEM, prime contractor, or government customer organizations are highly preferred. - Familiarity with DoD procurement processes, government contracting, and international export compliance (ITAR and EAR). - Excellent communication, negotiation, presentation, and relationship-building skills. - Ability to travel domestically and internationally as needed. - Must be a U.S. Citizen and eligible for a U.S. Secret clearance. - Bachelor's degree in engineering, business, or a related field. - Master's degree or MBA preferred. We could keep education separate but it's fine. Now Benefits: from "Why This Opportunity?" items: - Make an Impact: Contribute to technologies supporting critical space, defense, and aerospace applications. - Drive Innovation: Help bring advanced electronic component solutions to new customers and emerging markets. - Build Your Network: Engage with industry leaders, strategic customers, and key government and commercial partners. - Own Your Growth: Play a meaningful role in expanding business opportunities and shaping long-term market strategy. Now Pay