ZipRecruiter

Log In

2

Remote Failure Analysis Engineer Jobs in San Rafael, CA

Ōura

Senior Product Quality Engineer, EE

San Francisco, CA · On-site +1

$104K - $141K/yr

In this role you will lead Early Field Failure Analysis (EFFA), field quality, and product safety ... We've been alerted to scammers posing as ŌURA recruiters, especially for remote roles. Please note:

Ōura

Hardware Reliability Engineer

San Francisco, CA · On-site +1

$120K - $152K/yr

Support failure analysis and root cause investigations, working with design, Quality, and ... We've been alerted to scammers posing as ŌURA recruiters, especially for remote roles. Please note:

Kairos Power

Senior Nuclear Facility Engineer

Alameda, CA · On-site +1

$118K - $162K/yr

Participate in hazard and failure analyses (HAZOP, FMEA, FTA) and incorporate safety insights into ... the role. #LI-remote About our Benefits We know that we have some of the most talented and ...

talentpluto

Research Engineer

San Francisco, CA · Remote

$140K - $250K/yr

Location: Remote (United States) Work Model: Remote Industry: AI training data infrastructure ... You will start by digging into the data manually to understand failure modes, then design systems ...

talentpluto

Research Engineer

San Francisco, CA · On-site +1

$140K - $250K/yr

Location: Remote (United States) Work Model: Remote Industry: AI training data infrastructure ... You will start by digging into the data manually to understand failure modes, then design systems ...

next page

Showing results 1-20

All JobsFailure Analysis Engineer JobsRemote Failure Analysis Engineer JobsRemote Failure Analysis Engineer Jobs in San Rafael, CA

Remote Failure Analysis Engineer information

See San Rafael, CA salary details

$50.7K

$103.9K

$151K

How much do remote failure analysis engineer jobs pay per year?

As of Sep 5, 2026, the average yearly pay for remote failure analysis engineer in San Rafael, CA is $103,868.00, according to ZipRecruiter salary data. Most workers in this role earn between $78,000.00 and $131,500.00 per year, depending on experience, location, and employer.

What is the difference between Remote Failure Analysis Engineer vs Remote Quality Engineer?

AspectRemote Failure Analysis EngineerRemote Quality Engineer
CredentialsBachelor's in Engineering, certifications in failure analysis or reliabilityBachelor's in Engineering, certifications in quality management or Six Sigma
Work EnvironmentLaboratory, technical analysis, remote troubleshootingProcess audits, quality control, remote data analysis
Industry UsageElectronics, manufacturing, aerospaceManufacturing, electronics, automotive
Search & Comparison IntentUnderstanding failure analysis roles, technical skillsQuality assurance, process improvement roles

The Remote Failure Analysis Engineer focuses on diagnosing product failures through technical analysis, often involving lab work and remote troubleshooting. In contrast, the Remote Quality Engineer emphasizes maintaining quality standards, process improvements, and data analysis. Both roles require engineering backgrounds and certifications but serve different functions within manufacturing and electronics industries.

Remote Failure Analysis Engineer jobs near you
Infographic showing various Remote Failure Analysis Engineer job openings in San Rafael, CA as of August 2026, with employment types broken down into 81% Full Time, 17% Part Time, and 2% Contract. Highlights an 81% Physical, 4% Hybrid, and 15% Remote job distribution, with an average salary of $103,868 per year, or $49.9 per hour.

Mechanical Engineering Expert - Remote

YO AI Labs

San Francisco, CA • Remote

$30 - $70/hr

Full-time

Posted 12 days ago

Job description

Mechanical Engineering Technician

Job Type: Contractor
Location: Remote

Job Overview

We are seeking experienced Mechanical Engineering Technicians to support an advanced AI benchmark project. You will use your hands-on technical expertise to create realistic testing, data interpretation, and failure-diagnosis scenarios.

No prior AI experience is required.

Key Responsibilities
  • Create realistic technician tasks involving test setup, instrumentation, data collection, and failure diagnosis.
  • Develop technical datasets such as test logs, calibration records, sensor outputs, and failure reports.
  • Define accurate solution pathways and next-step recommendations based on test data.
  • Create detailed 35+ point grading rubrics covering instrumentation, data interpretation, and failure analysis.
  • Document test procedures, observations, results, and diagnostic findings clearly.
  • Ensure tasks reflect real-world professional complexity rather than textbook scenarios.
Required Skills
  • Test Setup
  • Data Interpretation
  • Failure Diagnosis
  • Instrumentation
  • Sensor & Data Acquisition
  • Mechanical Testing
  • Technical Documentation
  • Data Analysis
  • Quality & Troubleshooting
Preferred Qualifications
  • 4+ years of hands-on experience in mechanical testing, laboratory, or production environments.
  • Associate degree or relevant trade/technical credential preferred.
  • Strong experience with instrumentation, sensors, data acquisition systems, and prototype testing.
  • Ability to document test procedures, results, and failure modes accurately.
  • Strong analytical and troubleshooting skills.
  • Comfortable working with CSVs, spreadsheets, PDFs, and technical datasets.
  • Ability to work independently in a remote environment.
Compensation & Availability

Compensation is output-based, with payment per approved task. Minimum weekly submission requirements apply.

Selected experts should be ready to begin their first tasks within 24–48 hours of completing onboarding. Roles are typically filled within 48 hours.

Screening Questions
  1. How many years of hands-on mechanical testing or technician experience do you have?
  2. What experience do you have with instrumentation, sensors, and data acquisition systems?
  3. Describe your experience with test setup and failure diagnosis.
  4. Have you worked with test logs, calibration records, sensor data, or failure reports?
  5. What technical documentation tools or formats do you regularly use?
  6. Are you comfortable creating detailed evaluation rubrics and diagnostic scenarios?
  7. How soon can you start?