Technical Specialist Sr

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Minimum Qualifications and Preferred Qualifications), Benefits, Pay (Base Pay Range), maybe Schedule? Not present. Travel requirement is mentioned but not schedule. Should we include a "Travel" section? Not required heading list includes Schedule only. So we omit Schedule if not present. We need headings:

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. We must not repeat job title. No Job ID. Remove boilerplate: Application Close Date, vision statements repeated, etc. Keep substantive info. We need to preserve all substantive information: responsibilities list, qualifications, preferred qualifications, base pay range, benefits, travel requirement (up to 25% travel). Also mention role part of ACP etc. Should we include an "About the role" section summarizing the role description? Probably yes: we can put a paragraph describing the role: part of Blue Origin Engines business unit, ACP organization, design and deliver avionics ground and test systems, etc. Must not duplicate repeated sentences. We'll condense but preserve all details: we must not invent or summarize away detail. However we can combine similar sentences but must keep all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we cannot omit details, but we can rephrase? Probably we should keep the info verbatim but can restructure. Safer to keep the sentences as they are, maybe split into paragraphs. We need to avoid filler like "commensurate with experience". Not present. We need to include sections only when posting has real specific content. Thus sections: About the role (maybe we can call it "About the role"): include description of role, mission, business unit, ACP, responsibilities overview? But we also have Responsibilities section separate. So About the role can contain the overview: "This role is part of the Blue Origin Engines business unit... As part of the ACP Test Equipment and Manufacturing Automation team, you will design and deliver avionics ground and test systems supporting engineering development and production..." etc. Also mention travel up to 25%. Responsibilities: list bullet points from "Responsibilities" block. Requirements: maybe combine Minimum Qualifications and Preferred Qualifications under "Requirements" or separate "Minimum Qualifications" and "Preferred Qualifications"? The heading list includes Requirements, Qualifications, Skills. We could use "Requirements" for minimum qualifications, and "Preferred Qualifications" maybe as a subsection? But we only allowed headings from list; we could use "Qualifications" for both minimum and preferred? Might be better to have "Minimum Qualifications" and "Preferred Qualifications" as subheadings? Not allowed. Could use "Requirements" for minimum, and "Preferred Qualifications" maybe as a

  inside Requirements? But we need to preserve all info. Could create a section "Requirements" with

  for minimum qualifications, then another
  for preferred qualifications with a note? Might be okay. Better: Use "Requirements" heading for minimum qualifications, and then a separate "Preferred Qualifications" heading (though not in list). The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. We could put both minimum and preferred under "Requirements" or "Qualifications". Perhaps "Qualifications" heading can contain both minimum and preferred, with sub-bullets labeled. We also have "Skills" maybe not needed. We have Benefits section. Pay section: Base Pay Range. We also have travel requirement: could be placed under About the role or Responsibilities? It's a requirement; maybe include in About the role paragraph. We must not include boilerplate like Equal Employment Opportunity, Export Control Regulations, Background Check, etc. Remove those. Also remove duplicated lines: there is duplicate paragraph about Blue Origin Engines business unit repeated twice; we should keep only once. Now craft HTML. Structure:

  About the role

  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 is part of the Blue Origin Engines business unit, where our focus is the design, development, manufacturing, and testing of engines and propulsion systems. Built for multiple uses, our family of engines is powering the next generation of rockets for commercial, civil, national security, and human spaceflight. This position resides within the Avionics & Control Products (ACP) organization, part of the Engine Business Unit. As part of the ACP Test Equipment and Manufacturing Automation team, you will design and deliver avionics ground and test systems supporting engineering development and production. The test systems will provide an environment to integrate the electronics and software for system development, verification, and validation. This will include software simulations and hardware emulators, as well as software for interfacing with these simulators and emulators. We are looking for someone to apply their technical expertise, leadership skills, and commitment to quality to positively impact safe human spaceflight. Passion for our mission and vision is required! Position requires up to 25% travel to rocket engine test sites.

  Responsibilities

  • Participate in the requirements, design, architecture, procurement, build, integration, and checkout of the component testers
  • Support a development environment with open box testing and card to card level testing
  • Perform checkout and troubleshooting of electronic assemblies
  • Create and release drawings of the component hardware infrastructure, rack layouts, harnesses, breakout boxes/panels, power distribution, and grounding
  • Create and release manufacturing work orders and maintain an active supply chain
  • Coordinate with technicians for the build, assembly, and installation of equipment and harnesses
  • Support the integration of flight avionics, hardware, operator consoles, and test equipment to verify the requirements and performance of avionics units under test
  • Maintain configuration control of the drawings and the tester configuration
  • Support problem investigation and resolution
  • Assemble Component Test electrical and mechanical systems using engineering drawings
  • Build, test and rework cable and harness assemblies

  Requirements

  • Associate degree in a STEM Technology Program or 10+ years of experience in aerospace test
  • 5+ years of industry experience with electrical/electro-mechanical assemblies
  • Experience assembling and handling small mechanical and electrical parts
  • Ability to interpret electrical schematics, wiring diagrams, mechanical drawings, and written assembly procedures
  • Proficient in the use of standard electronic lab test and troubleshooting equipment
  • Good written, verbal, and interpersonal communication skills
  • Strong analytical and organizational skills, attention-to-detail, and desire for continuous improvement
  • Demonstrate to thrive as a member of a tightly integrated team

  Preferred Qualifications

  But Preferred Qualifications not in allowed headings. Could we use "Qualifications" heading to include both minimum and preferred? But we already used Requirements for minimum. Maybe we rename "Requirements" to "Minimum Qualifications" and then have another heading "Preferred Qualifications". However instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those as examples. Safer to stick to those. We could put preferred qualifications under "Qualifications" heading. Then we need to also include minimum qualifications somewhere else, maybe under "Requirements". So we have both Requirements and Qualifications sections. Thus:

  Requirements

  (minimum)

  Qualifications

  (preferred) Under Qualifications we list preferred qualifications. Let's do that. Preferred qualifications list: - B.S degree in electrical engineering - Experience designing avionics labs, electrical ground support equipment, and/or test assets for electrical equipment testing - Working knowledge of digital circuits, analog circuits, computers, microprocessors, and networks - Experience with modeling and drafting engineering drawings using CREO, Zuken (or equivalent) Now Benefits:

  Benefits

  • 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%
  • 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.
  But note the last bullet includes a sentence that is not a simple list item; maybe we keep as

  inside Benefits? The instruction: Use

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

    for prose. Benefits list is a list; we can keep each item as

  • . The last item is a sentence; still okay as
  • . Pay:

    Pay

    Base Pay Range For WA applicants is $124,476.00 - $174,265.35. Other Site Ranges May Differ.

    We should not include "Other Site Ranges May Differ" if it's not specific? It's part of the posting; we keep. Now ensure we removed all boilerplate: Application Close Date, repeated vision, duplicate sentences, EEO, Export Control, Background Check, Culture Statement, etc. Check for any leftover: The paragraph about "Don’t meet all desired requirements? Studies have shown..." is part of Culture Statement; we should remove. Also remove "Equal Employment Opportunity" etc. Now produce final HTML fragment. Check that we didn't miss any substantive info: The role description includes "Blue Origin is self-funding rapid development of multiple in-space flight systems – over a range of sizes, propellant types, and technical challenge." Did we include that? Not yet. We omitted that sentence. It's substantive. Should we include it in About the role paragraph. Let's add after mission statement. Add: "Blue Origin is self-funding rapid development of multiple in-space flight systems – over a range of sizes, propellant types, and technical challenge." Also we had "Join us in lowering the cost of access to space and enabling Blue Origin’s vision of millions of people living and working in space to benefit Earth." Already covered. Also "This position will directly impact the history of space exploration and will require your commitment and detailed attention towards safe and repeatable space flight." Might be covered by passion statement; but we can include. Let's incorporate these details into About the role paragraph without losing any. We'll rewrite About the role paragraph to include all unique statements: - At Blue Origin, we envision millions of people living and working in space for the benefit of Earth. - We’re working to develop reusable,