Design Engineer I/II, Interiors and Structures

We need to output HTML fragment with sections: About the role? Actually we have sections: WHO WE ARE, THE ROLE, WHAT YOU'LL DO, WHAT YOU BRING, WHY ALTITUDE, CONDITIONS OF EMPLOYMENT. We need to use

for section headings. Use

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

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — none present. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Altitude Aerospace is an equal opportunity employer." That's EEO boilerplate, remove. We need to preserve all substantive information. Need to include sections only when posting has real, specific content. So we need sections: About the role? Actually we have "WHO WE ARE" (company description). Could map to "About the company"? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can also use other headings? 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, but we should likely stick to those categories. However we have content that doesn't fit exactly those categories: "WHO WE ARE" could be "About the role"? Not exactly. Could be "About the company" but not listed. Perhaps we can treat "WHO WE ARE" as "About the role"? Might be okay. Or we could create a section "About the company" but not in list; but instruction says use those headings for section headings (e.g...). It may be okay to use other headings if they match content? Safer to map to given headings: "About the role" could encompass WHO WE ARE and THE ROLE? But we need to preserve details. Maybe we can have multiple sections: About the role (includes WHO WE ARE and THE ROLE), Responsibilities (WHAT YOU'LL DO), Requirements (WHAT YOU BRING - Required), Qualifications (WHAT YOU BRING - Preferred), Skills (maybe combine), Benefits (WHY ALTITUDE includes benefits? Actually WHY ALTITUDE includes Real Programs, Mentorship, Team Culture, Room to Grow - not benefits. Benefits are listed in WHO WE ARE: "We offer 100% employer-paid medical, dental, and vision insurance, SIMPLE IRA retirement plan, paid vacation and PTO, and 8 paid holidays." That's benefits. Also Pay is given: Salary: $83,000 to $104,000 per year, based on level. Schedule: Full-time, 6+ months (maybe schedule? Actually schedule is full-time, duration 6+ months). So we can create Benefits, Pay, Schedule sections. We must not create sections with filler like "commensurate with experience". We have actual content. Thus sections: - About the role (maybe combine WHO WE ARE and THE ROLE). Could split: About the company and About the role? But we have limited headings. Could do "About the role" for THE ROLE, and maybe "About the company" not allowed. Could we omit WHO WE ARE? It's substantive info about company; we should preserve. Could we put it under About the role? Might be okay. Better: Use headings: About the role (contains WHO WE ARE and THE ROLE). Responsibilities (WHAT YOU'LL DO). Requirements (WHAT YOU BRING - Required). Qualifications (WHAT YOU BRING - Preferred). Benefits (from WHO WE ARE). Pay (Salary). Schedule (Full-time, 6+ months). Also maybe Skills? Could combine with Requirements/Qualifications. We need to use

  • for any list of duties/requirements/benefits. So for responsibilities list, we have bullet-like sentences: "Model & Draft", "Build 3D models...", "Turn direction...", "Manage files...", "Support & Coordinate", etc. We can turn each into list items. For requirements list: Required items: Bachelor's degree..., 1 to 5 years..., Solid 3D modeling..., Comfortable..., Must be US citizen..., Able to work onsite... For qualifications list (Preferred): Autodesk Inventor..., Aircraft interiors..., VIP or business jet completions background. Benefits list: 100% employer-paid medical, dental, and vision insurance, SIMPLE IRA retirement plan, paid vacation and PTO, 8 paid holidays. Pay: just a sentence maybe

    . Schedule: Full-time, 6+ months. We must not include duplicated lines. Ensure we don't include boilerplate like "Altitude Aerospace is an equal opportunity employer." Remove. Also remove "CONDITIONS OF EMPLOYMENT" lines? Those are substantive: Onsite role in Bothell, WA area; Background check and drug screen required; ITAR eligibility required: U.S. citizen or permanent resident, work performed within the United States. Some of that overlaps with requirements (US citizen). But we should keep them maybe under Requirements or a separate section? Could incorporate into Requirements. But we already have US citizen requirement. Could add background check and drug screen as requirement. Also onsite location is already in location line at top. Could keep as part of schedule? Might be redundant. But we need to preserve all substantive information. So we need to include background check and drug screen, and ITAR eligibility (which is same as US citizen). We'll include under Requirements. Thus Requirements list will include: Bachelor's degree..., 1 to 5 years..., Solid 3D modeling..., Comfortable..., Must be US citizen or permanent resident..., Able to work onsite in Bothell, WA area..., Background check and drug screen required..., ITAR eligibility required: U.S. citizen or permanent resident, work performed within the United States. But note US citizen appears twice; we can combine. We'll avoid duplication. Now produce HTML fragment. Structure:

    About the role

    Altitude Aerospace delivers engineering and certification solutions for commercial and VIP aircraft programs worldwide. With FAA DER, EASA DOA, and TCCA DAO approvals, we support customers from concept through certification and in-service. Our 150+ person team across the US, Canada, and France works on programs for major OEMs and completion centers globally.

    A strong opportunity for early to mid career engineers to build hands on aircraft design experience. You will create the models and drawings behind interior and structural components on custom VIP aircraft programs, working from the direction of experienced senior engineers who lead development and design. This role covers interiors and structures (not monuments).

    Then Responsibilities:

    Responsibilities

    • Model & Draft: Build 3D models and 2D drawings for aircraft interior and structural components in Autodesk Inventor, with some AutoCAD.
    • Turn direction from senior design engineers into clean, accurate drawings.
    • Manage files in Autodesk Vault and track tasks in Autodesk PLM 360 (now Autodesk Fusion Manage).
    • Support & Coordinate: Incorporate feedback from senior design engineers.
    • Coordinate with other disciplines as designs integrate.
    • Ask questions freely. This team would rather you ask than guess.
    • Impact: Only a handful of companies in the world complete VIP interiors on wide body aircraft. Every program is custom built, so you won't get stuck doing the same thing over and over.
    Requirements:

    Requirements

    • Bachelor's degree in Mechanical or Aerospace Engineering, or equivalent hands-on modeling and drafting experience.
    • 1 to 5 years of design, modeling, or drafting experience.
    • Solid 3D modeling and drawing skills in a CAD tool; Inventor experience is a plus but not required.
    • Comfortable working from senior engineer direction.
    • Must be a U.S. citizen or permanent resident and able to perform this work within the United States.
    • Able to work onsite in the Bothell, WA area.
    • Background check and drug screen required.
    • ITAR eligibility required: U.S. citizen or permanent resident, work performed within the United States.
    Qualifications (Preferred):

    Qualifications

    • Autodesk Inventor, Vault, or PLM 360 (Fusion Manage) experience.
    • Aircraft interiors or structures experience.
    • VIP or business jet completions background.
    Benefits:

    Benefits

    • 100% employer-paid medical, dental, and vision insurance.
    • SIMPLE IRA retirement plan.
    • Paid vacation and PTO.
    • 8 paid holidays.
    Pay:

    Pay

    Salary: $83,000 to $104,000 per year, based on level.

    Schedule:

    Schedule

    Full-time, 6+ months.

    We should not include any extra sections like Skills. Ensure no empty headings. Check for any boilerplate removed: We removed equal opportunity line. Also removed "CONDITIONS OF EMPLOYMENT" heading; we incorporated its content into Requirements. Check duplication: We have US citizen requirement twice? We have one line "Must be a U.S. citizen or permanent resident and able to perform this work within the United States." and later "ITAR eligibility required: U.S. citizen or permanent resident, work performed within the United States." That's somewhat redundant but both are substantive; we could combine but it's okay to keep both as they are distinct statements. However we might consider merging to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original; but we should not invent. The original had both statements: under WHAT YOU BRING Required: "Must be a U.S. citizen or permanent resident and able to perform this work within the United States." Under CONDITIONS OF EMPLOYMENT: "ITAR eligibility required: U.S. citizen or permanent resident, work performed within the United States." So we keep both. Now ensure we didn't miss any substantive info: Location line: "Location: On-Site, Bothell, WA | Salary: $83,000 to $104,000 per year, based on level | Employment: Full-time, 6+ months". We captured location in requirement (onsite Bothell), salary in Pay, employment in Schedule. Good. We also have "WHO WE ARE" includes "We offer 100% employer-paid medical, dental, and vision insurance, SIMPLE IRA retirement plan, paid vacation and PTO, and 8 paid holidays." That's benefits. We also have "WHY ALTITUDE" includes Real Programs, Mentorship, Team Culture, Room to Grow. That's not benefits but could be considered "About the role" or maybe we could add a section "Why Altitude". But not in allowed headings. Could we incorporate into About the role? Already we have About the role with WHO WE ARE and THE ROLE. Could add the WHY ALTITUDE content there as well. It's substantive; we should preserve. So we should add that content to About the role section. Thus About the role section should include WHO WE ARE, THE ROLE, and WHY ALTITUDE. Let's craft About the role paragraph(s): Paragraph 1: WHO WE ARE description. Paragraph 2: THE ROLE description. Paragraph 3