Control Systems Engineer III
for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. We have: - Application Close Date: "Applications will be accepted on an ongoing basis until the requisition is closed." This is metadata; we can fold into short
or drop. Probably drop or short p. - At Blue Origin, we envision... This is about the company/mission. Could be "About the role" or maybe "About the company". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have an "About the role" section containing the mission description and role description. - The role supports development and operations of New Glenn... repeated twice. We'll include that. - As part of a hardworking... team... etc. That's responsibilities? Actually that's description of team and tasks. Could be part of responsibilities. - Responsibilities Include But Are Not Limited To ... list. - Minimum Qualifications list. - Preferred Qualifications list. - Base Pay Range For WA applicants is $164,652.00 - $230,512.80 Other Site Ranges May Differ - Benefits list. - Culture Statement (maybe not a heading; we could incorporate into About the role or drop). It's not one of the prescribed headings; we could omit or put in About the role. - Export Control Regulations (citizenship) - could be part of Requirements or Qualifications? It's a requirement: Must be US citizen etc. Could be part of Minimum Qualifications or Requirements. We'll include in Requirements. - Background Check Required... - could be part of Requirements. - Benefits section already. - Equal Employment Opportunity etc. - boilerplate to remove. - Affirmative Action and Disability Accommodation - boilerplate to remove. We need to avoid repeating job title as heading. Not needed. We need to output only HTML fragment, no /, no markdown fences. We need to include sections only when posting has real specific content. So we will have:
Application close date: Applications will be accepted on an ongoing basis until the requisition is closed.
maybe. ThenAbout the role
with paragraph(s) containing mission description and role description. ThenResponsibilities
with- ... list.
Then
Minimum Qualifications
with- ... list.
Then
Preferred Qualifications
with- ... list.
Then
Pay
with paragraph containing base pay range. ThenBenefits
with- ... list.
We might also include a
Requirements
for citizenship/background check? But we already have Minimum Qualifications includes some; citizenship could be part of Minimum Qualifications. However Minimum Qualifications list didn't include citizenship; we could add a separate Requirements section for citizenship and background check. But we could also fold into Minimum Qualifications as extra items. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could have Requirements separate from Qualifications. But we already have Minimum Qualifications and Preferred Qualifications; maybe we treat those as Qualifications. The instruction says we can use Qualifications heading. But we have both minimum and preferred; we could combine under Qualifications with subheadings? But better to follow the example: they list Requirements, Qualifications, Skills as separate possible headings. We have Minimum Qualifications and Preferred Qualifications; we could put them under Qualifications heading with two sub-lists? But we need to preserve all substantive info. Could do:
Qualifications
Minimum:
- ...
Preferred:
- ...
- for any list of duties/requirements/benefits. So we can have nested lists? Probably okay.
Alternatively we could keep Minimum Qualifications and Preferred Qualifications as separate headings, but those are not in the example list; but they are still headings; we could use
Minimum Qualifications
andPreferred Qualifications
. The instruction says "e.g." not exclusive. So we can use those. Thus we will have: - About the role - Responsibilities - Minimum Qualifications - Preferred Qualifications - Pay - Benefits We might also include a short paragraph for Application close date. We must not include boilerplate like Culture Statement, Export Control Regulations, Background Check, EEO, etc. However citizenship requirement is substantive; we should keep it. Where to put? Could be under Minimum Qualifications as an item: "Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum." Similarly background check maybe not needed? It's a requirement but could be considered boilerplate? It's a condition of employment; we could keep it under Minimum Qualifications as well. Thus we will add those items to Minimum Qualifications list. Now let's extract content. About the role paragraph(s): "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 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. 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. As part of a hardworking and complementary team of engineers, you will develop and verify inner-loop flight control applications for New Glenn launch vehicle systems. Together, we will positively contribute to all aspects of developing and verifying control software applications. Our team serves in several traditionally distinct roles: Systems Engineering, Fluids Engineering, Control Systems Engineering, Software Development, and Software Verification. We build and validate engineering simulations of fluids subsystems to verify that control algorithms and software satisfy requirements. Successful team members demonstrate excellent engineering judgment and an ability to work independently with minimal direction and supervision. We are looking for engineers to apply their technical expertise, leadership skills, and dedication to quality to positively advance safe human spaceflight. Passion for our mission and vision is required and is a key indicator of a successful candidate!" We can combine into one or two paragraphs. Responsibilities list: "Model-based design and control software development for multiple simultaneous New Glenn configurations Collaborate across New Glenn Autonomy with fluids, systems engineering, software integration, avionics and vehicle operation teams Conduct Monte Carlo simulations and covariance analysis for system performance characterization Support Hardware-in-the-Loop (HIL) and Software-in-the-Loop (SIL) testing Deliver software for vehicle testing and flight Support bench tests, integrated vehicle tests and flight operations including basic operator training" We need each as - . Minimum Qualifications list (original): "Strong engineering fundamentals; particularly in modeling dynamics and model validation. Deep understanding of fundamentals of controls, frequency response analysis, stability margins etc. Experience with filtering, state estimation (Kalman filters, extended Kalman filters) and optimal control techniques (LQR, LQG) High proficiency in Simulink and MATLAB for modeling, simulation, control design, and automatic code generation. Experience with analysis-based software verification and unit testing (software-in-loop and hardware-in-loop) Practical experience in software development, including embedded C or C++ programming. Proficiency with software configuration management tools such as git, subversion. Excellent technical writing and verbal communication skills. B.S. (or M.S. or Ph.D.) in aerospace, mechanical, or related engineering with 5+ years of real project experience. Ability to support 40–50-hour work weeks with occasionally higher effort as required to meet schedule. Ability to earn trust, maintain positive and professional relationships, and strengthen our culture of inclusion. Must be a U.S. citizen or national, U.S. permanent resident (current Green Card holder), or lawfully admitted into the U.S. as a refugee or granted asylum." Add background check? The posting includes: "Background Check Required for all positions: Blue’s Standard Background Check Required for Certain Job Profiles: Defense Biometric Identification System (DBIDS) background check if at any time the role requires one to be on a military installation Required 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 quite detailed but seems generic boilerplate for many roles; but it's still substantive. However the instruction says remove boilerplate like EEO etc. Background check might be considered boilerplate but it's a requirement. I'd keep a short note: "Background check required." But we could include as an item. Given the instruction to remove duplicated lines and boilerplate, but we need to preserve ALL substantive information. The background check is substantive but maybe considered boilerplate; but it's a condition of employment. I'd include a concise item: "Must pass a standard background check; additional checks may apply depending on job profile." But to be safe, we could include the exact sentences but they are long. However they are not duplicated elsewhere. I'd include a short summary. Preferred Qualifications list: "Substantial experience and success developing controls for real systems. Simulation experience with high-pressure gas and cryogenic propellant systems. Test support experience for bench testing or integrated testing of similar systems Deep knowledge of systems engineering for safety-critical systems. Experience with rockets, missiles, or other aerospace vehicle systems." Pay: "Base Pay Range For WA applicants is $164,652.00 - $230,512.80 Other Site Ranges May Differ" We'll output as paragraph. Benefits list: "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." We can turn each sentence into
- for any list of duties/requirements/benefits. So we can have nested lists? Probably okay.
Alternatively we could keep Minimum Qualifications and Preferred Qualifications as separate headings, but those are not in the example list; but they are still headings; we could use
- ... list.
We might also include a
- ... list.
Then
- ... list.
Then