Principal Architect, Autonomous Systems (Ground and Space)
or drop it. The "Application Close Date Applications will be accepted on an ongoing basis until the requisition is closed." is minor metadata; we can put in a short
maybe. But we should not include headings for Job ID etc. We need sections only when there is real specific content. We have: - Role Summary (maybe under "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing role summary paragraph.
- Responsibilities: list of duties.
- Requirements: maybe Minimum Qualifications? Could be "Requirements". Or "Qualifications". The instruction says we can use Requirements, Qualifications, Skills. We have Minimum Qualifications and Preferred Qualifications. Could combine into "Qualifications" with sub-sections? But we must not create thin sections. Probably better to have "Requirements" for Minimum Qualifications, and "Preferred Qualifications" as a separate section? But they said prefer a few substantive sections over many thin ones. Could combine Minimum and Preferred into one "Qualifications" section with two lists: Required and Preferred. But we need to follow instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "Requirements" for minimum qualifications, and "Preferred Qualifications" maybe as a subsection? But they didn't list Preferred Qualifications as example; but we could still use "Qualifications" heading and include both required and preferred within. However they said "include a section ONLY when the posting has real, specific content for it". So we can have a "Qualifications" section with both required and preferred lists. That seems fine.
- Benefits: we have benefits description.
- Pay: we have Base Pay Range.
- Schedule: not mentioned, so omit.
- Skills: maybe not separate; we could incorporate into Qualifications.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings.
We need to remove boilerplate: EEO, equal opportunity, etc. Also remove "Culture Statement" maybe? It's not a standard heading; but we could incorporate into About the role? It's a statement encouraging applicants; could be considered boilerplate? It's not EEO but it's a culture statement encouraging to apply; might be considered generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Culture statement is not exactly those, but it's a generic encouragement; maybe we can keep it as part of About the role? It's not duplicate. However it's somewhat generic; but we can keep it as a paragraph under About the role.
Also need to remove "Export Control Regulations", "Background Check Required for all positions:" etc. Those are legal/boilerplate; should be removed.
Also remove "Equal Employment Opportunity" etc.
Also remove "Affirmative Action and Disability Accommodation".
Also remove "Export Control Regulations" etc.
Also remove "Background Check Required for all positions:" and its details.
Also remove "Culture Statement" maybe? But it's not exactly boilerplate; but it's a generic statement encouraging applicants; could be considered part of About the role. We'll keep it as a paragraph.
Also remove "Application Close Date" line? It's metadata; we can fold into a short
maybe at top. But we could also drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
for Application Close Date. Let's include a
at top: "Applications will be accepted on an ongoing basis until the requisition is closed." Now we need to preserve all substantive information: role summary paragraph, responsibilities bullet list, minimum qualifications list, preferred qualifications list, base pay range, benefits list. We must not invent or summarize away detail. So we need to keep exact details. Let's extract: Role Summary paragraph: "You are the technical owner of Blue National Security's autonomy product architecture, spanning both ground and space. You will define how autonomous capability is decomposed across the ground segment and the vehicle, drive that architecture through implementation across every contributing discipline, and carry it to operational deployment." That's the role summary. Responsibilities: multiple sentences each starting with a verb. We need to put them as
- . Let's list each responsibility sentence:
- Own the end-to-end autonomy product architecture across ground and space.
- Define the system decomposition, interfaces, and functional allocation between ground based and onboard autonomy, and own the technical roadmap that takes it to flight.
- Make and defend the hard allocation decisions.
- Determine what reasoning executes on orbit versus on the ground, and architect for degraded, latent, and communications denied operations.
- Drive architectural coherence across disciplines. Coordinate across ground systems, perception, flight software, electrical hardware, GN&C, simulation, and navigation and trajectory functions, translating operational requirements into a single, consistent, buildable architecture.
- Own the embedded AI/ML realization. Guide model architecture, training and data pipelines, compression and quantization, and hardware aware optimization, so that models meet real time and deterministic behavior requirements within actual SWaP-C constraints.
- Build the assurance case for the full autonomy loop. Establish V&V practices for ML in high consequence systems, including uncertainty quantification, fault detection and isolation, runtime assurance, robustness testing, and simulation to hardware validation.
- Set the technical direction and raise the team with you. You own the autonomy architecture baseline and technical roadmap. You will mentor and unblock engineers across the AI, FSW and Autonomy team, and represent Blue National Security's autonomy and AI/ML capability to government customers and partners.
We need to ensure we keep all details.
Minimum Qualifications list:
- B.S. in Computer Science, Electrical or Computer Engineering, Aerospace Engineering, Applied Mathematics, or a related technical field, or equivalent hands on experience.
- 10+ years developing software or systems for mission or safety critical applications, including architectural ownership of a distributed or multi segment system.
- 3+ years developing and deploying ML systems into production, with demonstrated deployment on resource constrained or embedded targets such as edge GPUs, FPGAs, DSPs, or radiation tolerant processors.
- Proficiency in Python and C/C++, and working expertise with modern ML frameworks (PyTorch, TensorFlow, or ONNX Runtime) and edge optimization toolchains (quantization, pruning, TensorRT, TFLite, or equivalent).
- Demonstrated experience leading architecture across multiple engineering disciplines, including flight software, hardware, and vehicle dynamics or controls.
- Demonstrated ability to build technical consensus across disciplines, earning influence through depth and credibility, and to brief executives, government customers, and engineering peers with equal clarity.
- 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.
Preferred Qualifications list:
- Advanced degree in Computer Science, Electrical Engineering, Robotics, or Aerospace Engineering.
- GN&C, navigation, trajectory, or estimation background for flight vehicles, including experience bringing learning-based methods into classical control and estimation architectures.
- Autonomous spacecraft operations experience: on orbit fault detection and isolation, autonomous mission sequencing, RPO, closed loop vehicle control, or autonomous operations in communications denied environments.
- Ground segment or mission operations experience, including tasking, ground autonomy, or ground to space autonomy handoff.
- Space grade or radiation tolerant compute (NVIDIA Orin, Xilinx Versal, rad hard SoCs); real time and safety critical environments (RTOS, bare metal); hardware in the loop and simulation to hardware workflows; or formal V&V methods for ML.
- DoD, USSF, NRO, or IC program experience, and an active U.S. Secret or TS/SCI clearance.
Base Pay Range: "Base Pay Range For CO applicants is $218,520.00 - $305,926.95 Other Site Ranges May Differ". We need to keep that exactly. Probably we should keep as a
. 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 need to keep that as a
- maybe each benefit as separate items? The instruction: Use
- for any list of duties/requirements/benefits. So we should split benefits into list items. However the benefits paragraph includes multiple items separated by commas and periods. We need to parse them into list items preserving all detail. Let's extract:
- 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%
- 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 need to keep the last two sentences as items maybe.
Now we also have culture statement paragraph: "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."
We can keep that as a
maybe under About the role or separate section? It's not a standard heading; but we could incorporate into About the role as additional paragraph. Now we need to output only HTML fragment, no /, no markdown. Let's structure:
Applications will be accepted on an ongoing basis until the requisition is closed.
About the role
You are the technical owner of Blue National Security's autonomy product architecture, spanning both ground and space. You will define how autonomous capability is decomposed across the ground segment and the vehicle, drive that architecture through implementation across every contributing discipline, and carry it to operational deployment.
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
- for any list of duties/requirements/benefits. So we should split benefits into list items. However the benefits paragraph includes multiple items separated by commas and periods. We need to parse them into list items preserving all detail. Let's extract:
- 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%
- 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 need to keep the last two sentences as items maybe.
Now we also have culture statement paragraph: "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."
We can keep that as a
- maybe each benefit as separate items? The instruction: Use