Techincal Writer

Possible 3 Month CTH | No Fees | Do Not Re-Post | Confidential

TMR
Role:
Techincal Writer

Work location:

Palo Alto, CA or Irvine, CA
Background and Meet and Greet: MANDATORY

The Technical Writer for Automotive ECU Validation is responsible for creating, organizing, and maintaining high quality technical documentation that supports the validation and verification of Electronic Control Units (ECUs). This role acts as a bridge between test engineers, software/hardware teams, suppliers, and OEM stakeholders to ensure clarity, compliance, and traceability across the validation lifecycle.

• Documentation Development
  • Create and maintain test plans, test procedures, test reports, traceability matrices, and validation summaries.
• Translate engineering inputs (requirements, test data, Jira issues, Vector tools output) into clear, structured documents aligned with OEM standards.
• Develop DFMEA/PFMEA supporting docs, validation compliance checklists, and safety related documentation (ASIL A-D where applicable).
• Requirements & Traceability
  • Interpret system, software, and hardware requirements from DOORS, Jama, or Polarion.
  • Map validation test cases to requirements ensuring full coverage and compliance.
  • Work closely with functional safety teams to align documentation with ISO 26262 processes.
• Test Artifacts & Evidence Management
  • Convert raw test logs (CANoe/CANalyzer, INCA, ETAS tools, scripts) into readable, engineering grade evidence.
  • Ensure standardized formatting, version control, and metadata tagging across all validation artifacts.
• Cross-Functional Collaboration
  • Work with validation engineers, calibration teams, software developers, and program managers.
  • Participate in design reviews, validation reviews, and stakeholder meetings to gather documentation requirements.
  • Support suppliers in aligning their deliverables with OEM documentation expectations.
• Compliance & Process Adherence
  • Ensure documentation follows automotive standards such as:
  • ISO 26262 (Functional Safety)
  • ASPICE
  • SAE J1939 / CAN
  • OEM-specific documentation guidelines (e.g., Ford, GM, Stellantis, Rivian, Nissan)
  • Maintain consistency across documentation repositories (SharePoint, Confluence, Git Lab, or PLM systems).

• Strong understanding of automotive ECUs (Body, Powertrain, Chassis, ADAS, Infotainment).
• Familiarity with tools such as CANoe/CANalyzer, INCA, ETAS, dSPACE, Vector tools, XCP/UDS, logging tools.
• Experience with test frameworks, validation workflows, and verification methodologies.
• Ability to read DBC files, CAN logs, test outputs, and basic diagnostic services.

• Excellent technical writing skills with the ability to simplify complex engineering topics.
• Strong command of document structuring, templates, grammar, and engineering clarity.
• Proficiency with MS Office, Confluence, Visio, SharePoint, DOORS, Polarion, Jama.

• Detail oriented and structured thinker.
• Strong stakeholder communication.
• Ability to manage multiple document streams across engineering teams.

• Bachelor's degree in Electrical, Electronics, Mechanical, Automotive Engineering, or Technical Communication.
• Background in ECU development, validation, or automotive testing.
• Exposure to ASIL related documentation and safety analysis workflows.
• Experience working with global engineering teams (India, Morocco, Europe, North America).

Onsite in either Palo Alto, CA or Irvine, CA.

Client is looking for someone that can understand the ECUs at a high level, as well as the testing we do with them (in particular thermal/vibration). The task would be to write both test procedures and test reports (Top Priority).

First Name, Middle name, and Last Name:

City and State:

Open to Relocate?

Rate:

Availability:

Phone #:

Mobile #:

Email address:

Visa type:

Visa Expiration Date:

Hiring Status:

Soemia Pineda - ERM

Tel.: +***