Aerospace Engineer II

We need to produce HTML fragment with sections: About the role, Responsibilities? The posting includes "About The Role" and "About You". There's also "Minimum Qualifications", "Preferred Qualifications". Also "Compensation: Pay Range". Also benefits: "We also offer a generous benefit package, including medical, dental, and vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, and more." So we can have Benefits section. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, application deadline? Actually "Application Deadline: This role will remain posted until a qualified pool of candidates is identified." That's application instruction? It's not exactly instruction but could be considered meta. The instruction says remove application instructions. So we should drop that line. Also "Please note: Sierra Space does not accept unsolicited resumes..." that's also application instruction, drop. Also "Sierra Space Corporation is an equal opportunity employer..." drop. Also "If you need special assistance..." drop. Also "Elevate Your Career At Sierra Space..." maybe part of benefits? It's more about culture; could be part of Benefits or maybe we can include as a paragraph under Benefits? It's not exactly benefits but could be considered "Culture". However we only have headings for specified list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We have About The Role (section heading). We can put that as

About the role

with prose. Responsibilities: we can extract duties from About The Role description: design, analysis, testing, vehicle-level analysis, system design, applying aerospace principles, contributing expertise, performing vehicle-level analysis, conducting first-order analyses and tests, develop and document technical data and reports, providing clear verbal and written communication, collaborating with cross-functional teams, participating in technical reviews, team meetings, discussions, providing insights, contributing to engineering solutions. We'll put those as

• . Requirements: maybe Minimum Qualifications? Or Requirements could be same as Minimum Qualifications. We'll use Requirements heading for minimum qualifications. Qualifications: maybe Preferred Qualifications? Or we could have Skills heading for preferred qualifications? The list includes Skills, Benefits, Pay, Schedule. We have Pay (compensation). Benefits we have. Schedule not mentioned, so we should not create Schedule section. Skills maybe we can list some skills from preferred qualifications: programming languages, simulation, modeling, software development lifecycle, object-oriented design patterns, Linux environment, organizational skills, learning ability, teamwork, communication. Could put under Skills. Qualifications could be Preferred Qualifications? But we already have Requirements for minimum. Could also have Qualifications for preferred. However instructions: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include Qualifications heading for preferred qualifications. Skills maybe we can extract some specific skills like programming languages etc. But we might combine. We need to avoid filler like "commensurate with experience". Not present. We must preserve all substantive information. So include all details from Minimum Qualifications, Preferred Qualifications, Compensation, Benefits. We must not invent or summarize away detail. So we need to keep exact phrasing? We can paraphrase but must preserve info. Safer to keep sentences as is. Let's extract sections: About the role: The paragraph(s) under "About The Role". There's some repetition. We'll combine into a concise paragraph but must preserve all substantive info. The text: "As an Aerospace Engineer II at Sierra Space, you will draw on your foundational knowledge and experience to contribute to the design, analysis, and testing of aerospace systems and components. With a strong understanding of Aerodynamics, Aerothermal or Astrodynamics, you will engage in vehicle-level analysis and system design. Your role will involve applying aerospace principles and concepts to support various engineering projects while collaborating within a team environment. In this role, you will apply a strong understanding of aerospace engineering principles to assist in the design, analysis, and testing of aerospace systems and components. You will contribute expertise in specific areas such as aerodynamics, aerothermal, or astrodynamics, performing vehicle-level analysis and system design tasks while leveraging your fundamental understanding of these areas. Conducting first-order analyses and tests, you will apply standard aerospace principles, theories, and concepts to support engineering projects. Additionally, you will develop and document technical data and reports to ensure traceability and facilitate project progress. Providing clear verbal and written communication of technical concepts and information, you will collaborate with cross-functional teams to achieve project goals and contribute to problem-solving efforts. You will actively participate in technical reviews, team meetings, and discussions, providing insights and contributing to engineering solutions to address challenges and drive success." We can keep that as a paragraph. Responsibilities: Could be a list derived from that. But we already have About the role paragraph; maybe we should not duplicate. However instructions: "Use

  • for any list of duties/requirements/benefits". So if we have duties, we should list them. The About the role paragraph already contains duties; we could turn them into list. But we also need About the role heading with prose? Could we have both? The instruction says use

    for section headings,

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

      for prose. So we can have About the role heading with prose summarizing role, and then Responsibilities heading with list of duties. That seems okay. Let's extract duties list: - Contribute to the design, analysis, and testing of aerospace systems and components. - Engage in vehicle-level analysis and system design (with strong understanding of Aerodynamics, Aerothermal or Astrodynamics). - Apply aerospace principles and concepts to support various engineering projects while collaborating within a team environment. - Contribute expertise in specific areas such as aerodynamics, aerothermal, or astrodynamics, performing vehicle-level analysis and system design tasks. - Conduct first-order analyses and tests, applying standard aerospace principles, theories, and concepts. - Develop and document technical data and reports to ensure traceability and facilitate project progress. - Provide clear verbal and written communication of technical concepts and information. - Collaborate with cross-functional teams to achieve project goals and contribute to problem-solving efforts. - Actively participate in technical reviews, team meetings, and discussions, providing insights and contributing to engineering solutions to address challenges and drive success. That covers. Requirements: Minimum Qualifications bullet list: - Requires bachelor's degree in a related field (or equivalent work experience in lieu of degree). - Typically, 2+ years of related experience. - Strong understanding of one of the following areas: Aerodynamics, Astrodynamics, Thermal Analysis, Dynamics and Vibration, GN&C, Mass Properties. - Familiar with vehicle-level analysis and system design. - Application of aerospace principles, standards, theories, first-order analysis, and concepts. We'll put as

      • . Qualifications: Preferred Qualifications list: - Experience developing and testing multibody, 6-DOF simulations for aircraft and spacecraft trajectory analysis. - Hands on experience with programming languages such as Python, C++, MATLAB, or Fortran for simulation and analysis tasks. - Knowledge and experience in modeling the following areas: flight surface control actuators, landing gear systems, aerodynamics, propulsion systems, GNC flight software, and navigation sensors. - Strong knowledge of software development methodologies, tools, and best practices. - Thorough understanding and experience spanning the full software development lifecycle. - Familiarity with common object-oriented software design patterns. - Experience working in a Linux-based development environment. - Strong organizational skills and the ability to manage multiple tasks and priorities effectively. - Demonstrated ability to learn new concepts quickly and apply them in practical settings. - Enthusiasm for continuous learning and professional development in aerospace engineering. - Excellent teamwork and collaboration skills to work effectively within cross-functional teams. - Strong communication skills to clearly convey technical information to a diverse audience. We'll put as
        • . Skills: Could be a subset like programming languages, modeling, software development, etc. But we already have Qualifications covering many. Perhaps we can put Skills heading for technical skills like programming languages, modeling, software development, Linux, etc. However we risk duplication. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills? But we need to follow headings list; we can include Skills if we have content. Let's see if we can extract specific skills: programming languages (Python, C++, MATLAB, Fortran), modeling areas, software development methodologies, full lifecycle, object-oriented design patterns, Linux environment, organizational skills, learning ability, teamwork, communication. Those are skills. So we can have Skills section with list. But then Qualifications could be just the minimum qualifications? Actually we already used Requirements for minimum qualifications. Qualifications could be for preferred qualifications. But then Skills would be redundant. Perhaps better: Use Requirements for minimum qualifications, Qualifications for preferred qualifications, and skip Skills. But we need to decide. The instruction says "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to use all. We should include only those with real content. So we can have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six sections. Skills we could omit if we feel Qualifications covers it. But Qualifications heading is for preferred qualifications; we have content. So we will include Qualifications. Thus sections: - About the role (prose) - Responsibilities (list) - Requirements (list) (minimum qualifications) - Qualifications (list) (preferred qualifications) - Benefits (list) (medical, dental, vision, 401k match, life insurance, 3 weeks PTO, etc.) - Pay (list or prose) (Pay Range: $94,203.00 - $129,549.75, plus note about case-by-case determination) We should not include Schedule. Now we need to ensure we preserve all substantive information. Also include the note about compensation: "Your actual base compensation will be determined on a case-by-case basis and may vary based on job-related knowledge and skills, education, experience, internal equity and market competitiveness." We'll keep that as prose under Pay. Benefits: The text: "We also offer a generous benefit package, including medical, dental, and vision plans, 401(k) with 150% match up to 6%, life insurance, 3 weeks paid time off, and more." We'll put as list items. Also there is earlier: "Elevate Your Career At Sierra Space, we are committed to your personal and professional development. We empower you to make profound and meaningful contributions and foster a vibrant culture of collaboration, where teamwork ignites breakthrough innovations." That's more about culture; could be part of Benefits? Not exactly benefit. Could be omitted? It's substantive but not a benefit. However we have no section for culture. Could we put it under About the role? Might be stray. The instruction says preserve ALL substantive information. So we need to include that somewhere. Perhaps we can add a short paragraph under Benefits or under About the role? But it's not about role. Could we add a section "Culture"? Not in allowed headings. But we could incorporate into Benefits as a bullet? Might be okay but not exactly benefit. However we could add a separate section "About the company"? Not allowed. The instruction says we should only use those headings; but we could also include a

          outside headings? The instruction: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

            for prose." It doesn't forbid other headings, but says use those for section headings. It says "include a section ONLY when the posting