DirectJobHub
Jobs · Engineering · California

Senior Reliability Test Engineer

Astranis Space Technologies · San Francisco Bay Area · 1 mo ago
On-siteEngineering$145k–$235k/yrFull-time
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. The posting includes description of role (Senior Reliability Test Engineer) with responsibilities list. It includes requirements list. It includes "What we offer" which includes benefits and base pay range. It does not mention schedule. So we include About the role (maybe a brief paragraph summarizing role), Responsibilities (list), Requirements (list), Qualifications? The posting has "Requirements" and also "Bonus" items; but we can treat Requirements as the list of required qualifications. Could also have Qualifications section separate? The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. The posting includes: description (role overview) -> About the role. Then bullet list of responsibilities (Develop and execute..., Design..., Establish..., Review..., Lead..., Build..., Serve..., Coordinate..., Perform..., Define..., etc). That's Responsibilities. Then "Requirements" bullet list: B.S. ..., 5+ years..., Hands-on testing..., Experience standing up..., Experience generating..., Domain depth..., Experience owning..., Proven track record..., Expertise..., Failure investigation..., Design review..., Strong technical..., Working proficiency... That's requirements. Then "Bonus" items: M.S., Familiarity with standards, Weibull++, HV testing, JMP..., Familiarity with Linux..., etc. Those could be considered Skills or Qualifications? Could put them under Skills or Qualifications. The instruction says we can include Skills section if there is real specific content. The bonus items are specific skills/knowledge. So we could make a Skills section for bonus items. Then "What we offer": includes compensation package, equity, benefits, base pay range. So we can have Benefits (list of benefits: equity, healthcare, disability/life insurance, 401(k), flexible PTO, free on-site catered meals). Pay: base salary range $145,000—$235,000 USD. Also mention that compensation includes equity etc but we already have Benefits. Pay section just base salary. Schedule: not present, so omit. We also need to include any metadata like Job ID? Not present. So ignore. We must not repeat job title as heading. Already not. We must not include boilerplate like EEO, SMS terms, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given? We can keep them but maybe rephrase? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the content verbatim (or close) but not omit any detail. We can keep bullet points as
  • items. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

    About the role

    As a Senior Reliability Test Engineer you work at the intersection of every engineering discipline to ensure our hardware meets the highest bar for quality and reliability. You own reliability for complex electromechanical and electronic hardware from concept through high-rate production and on-orbit operations. You set the targets, build the analyses and test frameworks that prove them, own the labs and tooling that generate the evidence, and lead the investigations when hardware fails. The ideal candidate is self-driven and has designed reliability test campaigns from the ground up.

    Responsibilities

    • Develop and execute qualification and validation test plans: environmental, accelerated life, shock, vibration, thermal cycling, HALT, and HASS.
    • Design, build, and automate test equipment, fixturing, and instrumentation end to end in Python, maximizing throughput against rapid design cycles.
    • Establish reliability targets across PCBAs, power electronics, avionics, actuators, batteries, high-speed digital and RF systems, and develop the unit-level mission profiles that every prediction and test profile derives from.
    • Review block diagrams, interface control documents, and schematics and guide teams on design for reliability before designs lock.
    • Lead DFMEA and Fault Tree Analysis with cross-functional teams, and convert the output into design verification plans and implemented design changes.
    • Build and maintain reliability models as living artifacts. Create physics-of-failure predictions, mission risk quantification, and Weibull analysis on qualification, production, and field data.
    • Serve as the escalation point for reliability risks: triage severity, then lead containment and root-cause investigation of high-impact failures from validation, production, and on-orbit anomalies.
    • Coordinate failure analysis and destructive physics analysis using: electrical characterization, microscopy, thermal imaging, X-ray, CT, cross-sectioning, and SEM-EDS.
    • Perform analyses on field telemetry, identify performance and degradation trends, update mission profiles, and influence upstream teams to prioritize work that prevents reliability failures.
    • Define entry and exit criteria for program gates and mentor engineers to raise reliability capability across the company.

    Requirements

    • B.S. in Mechanical, Electrical, Physics, Materials Science, or an equivalent technical discipline.
    • 5+ years in reliability, test, or design engineering on high-reliability hardware or 3+ years with an M.S.
    • Hands-on testing experience with mechanical, electrical, and electromechanical systems, and with a wide range of sensors, actuators, instrumentation, and DAQ devices.
    • Experience standing up reliability engineering frameworks for a product or program, covering detailed reliability analysis, development testing, production testing, and field data analysis.
    • Experience generating qualification test requirements and executing tests that proactively characterize product behavior and iteratively improve designs and reliability estimates.
    • Domain depth in one or more of: EEE piece parts, avionics, PCBA reliability, battery systems, EV powertrain or HV devices, thermal systems, actuators, or solar cells.
    • Experience owning reliability infrastructure: test labs and chambers, failure analysis equipment, metrology and instrumentation, automatic testing equipment and fixtures.
    • Proven track record of driving systemic improvements and shaping engineering strategy.
    • Expertise in reliability analysis: FMEA/FMECA, FTA, predictive modeling, and Weibull analysis.
    • Failure investigation experience with a proven record of solving problems and preventing recurrence.
    • Design review experience (PDR, CDR, MRR) and confidence presenting to every level of leadership.
    • Strong technical writing: test plans, reports, requirements, standards, and specifications.
    • Working proficiency in Python, C++, or your coding language of choice.

    Skills

    • M.S. in an engineering discipline, or a degree specifically in Reliability Engineering.
    • Familiarity with ASTM, JEDEC, IEEE, ISO, and MIL test standards.
    • Weibull++, ReliaSoft, or equivalent.
    • HV testing experience.
    • JMP, Python, or R for data analysis.
    • Familiarity with Linux, shell scripting, software/firmware HITL/SITL, and Python/SQL for data analysis.

    Benefits

    • Significant equity package via incentive stock options.
    • High-quality company-subsidized healthcare.
    • Disability and life insurance.
    • 401(k) retirement planning.
    • Flexible PTO.
    • Free on-site catered meals.

    Pay

    Base Salary $145,000—$235,000 USD.

    We should not include Schedule. Check that we didn't repeat job title as heading. Good. We omitted the line about U.S. Citizenship requirement etc. That's substantive? It's a requirement for eligibility. Should we include? It's under "What we offer"? Actually it's after base salary. It's a requirement: "U.S. Citizenship, Lawful Permanent Residency, Or Refugee/Asylee Status Required". That is a requirement (eligibility). Should we include it under Requirements? It's a specific requirement. The instruction says preserve ALL substantive information. So we need to include that. Where to put? Could add to Requirements list as an item. Or maybe a separate section like "Eligibility". But we only have allowed headings list; we could add to Requirements. So add an item: "U.S. Citizenship, Lawful Permanent Residency, or Refugee/Asylee Status required (to comply with U.S. Government space technology export regulations)". Keep the detail. Also there is a line about "Our mission and products are built for everyone..." that's EEO boilerplate; we should remove. Also SMS terms etc remove. Also "Astranis pay ranges are informed..." that's descriptive about pay; we could incorporate into Pay section maybe as a sentence. But we already have base salary range. The instruction says preserve ALL substantive information; we could add a sentence after base salary: "Astranis pay ranges are informed and defined through professional-grade salary surveys and compensation data sources. The actual base salary offered to a successful candidate will additionally be influenced by a variety of factors including experience, credentials & certifications, educational attainment, skill level requirements, and the level and scope of the position." That's substantive. So include in Pay section as a paragraph. Also "All our positions offer a compensation package that includes equity and robust benefits. Base pay is just one component of Astranis’s total rewards package." That's also substantive; we could include in Benefits section intro or Pay section. Let's add a paragraph in Benefits: "All our positions offer a compensation package that includes equity and robust benefits. Base pay is just one component of Astranis’s total rewards package." Also mention "Your compensation also includes a significant equity package via incentive stock options, high-quality company-subsidized healthcare, disability and life insurance, 401(k) retirement planning, flexible PTO, and free on-site catered meals." That's already covered in Benefits list; we could keep as list. We need to ensure we don't duplicate. We'll include a brief intro paragraph then list. Now check for any other substantive content: The initial paragraph about Astranis building satellites etc. That's company overview; could be part of About the role? Might be considered background. The instruction says include a section ONLY when posting has real specific content for it. The About the role section we already have a paragraph describing role. Could also include company overview as part of About the role? Might be okay but not required. The initial description is about Astranis; not directly about the role but could be considered context. However we already have role description; we could keep it as part of About the role preceding the role-specific paragraph. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that company overview somewhere. Could add a

    before the role-specific paragraph within About the role. Let's do that. Thus About the role will have two paragraphs: first about Astranis (company overview), second about the role. Now ensure we didn't include any boilerplate like EEO, SMS terms, legal, etc. Remove. Now produce final HTML. Check for any missing content: The "Bonus" items we moved to Skills. Good. Check that we didn't miss any requirement like "Experience standing up reliability engineering frameworks for a product or program, covering detailed reliability analysis, development testing, production testing, and field data analysis, Experience generating qualification test requirements and executing tests that proactively characterize product behavior and iteratively improve designs and reliability estimates," Actually there is a comma splice; we captured as two separate bullets

    • Similar jobs