Senior Mechanical Design Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Castelion" then "Senior Mechanical Design Engineer" description. We need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Only include sections where there is real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, ITAR? Actually ITAR is a requirement, should be included under Requirements maybe. The posting includes "All employees are granted long-term stock incentives..." and "All employees receive access to comprehensive medical, vision, and dental insurance, and the company offers four weeks of paid time off per year." That's Benefits. Also maybe Pay? No explicit pay/salary mentioned, so we should NOT create Pay or Schedule sections. Also no schedule info. So sections: About the role (maybe from description after title?), Responsibilities, Requirements (including Basic Qualifications and ITAR), Skills? The posting includes Technical Skills etc. Could combine into Requirements or Skills. We need to decide: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple. We need to include only those with real content. Let's extract: About Castelion: description of company mission. That could be "About the role"? Actually "About Castelion" is company overview. Could be placed under "About the role" or maybe we can have a section "About Castelion". But the allowed headings list does not include "About Castelion". However we can still use "About the role" to contain that description? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use those for section headings. Likely we should stick to those headings. So we can have About the role (includes company overview and role description). Responsibilities (list). Requirements (education, experience, ITAR). Qualifications maybe separate? But we have Basic Qualifications already. Could treat Qualifications as same as Requirements? Might be redundant. Better to have Requirements and Qualifications separate if content distinct. The posting has "Basic Qualifications" with subpoints: Educational Background, Technical Skills, Flight-Ready Hardware, Full-Cycle Development Ownership, Leadership Qualities. Those could go under Requirements or Qualifications. Since we have both headings allowed, we could split: Requirements: maybe the ITAR and citizenship requirement? Qualifications: education, experience, skills. But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one "Requirements" section covering education, experience, skills, ITAR. Then "Responsibilities". Then "Benefits". Possibly "Skills" separate? But we already covered skills in Requirements. Could also have a "Skills" section for technical skills list. However to avoid thin sections, we can include Skills as part of Requirements. Let's decide: Sections: About the role, Responsibilities, Requirements, Benefits. Now we need to extract content. About the role: Should include company overview and role description. The posting starts: "About Castelion Castelion is bringing a new approach to defense development and production: one that focuses on short, iterative design cycles, rapid testing in development, and modern commercial manufacturing strategies for production at scale. Were designing, building, and testing next generation long range strike weapons systems to give America and its Allies a definitive edge and deter future conflicts. Senior Mechanical Design Engineer Castelion is seeking a high output Senior Mechanical Design Engineer with a full stack, Responsible Engineer mindset and experience shipping flight hardware. This person will be responsible for critical flight structures and mechanism design and build efforts for Castelion's hypersonic vehicles. The Senior Mechanical Design Engineer will work closely with a fast-moving team of peers and engineering leadership to ensure mission-critical hardware is delivered on time and meets demanding technical performance. A successful candidate will have significant experience delivering high-performance, mass-constrained hardware in a rapid development environment." We need to preserve all substantive information, not invent or summarize away detail. So we need to keep that text essentially. We'll put it in

tags. Responsibilities: The posting has a "Responsibilities" heading then bullet points: "Design and Deliver Mission-Critical Hardware: Lead the design, build, and integration of key flight vehicle components such as composite tanks, separation mechanisms, actuators, and control surfaces. Own your systems from concept to flight. Apply fundamentals in statics, dynamics, and modal analysis to justify designs and prove them in test and flight. Drive High-Cadence Design Iteration: Support iterative prototyping cycles every four weeks for key subsystems. Engage in cross-functional design reviews, integrate test feedback rapidly, and evolve hardware through fast-paced learning loops. Build and Maintain Engineering Rigor: Contribute to the development of engineering best practices at Castelion, including CAD standards, documentation practices, and hardware management protocols. Write build documentation and collaborate hands-on with technicians during integration and assembly." We need to format as

• for each duty. The bullet points are separated by bold headings? We can treat each paragraph as a list item. So we will have three list items. Requirements: Combine education, experience, technical skills, flight-ready hardware, full-cycle development ownership, leadership qualities, ITAR requirements. Also mention "Bachelors degree in Mechanical Engineering with 5+ years of professional ME experience." etc. We'll need to preserve all details. We'll need to format as
  • for each requirement? Could be paragraphs. The instruction: Use
    • for any list of duties/requirements/benefits. So if we have multiple items, we should list them. For requirements we have several categories; we can make each bullet a requirement. Let's extract each requirement bullet: - Educational Background: Bachelors degree in Mechanical Engineering with 5+ years of professional ME experience. - Technical Skills: This role requires broad mechanical domain knowledge, including detailed CAD design of complex parts, tolerance stack up analysis, thermal analysis, structural analysis, and deign-to-cost. (Note typo "deign-to-cost" but we keep as is.) - Flight-Ready Hardware: Experience designing elegant, manufacturable components optimized for weight, cost, and simplicity; familiarity with coatings, finishes, and composite structures - Full-Cycle Development Ownership: Experience bringing hardware designs from initial concept to implementation, production, and successful operations. Ability to maximize speed and value from vendors for company goals during vendor visits or joint development efforts. - Leadership Qualities: Bias to Action and Creative Problem Solving. Desire and experience questioning assumptions in ways that lead to break through ideas that are ultimately implemented. Successfully bring in applicable processes/concepts/materials from other industries to achieve efficiency gains. Ability to personally resolve minor issues in development without requiring significant support. High Commitment, High Initiative. A successful candidate will have a genuine passion for Castelion's mission and consistently look for ways to contribute to the company's technical goals and prevent hardware blockers. Ability to work in a fast paced, autonomously driven, and demanding atmosphere. Strong sense of accountability and integrity. Clear Communicator. Proactively communicates blockers. Trusted in previous roles to be voice of company with regulators, suppliers, gate keepers and customers. Capable of tactfully managing relationships with stakeholders to achieve company-desired outcomes without compromising relationships. Emails, IMs and verbal interactions are logical, drive clarity, and detailed enough to eliminate ambiguity. - ITAR Requirements: To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C.1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State. We could also include "Employment with Castelion is governed on the basis of competence and qualifications and will not be influenced in any manner by race, color, religion, gender, national origin/ethnicity, veteran status, disability status, age, sexual orientation, gender identity, marital status, mental or physical disability or any other legally protected status." That's EEO boilerplate; we should remove it per instruction: remove EEO/equal-opportunity boilerplate. So we omit that. Benefits: "All employees are granted long-term stock incentives as part of their employment at Castelion. All employees receive access to comprehensive medical, vision, and dental insurance, and the company offers four weeks of paid time off per year." We need to put as list items maybe. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Benefits

      • ...
      ...
      Make sure to preserve all substantive info. No extra sections like Pay or Schedule. Check for any duplicated lines: we should not repeat. Now craft the HTML. We need to be careful with apostrophes and quotes inside HTML; we can just keep them as is; they are fine inside text nodes. Let's write the About the role paragraph: "About Castelion Castelion is bringing a new approach to defense development and production: one that focuses on short, iterative design cycles, rapid testing in development, and modern commercial manufacturing strategies for production at scale. Were designing, building, and testing next generation long range strike weapons systems to give America and its Allies a definitive edge and deter future conflicts. Senior Mechanical Design Engineer Castelion is seeking a high output Senior Mechanical Design Engineer with a full stack, Responsible Engineer mindset and experience shipping flight hardware. This person will be responsible for critical flight structures and mechanism design and build efforts for Castelion's hypersonic vehicles. The Senior Mechanical Design Engineer will work closely with a fast-moving team of peers and engineering leadership to ensure mission-critical hardware is delivered on time and meets demanding technical performance. A successful candidate will have significant experience delivering high-performance, mass-constrained hardware in a rapid development environment." Note there is a missing apostrophe in "Were". We keep as is. Now Responsibilities list items: 1. "Design and Deliver Mission-Critical Hardware: Lead the design, build, and integration of key flight vehicle components such as composite tanks, separation mechanisms, actuators, and control surfaces. Own your systems from concept to flight. Apply fundamentals in statics, dynamics, and modal analysis to justify designs and prove them in test and flight." 2. "Drive High-Cadence Design Iteration: Support iterative prototyping cycles every four weeks for key subsystems. Engage in cross-functional design reviews, integrate test feedback rapidly, and evolve hardware through fast-paced learning loops." 3. "Build and Maintain Engineering Rigor: Contribute to the development of engineering best practices at Castelion, including CAD standards, documentation practices, and hardware management protocols. Write build documentation and collaborate hands-on with technicians during integration and assembly." Now Requirements list items: - Educational Background: Bachelors degree in Mechanical Engineering with 5+ years of professional ME experience. - Technical Skills: This role requires broad mechanical domain knowledge, including detailed CAD design of complex parts, tolerance stack up analysis, thermal analysis, structural analysis, and deign-to-cost. - Flight-Ready Hardware: Experience designing elegant, manufacturable components optimized for weight, cost, and simplicity; familiarity with coatings, finishes, and composite structures - Full-Cycle Development Ownership: Experience bringing hardware designs from initial concept to implementation, production, and successful operations. Ability to maximize speed and value from vendors for company goals during vendor visits or joint development efforts. - Leadership Qualities: Bias to Action and Creative Problem Solving. Desire and experience questioning assumptions in ways that lead to break through ideas that are ultimately implemented. Successfully bring in applicable processes/concepts/material