Senior Enterprise Account Executive - Space Technology (Texas)

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines and application instructions. We need to parse the posting. Let's extract sections: - About MISUMI Americas: description of company. Could be "About the role"? Actually "About MISUMI Americas" is company overview. Could be placed under "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content matches. We have "About MISUMI Americas" which is about company, not role. Could map to "About the role"? Might be okay to use "About the role" heading and put company description there? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid using About the role for company overview. Usually "About the role" is about the role itself. But we have "Impact In This Role" which describes role impact. Could be "About the role". Let's treat "Impact In This Role" as about the role. We have sections: - Impact In This Role (description of role) - What You’ll Be Doing (list of duties) - Desired Traits (list of qualifications/skills/experience) - Physical Demands (maybe not needed? It's boilerplate? It's about physical demands; could be considered part of Requirements? Might be considered boilerplate but it's specific. However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Physical demands is not exactly that; it's job requirement. Might keep as part of Requirements or Qualifications. But we can include a short

under Requirements. - Perks And Benefits (list) - Salary: $100,000 base per year, $100,000 variable per year (uncapped) -> Pay section. - Also there is "Interested in learning more? We look forward to hearing from you soon..." that's application instruction; remove. - Also "We’re actively seeking teammates who: ..." that's culture; could be part of Benefits? Not exactly. Might be considered part of Qualifications? It's about desired attributes; could be part of Skills/Traits. But we already have Desired Traits. Could incorporate. - Also "We encourage applications from members of underrepresented groups..." that's EEO boilerplate; remove. Thus we need sections: About the role (maybe using Impact In This Role), Responsibilities (What You’ll Be Doing), Requirements/Qualifications/Skills (Desired Traits plus Physical Demands), Benefits (Perks And Benefits), Pay (Salary). Possibly Schedule not present; omit. We must not create sections with filler like "commensurate with experience". We have concrete content. We need to 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 extract bullet points from "What You’ll Be Doing" and "Desired Traits" and "Perks And Benefits". Also maybe include "Physical Demands" as a paragraph. Let's extract. First, "Impact In This Role" paragraph: "As a Sr. Enterprise Account Executive – Space Technology, you'll work with some of the leading satellite communications and aerospace companies, helping them source precision manufactured components as they move from prototype through low-volume and bridge production. You'll dig into each customer's business goals - financial KPIs, engineering priorities, org structure, in-house manufacturing capabilities and supply chain resiliency needs, and their internal decision-making structure, so you can build relationships with the right people across engineering, procurement, and operations. You'll also learn their product roadmaps, requirements, and priorities for bringing products to market, along with their existing supplier relationships and qualification processes. With that knowledge, you'll configure the right solution to speed up their time to market, identifying both prototyping opportunities and production-class manufacturing programs that let customers launch products faster than they thought possible. Your leadership will be key to coordinating the full MISUMI Americas team supporting you - applications engineering, sourcing, manufacturing operations, quality, and finance. You'll deliver sales presentations and lead on-site meetings - sales meetings, quarterly business reviews, and technical reviews - to build confidence, deepen relationships, and grow customer lifetime value." We'll put that under

  About the role

  as prose

  . Next, "What You’ll Be Doing" bullet list: - Develop and execute strategic account plans for large enterprise targets - Own a defined portfolio of high-value accounts and build account strategies that map business units, engineering teams, procurement groups, manufacturing decision-makers, executive sponsors, current supplier relationships, program timelines, and expansion paths. Top performers will know where the account is going before the customer issues an RFQ. - Create and progress complex, multi-stakeholder opportunities - Identify manufacturing pain points across prototype, new product introduction, low-volume production, bridge production, and supply chain resiliency use cases. - Navigate long sales cycles involving engineering validation, supplier qualification, procurement scrutiny, legal review, quality requirements, and executive approval. - Translate technical manufacturing challenges into business value - Work with customers to understand requirements related to CNC machining, injection molding, sheet metal fabrication, additive manufacturing, tolerances, materials, inspection, DFM, lead times, cost drivers, and production risk. - Convert those requirements into clear commercial value tied to speed-to-market, engineering throughput, supply continuity, working capital efficiency, and total cost of ownership. - Lead cross-functional deal orchestration - Partner closely with applications engineering, sourcing, manufacturing operations, customer success, quality, finance, and leadership to design solutions that can be sold, delivered, scaled, and renewed. - The best SAEs will not simply “throw opportunities over the wall”; they will coordinate internal resources with discipline and urgency. - Build executive-level relationships and account expansion pathways - Establish credibility beyond the initial buying group by developing relationships with VP-level and C-level leaders in engineering, supply chain, operations, product development, and procurement. - Use early wins to expand across divisions, product lines, geographies, and manufacturing categories. - Own commercial strategy, negotiation, and closing - Drive pricing strategy, business cases, proposals, MSAs, supplier onboarding, enterprise agreements, and complex negotiations. - Balance customer advocacy with MISUMI Americas commercial goals, ensuring that deals are strategically valuable, operationally executable, and positioned for long-term growth. - Maintain rigorous pipeline discipline and forecast accuracy - Build a sufficient, qualified pipeline, manage opportunity stages with precision, identify risks early, and maintain a reliable forecast. - Excellence in this role requires both strategic creativity and operating discipline. We need to preserve all detail. Could flatten into a simple list of items; but we have sub-bullets. The instruction: use

  • for any list of duties/requirements/benefits. It didn't forbid nested lists? Usually we can nest
    • . We'll keep hierarchy. But we need to ensure we don't lose any detail. We'll produce a nested list. Next, "Desired Traits" list: - 8+ years of B2B sales experience, with at least 5 years selling complex technical solutions into enterprise or strategic accounts - Background in space technology/satellite industry strongly preferred - Demonstrated success closing and expanding six and seven-figure annual contract value opportunities, with direct involvement in multi-million-dollar account growth - Proven record of consistently meeting or exceeding quota in a long-cycle, consultative sales environment - Experience selling into organizations where buying decisions involve multiple functions, including engineering, procurement, supply chain, operations, finance, legal, and executive stakeholders - Working knowledge of technical manufacturing, engineering services, industrial supply chains, product development, or related technical domains - Ability to understand and discuss manufacturing requirements such as tolerances, materials, production processes, lead times, quality standards, DFM considerations, inspection needs, and supplier qualification - Strong command of enterprise sales methodology, account planning, pipeline management, deal qualification, mutual action plans, and executive-level selling - Comfortable owning a territory or named-account book with high expectations for pipeline creation, deal strategy, forecast integrity, and expansion - Experience selling manufacturing, supply chain, engineering, product development, industrial technology, or production services to enterprise customers - Familiarity with CNC machining, injection molding, sheet metal, urethane casting, additive manufacturing, or precision manufacturing workflows - Experience in displacing incumbent suppliers or introducing a new operating model into conservative manufacturing organizations - Background using MEDDICC, Challenger, Command of the Message, Force Management, or similar enterprise sales frameworks - Experience managing strategic accounts that include both centralized procurement and decentralized engineering demand - Comfort operating in a fast-moving, technology-enabled company where sales, operations, product, and supply teams must work tightly together - Spend over 50% of your time out of the office in front of customers - BS in Engineering or a technical degree preferred - Fluency in Spanish preferred, not required We'll put under

      Requirements

      maybe also Qualifications/Skills. The instruction list includes Requirements, Qualifications, Skills. We could combine into one section "Requirements". Or we could split: Requirements (experience), Qualifications (education), Skills (technical). But they said prefer a few substantive sections over many thin ones. So we can have one Requirements section containing all desired traits. We also have Physical Demands paragraph: "Standard office and home-office work environment with extensive computer, phone, and video-conference use. Ability to travel by air and drive within assigned territory, including navigating customer plant floors and manufacturing environments during field visits." plus earlier sentence about reasonable accommodations. We'll include as a paragraph under Requirements maybe after list. But we need to ensure we don't include boilerplate like "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's generic but still part of physical demands; it's not EEO but it's about accommodations. Might be considered boilerplate but it's standard. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not exactly those; it's about accommodations. Might keep. We'll include a short

      for Physical Demands. Next, "Perks And Benefits" list: - Competitive medical, dental, and vision insurance - 401K plan - Parental leave programs - Paid volunteer days - And much, much more! The last is vague; but it's part of benefits. We'll keep as list item. We'll put under

      Benefits

      . Next, Pay: "Salary: $100,000 base per year, $100,000 variable per year (uncapped)". We'll put under

      Pay

      as

      . Schedule: not present, omit. We also have company description "About MISUMI Americas". Could be included under About the role? Might be better to have a separate section "About the company" but not in allowed headings. Could fold into About the role paragraph? Might be okay to include as part of About the role? But the role description already covers impact. The company description is separate. Could we add a section "About the role" and include both company overview and role impact? Might be mixing. However we need to preserve all substantive info; we can't drop company description. We could add a section "About the role" and put company