Explore 57 open fpga jobs at fast-growing tech, startup, and AI companies hiring right now. Build hardware logic on FPGAs for speed the CPU cannot reach.
Open Positions57 FPGA jobs
The hardware career ladder
Hardware careers grow within a discipline: electrical, mechanical, embedded, robotics, or silicon. You start as an engineer designing and testing a real part of the system, then grow to Senior and Staff as you own harder subsystems and the bring-up that makes them work. The physical world sets the pace, so the craft rewards people who can debug across the hardware and software boundary.
Above Staff the path forks. You can stay the deepest technical person as a Senior Staff or Principal engineer, owning the hardest design and architecture calls. Or you can lead people as an Engineering Manager, Director, and VP, running teams and the roadmap. As in software, the two tracks are usually paid the same at each level, so it is a choice about the work.
The pivot point: Staff Engineer
Staff is where hardware engineers choose. If you want to stay the person who solves the hardest design and bring-up problems, the Senior Staff and Principal track keeps you at the bench. If you would rather build and run teams, the Manager and Director path is yours. Both pay well and both are real.
What changes as you climb
- Electrical and mechanical engineering are the biggest slices by open roles; embedded, robotics, and chip design are smaller but fast-growing.
- Titles usually name the discipline (electrical, mechanical, firmware) rather than a generic hardware term, so the ladder runs inside each one.
- The deep IC track stays strong in hardware because bring-up and design experience is hard to replace.
- Leadership roles cluster at companies large enough to run several hardware teams at once.
Where everyone starts
Illustrative titles and pay. Real ladders vary by company. Counts are live open roles matching each level.
IC vs. Management, side by side
| Individual Contributor | Management | |
|---|---|---|
| Core work | The hardest design, bring-up, and architecture | The team, the roadmap, and the schedule |
| Judged on | The parts and systems you make work | What the whole team ships and when |
| A normal day | Design, lab bring-up, and debugging real hardware | 1:1s, planning, reviews, and cross-team work |
| Scope grows by | The difficulty of the systems you own | The size of the team you lead |
Kinds of hardware
Hardware is a wide field. Most people specialize in one area over time, and the day-to-day work looks different in each. Here are the main tracks and what they cover.
Hardware jobs: common questions
What does a hardware engineer do?
A hardware engineer designs, builds, and tests the physical parts of a system, then does the bring-up that makes them actually work. The exact work depends on the discipline: electrical engineers design boards and circuits, mechanical engineers design the structure and enclosures, embedded engineers write the firmware, and silicon engineers design the chips. Much of the craft is debugging real hardware in the lab, across the line where hardware meets software.
How do I become a hardware engineer?
Most hardware engineers come through an engineering degree, usually electrical, mechanical, computer, or aerospace, because the fundamentals are hard to pick up on your own. Internships and real projects (a robot, a board, a rocket team) matter a lot for a first role. Unlike software, the field leans more on formal training, though a strong portfolio of built hardware still carries real weight.
What is the hardware career path?
The ladder runs inside a discipline: engineer, then Senior, then Staff, growing as you own harder subsystems and bring-up. Above Staff it forks. You can stay the deepest technical person as a Senior Staff or Principal engineer, owning the hardest design calls, or lead people as an Engineering Manager, Director, and VP. Titles usually name the discipline (electrical, mechanical, firmware) rather than a generic hardware term.
Which skills and tools should I learn?
It depends on the discipline. Electrical leans on PCB design, signal integrity, and EDA tools like Altium or Cadence. Mechanical leans on CAD tools like SolidWorks plus DFM and thermal work. Embedded means C, C++, and RTOS work; silicon means Verilog or VHDL and verification. Across all of them, comfort in the lab with an oscilloscope and a logic analyzer is what turns a design into a working part.
Do you need a degree for hardware engineering?
Usually yes, more than in software. The physics and math behind circuits, mechanics, and chips are hard to learn without formal training, so most roles want an engineering degree in a relevant discipline. Some embedded and test roles are more open to a strong self-taught background, but the deep electrical, mechanical, and silicon roles almost always expect the degree.
How much do hardware engineers make?
Pay ranges by discipline, level, and company. In the US, a mid-level hardware engineer commonly lands in the range shown on this page, staff and principal roles go higher, and total compensation at well-funded hardware companies includes equity. Silicon and specialized RF or embedded roles often pay a premium. The salary bands above are illustrative; the roles listed here are real open postings.
Explore other roles
Browse open roles in other functions across tech, startup, and AI companies.
The people who design, build, and run the software.
Find the buyers, run the deals, and grow revenue.
Turn raw data into models, metrics, and decisions.
Keep the company running and the trains on time.
Decide what to build and why, then get it shipped.
Get the right people to hear about the product.
Hardware jobs by location
View all locations →See where hardware roles are concentrated, by state and city.
San Francisco, Los Angeles, Costa Mesa hiring.
New York, New York City, Brooklyn hiring.
London, Bristol, Manchester hiring.