Description
We are seeking an experienced Independent Hardware Engineer to take end-to-end ownership of hardware designs across the full development lifecycle.
This role is ideal for a senior engineer with strong autonomy, accountability, and engineering discipline. The successful candidate will own key hardware deliverables, make independent technical decisions, identify risks early, and deliver results against defined project milestones.
Responsibilities
- Own hardware design activities from schematic design and component selection through bring-up, validation, failure analysis, and sustaining support.
- Develop structured bring-up plans, test procedures, debug strategies, and validation documentation.
- Perform local hardware bring-up using available lab equipment and coordinate additional testing through remote or centralized laboratories.
- Work closely with remote hardware, software, FPGA, systems, manufacturing, and lab teams.
- Analyze test results, troubleshoot hardware issues, and document findings clearly.
- Present and defend hardware designs in schematic reviews, milestone reviews, readiness reviews, and technical surveys.
- Communicate design decisions, risks, trade-offs, open issues, and validation status clearly.
- Write basic microcontroller firmware in C/C++ to support bring-up and validation, including GPIO control and peripheral configuration such as I²C, SPI, UART, ADCs, and timers.
- Support FPGA-based system integration by reading existing VHDL/Verilog code and assisting with basic debug or minor updates when needed.
Requirements
Key Qualifications:
- Proven experience in digital and mixed‑signal hardware design
- At least 6+ years of experience
- Hands‑on board bring‑up and hardware debug experience
- Ability to write basic microcontroller code for hardware validation
- Familiarity with FPGA systems and HDL at an integration/debug level
- Experience presenting designs in technical reviews and surveys
- Strong documentation, communication, and self‑management skills
- Ability to work effectively in a remote, high‑trust environment
Originally posted on