Tracking 100,000+ career sites

Senior Hardware Engineer Jobs

This list updates hourly with senior hardware engineer roles surfaced from 100K+ company job sources across silicon, ASIC, RF, electronics, verification, mechatronics, and physical-system design.

Roles may be titled senior or principal hardware engineer, silicon or ASIC architect, RF engineer, digital design or verification engineer, electronics designer, board engineer, mechatronics specialist, test engineer, or hardware engineering manager. The work ranges from architecture and RTL through circuit or board design, simulation, verification, bring-up, characterization, system integration, and transfer to manufacturing. Semiconductor, communications, aerospace, quantum, robotics, medical-device, and computing-hardware employers each bring different development cycles and constraints. Verification ownership can be as consequential as design ownership on complex programs. Evaluate seniority through ownership of architecture or a critical subsystem, review and sign-off authority, tape-out or product lifecycle responsibility, cross-disciplinary influence, and technical mentoring. A principal individual contributor may guide designs across teams, whereas a manager is also accountable for staffing, schedules, and the quality of the group's execution.

Start with the hardware layer: silicon architecture, RTL or verification, RF, board design, mechatronics, test, or system integration. Then use the source posting to identify required HDLs, methods, EDA and laboratory tools, interfaces, and expectations for tape-out, bring-up, or production support. Clarify whether ownership ends at a component boundary or continues through system integration and manufacturing. Confirm onsite access, travel, security clearance, and export-control language directly with the employer. If an assessment is described, prepare for the named design, architecture, or debugging topics instead of assuming a standard format. For management roles, examine team size, hiring needs, and how design reviews are staffed. Employer, location, industry, compensation, and sponsorship filters address practical fit; weigh disclosed pay and equity against program risk, schedule intensity, physical access, and leadership scope.

No account is required for browsing or filters. A free account can keep hardware roles and application stages organized and provide Copilot for selected forms. Recheck access constraints at the employer source.

2,275
roles in this list
1,030
added this week
Featuring roles at
Canva
Netflix
Notion
Visa
Capital One
& 100K+ more
Got questions?

Explore our FAQ section to learn more.

This list covers senior, staff, and principal roles in computer, electronic, mechanical, and system hardware engineering, including ASIC, FPGA, board, RF, validation, verification, silicon, component, and hardware architecture work.

Show products or subsystems you owned from requirements through validation or production. Quantify performance, power, area, reliability, yield, cost, schedule, or manufacturing improvements where possible.

The mix depends on the discipline and may include circuit design, RTL, verification, FPGA or ASIC flows, PCB design, signal and power integrity, RF, lab instrumentation, validation, reliability, and design-for-manufacturing.

Expect design tradeoffs, debugging scenarios, architecture discussions, fundamentals from your specialty, and detailed reviews of products you shipped. Some employers include whiteboard problems, design exercises, or lab questions.

Design roles create components, boards, silicon, or systems and own design tradeoffs. Validation roles build test strategies, characterize behavior, find failure modes, and establish evidence that the hardware meets requirements.

Usually they are senior individual contributors responsible for architecture, technical direction, reviews, and cross-team decisions. Management roles add staffing, coaching, budgets, and performance responsibility.

Ask about lab access, simulation and automation, prototype cadence, manufacturing partners, test coverage, failure analysis, requirements quality, design reviews, documentation, and how hardware and firmware teams collaborate.

Compare product maturity, technical ownership, lab and tooling resources, tapeout or production schedules, travel, on-site expectations, supply-chain constraints, team expertise, and accountability for cost, quality, and reliability.