Ground Autonomy Control Engineer III - New Glenn

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: Application Close Date line, EEO, etc. Also remove navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to extract content. Let's parse the posting: First paragraph: "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." That's boilerplate, remove. Next: "At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. We’re working to develop reusable, safe, and low-cost space vehicles and systems within a culture of safety, collaboration, and inclusion. Join our team of problem solvers as we add new chapters to the history of spaceflight!" This is about the company/mission; could be part of "About the role"? Actually it's about the company. Might be considered "About the role"? Usually "About the role" includes description of role and mission. We'll include that as part of About the role. Next: "This role supports the development and operations of New Glenn, a single-configuration, heavy-lift orbital launch vehicle capable of routinely carrying people and payloads to low-Earth orbit, geostationary transfer orbit, cislunar, and beyond. Its first stage is fully reusable, and the vehicle was designed from the beginning to be human-capable." That's role description. Next: "As part of a small, passionate, and accomplished team of experts, you will design, develop, verify, and commission software solutions for the ground control systems supporting New Glenn, Blue Origin's heavy-lift orbital launch vehicle." That's responsibilities. Next: "You will be designing Ground Control applications using Model Based development and verification techniques for the launch controls facilities." Responsibilities. Next: "In this role, you will help implement the overall strategy for autonomous ground control systems — a key enabler for increased launch cadence and efficient operations." Responsibilities. Next: "You will take ownership of complex technical challenges involved with configuration management, verification, commissioning and in-field troubleshooting." Responsibilities. Next: "The role hinges on using "physics-based" controls systems modeling to develop robust controls applications." Responsibilities. Next: "In addition, you will interact with the launch engineering and the operations team to solicit customer feedback and validate that the controls software meets the needs of the real-world operations scenario." Responsibilities. Next: "As a senior engineer, you will be ensuring that the products you are responsible for are ready for deployment for a New Glenn Mission and operationally ready." Responsibilities. Next: "You will actively leverage Large Language Models (LLMs) and Artificial Intelligence (AI) in the development of the autonomous applications." Responsibilities. Next: "We seek someone who will apply their technical expertise and commitment to quality to positively impact safe human spaceflight. Passion for our mission and vision is essential! If you thrive on challenge, want to make history, and enjoy solving the toughest engineering problems in aerospace, we encourage you to apply. Join us in launching the next era of human spaceflight!" This is more about desired traits; could be part of Requirements or Qualifications. Now Minimum Qualifications bullet list: - B.S. in Engineering (Mechanical, Electrical, Chemical, Aerospace, Software, or related field) - 5-8 years of experience in the applicable industry and/or a controls-related role in a non-academic, professional setting - Experience with model-based software design and validation - Experience in tuning and processing P&ID loops and familiarity in reading schematic drawings - Experience working in a configuration managed development environment - Good Knowledge of common programming languages such as C/C++, Python Preferred Qualifications bullet list: - Experience with modeling and simulations - Experience with software integration - Experience with StateFlow, State Machine - Familiarity with DO-178 and/or DO-278 - Familiarity with PLCs or embedded controllers - Experience in Automotive, Aviation or Space industry - Experience with Linux - Experience with GitLab, Confluence, JIRA Then "ITS Base Pay Range For WA applicants is $130,706.00 - $182,987.70 Other Site Ranges May Differ". That's Pay. Then "Culture Statement Don’t meet all desired requirements? Studies have shown that some people are less likely to apply to jobs unless they meet every single desired qualification. At Blue Origin, we are dedicated to building an authentic workplace, so if you’re excited about this role but your past experience doesn’t align perfectly with every desired qualification in the job description, we encourage you to apply anyway. You may be just the right candidate for this or other roles." That's more about encouraging; could be part of About the role or maybe a note but not required. It's not boilerplate? It's a culture statement; we could include as part of About the role or maybe a separate section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This culture statement is specific content, not filler. Could be placed under "About the role" or maybe a separate "Culture" but we only have predefined headings. Could fit under "About the role" or maybe "Qualifications"? It's more about encouraging applicants; could be part of "About the role". We'll incorporate it into About the role paragraph. Next: "Export Control Regulations Applicants for employment at Blue Origin must be a U.S. citizen or national, U.S. permanent resident (i.e. current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum." That's a requirement (citizenship). Should be included under Requirements or Qualifications. It's a specific requirement. Next: "Background Check Required for all positions: Blue’s Standard Background CheckRequired for Certain Job Profiles: Defense Biometric Identification System (DBIDS) background check if at any time the role requires one to be on a military installationRequired for Certain Job Profiles: Drivers who operate Commercial Motor Vehicles with a Gross Vehicle Weight (GVW), Gross Vehicle Weight Rating (GVWR) or combination of power unit and trailer that meets or exceeds 10,001 lbs. and/or transports placardable amounts of hazardous materials by ground in any vehicle on a public road while in commerce, may be subject to additional Federal Motor Carrier Safety Regulations including: Driver Qualification Files, Medical Certification (obtained before onboarding), Road Test, Hours of Service, Drug and Alcohol Testing, vehicle inspection requirements, CDL requirements (if applicable) and hazardous materials transportation/shipping training.Required for certain Job Profiles: Ability to obtain and maintain Merchant Mariner Credential, which includes pre-employment and random drug testing as well as DOT physical" This is background check info; could be considered Requirements (maybe under Requirements). It's specific. Next: "Benefits Benefits include: Medical, dental, vision, basic and supplemental life insurance, paid parental leave, short and long-term disability, 401(k) with a company match of up to 5%, and an Education Support Program.Stock Options for all regular employees (working at least 20 hours/week)Paid Time Off: Up to four (4) weeks per year based on weekly scheduled hours, and up to 14 company-paid holidays.Dependent on role type and job level, employees may be eligible for benefits and bonuses based on the company's intent to reward individual contributions and enable them to share in the company's results, or other factors at the company's sole discretion. Bonus amounts and eligibility are not guaranteed and subject to change and cancellation. Please check with your recruiter for more details." That's Benefits. Next: "Equal Employment Opportunity ..." boilerplate, remove. Next: "Affirmative Action and Disability Accommodation Applicants wishing to receive information on Blue Origin’s Affirmative Action Plans, or applicants requiring a reasonable accommodation in order to participate in the application and/or interview process, please contact us at EEOCompliance@blueorigin.com. Please note this is a publicly managed inbox. Please do not include any personal medical information in your request." That's boilerplate, remove. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (company mission + role description + culture statement). Responsibilities (list of duties). Requirements (minimum qualifications + export control + background check). Qualifications (preferred qualifications). Skills (maybe programming languages etc? Could be under Requirements or Skills. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide what goes where. Typically Skills could be separate from Requirements/Qualifications. But we have programming languages listed under Minimum Qualifications: "Good Knowledge of common programming languages such as C/C++, Python". That could be Skills. Also experience with Linux, GitLab, etc could be Skills. However we already have those under Preferred Qualifications. To avoid duplication, we could put technical skills under Skills section, and keep Requirements as education/experience, and Qualifications as preferred qualifications. But we must not invent sections if content is thin. Let's see if we have enough for Skills: programming languages, Linux, GitLab, Confluence, JIRA, StateFlow, State Machine, DO-178/DO-278, PLCs, modeling/simulations, software integration, experience in automotive/aviation/space industry. Many of those are already in Preferred Qualifications. Could we merge Preferred Qualifications into Skills? The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide distribution. We could treat Minimum Qualifications as Requirements, Preferred Qualifications as Qualifications, and then Skills could be a subset like programming languages, tools, etc. But we risk duplication. However we could still include Skills with specific technical skills not covered elsewhere: programming languages (C/C++, Python), Linux, GitLab, Confluence, JIRA, StateFlow, State Machine, DO-178/DO-278, PLCs, modeling/simulations, software integration. Some of those appear in Preferred Qualifications already. But we could still list them under Skills; duplication is okay as long as we preserve all substantive information. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited, but we should avoid unnecessary repetition? Not explicitly forbidden. However better to avoid duplication to keep concise. But we can include Skills as a separate section listing technical skills: programming languages, Linux, GitLab, Confluence, JIRA, StateFlow, State Machine, DO-178/DO-278, PLCs, modeling/simulations, software integration. That covers many of the Preferred Qualifications items; we could then keep Preferred Qualifications under Qualifications but maybe just note "Experience with modeling and simulations, software integration, StateFlow/State Machine, DO-178/DO-278, PLCs/embedded controllers, automotive/aviation/space industry, Linux, GitLab, Confluence, JIRA". That's essentially same as Skills. To avoid duplication, we could merge Preferred Qualifications into Skills and keep Qualifications empty? But we must include a section only when posting has real specific content for it. If we put Qualifications heading but no content, that's not allowed. So we need to ensure each heading we output has content. Thus we need to decide which sections to include: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also Qualifications if we have distinct content not covered elsewhere. Let's see if we have any content that is not covered by Requirements or Skills: The Preferred Qualifications list includes items that could be considered Qualifications (preferred). If we treat them as Qualifications, we need to keep them. Then Skills could be something else like