1

Firmware Engineering Jobs in Philadelphia, PA (NOW HIRING)

This entry-level Firmware Engineer role supports the development, debugging, testing, and ... Bachelor's degree in computer engineering, Electrical Engineering, Computer Science, or a closely ...

Senior Firmware Engineer

Audubon, PA ยท On-site

$120K - $159K/yr

The Senior Firmware Engineer will develop and deliver reliable, compliant, and high-quality ... S. in Computer Engineering, Electrical Engineering, or related field. * Minimum 4 years of ...

Senior Firmware Engineer

Audubon, PA ยท On-site

$120K - $159K/yr

The Senior Firmware Engineer will develop and deliver reliable, compliant, and high-quality ... S. in Computer Engineering, Electrical Engineering, or related field. * Minimum 4 years of ...

Bachelor's Degree in electrical engineering with 3-5 years of electrical engineering experience ... Experience with writing Firmware * Experience with circuit modelling software such as PSpice or ...

Work with optical, hardware and test engineering teams to continuously improve firmware performance, execution efficiency, and development processes. Teamwork and supporting - 20% * Coaching junior ...

Work with optical, hardware and test engineering teams to continuously improve firmware performance, execution efficiency, and development processes. Teamwork and supporting - 20% * Coaching junior ...

Principal Firmware Engineer

Horsham, PA ยท On-site

$120 - $150/hr

Work with optical, hardware and test engineering teams to continuously improve firmware performance, execution efficiency, and development processes. Teamwork and supporting -20% * Coaching junior ...

next page

Showing results 1-20

Firmware Engineering information

See Philadelphia, PA salary details

$68.3K

$152.5K

$186.7K

How much do firmware engineering jobs pay per year?

As of Aug 24, 2026, the average yearly pay for firmware engineering in Philadelphia, PA is $152,460.00, according to ZipRecruiter salary data. Most workers in this role earn between $130,200.00 and $186,700.00 per year, depending on experience, location, and employer.

What is firmware engineering?

Firmware engineering is the process of designing, developing, testing, and maintaining the low-level software that controls and interacts with hardware devices. Firmware sits between the hardware and higher-level software, enabling the hardware to function correctly and efficiently. Firmware engineers often work with embedded systems, microcontrollers, and specialized hardware across industries such as consumer electronics, automotive, and industrial equipment. Their work ensures that devices operate reliably and can be updated or improved over time.

How does a firmware engineer typically collaborate with hardware and software teams during product development?

Firmware Engineers play a central role in bridging the gap between hardware and software teams. They often work closely with hardware engineers to understand device specifications and constraints, while also collaborating with software developers to ensure seamless integration and functionality. Regular cross-functional meetings, code reviews, and hardware testing sessions are common practices to address issues early and optimize product performance. Effective communication and problem-solving skills are essential, as firmware must often be adapted to accommodate both hardware changes and evolving software requirements.

What are the key skills and qualifications needed to thrive as a firmware engineer, and why are they important?

To thrive as a Firmware Engineer, you need a strong background in embedded systems, C/C++ programming, and electronics, usually supported by a degree in computer engineering or a related field. Experience with microcontroller architectures, RTOS, hardware debugging tools, and version control systems like Git is typically required. Problem-solving ability, attention to detail, and effective teamwork are standout soft skills in this role. These competencies ensure reliable, efficient firmware development and seamless integration with hardware, which is critical for product functionality and performance.

What is the difference between Firmware Engineering vs Embedded Systems Engineering?

AspectFirmware EngineeringEmbedded Systems Engineering
CredentialsBachelor's in Electrical, Computer Engineering, or related; certifications like Certified Embedded Systems ProfessionalBachelor's or higher in Electrical, Computer Engineering, or related; similar certifications
Work EnvironmentDeveloping low-level code for hardware devices, often in embedded environmentsDesigning and integrating hardware and software for embedded systems
Industry UsageConsumer electronics, IoT devices, automotive, aerospaceMedical devices, industrial automation, consumer electronics

Firmware Engineering focuses on writing low-level code that directly interacts with hardware components, often in resource-constrained environments. Embedded Systems Engineering encompasses a broader scope, including designing entire embedded systems, integrating hardware and software, and system-level development. While overlapping, Firmware Engineers typically specialize in firmware development, whereas Embedded Systems Engineers may handle system architecture and integration tasks.

Are firmware engineers in demand?

Firmware engineers are in high demand due to the growth of embedded systems in industries such as consumer electronics, automotive, and healthcare. They often require skills in C/C++, debugging, and working with hardware, and job opportunities are expected to grow as technology advances. Certifications and experience with real-time operating systems can enhance employability.

How much money do firmware engineers make?

Firmware engineers typically earn a median annual salary ranging from $80,000 to $120,000, depending on experience, location, and industry. Senior roles or those with specialized skills in embedded systems and real-time operating systems can earn higher salaries, often exceeding $130,000 annually.

What do you do as a firmware engineer?

A firmware engineer designs, develops, and tests low-level software that controls hardware devices such as microcontrollers and embedded systems. They often work with programming languages like C or C++, use debugging tools, and ensure the firmware operates reliably within hardware constraints. This role requires knowledge of hardware architecture and real-time operating systems.
Infographic showing various Firmware Engineering job openings in Philadelphia, PA as of August 2026, with employment types broken down into 90% Full Time, 7% Part Time, 2% Contract, and 1% Nights. Highlights an 85% Physical, 4% Hybrid, and 11% Remote job distribution, with an average salary of $152,460 per year, or $73.3 per hour.

Manager, Firmware Engineering

FORT Robotics

Philadelphia, PA โ€ข Hybrid

Full-time

Posted 24 days ago


Job description

In today's dynamic worksites, seamless collaboration between people and machines is essential. FORT's platform ensures safe, secure, and dynamic control that surpasses legacy systems and next-generation AI capabilities.

While autonomous machines offer significant advantages, they also introduce new safety challenges. FORT addresses these concerns by providing solutions such as the Wireless E-Stop, which allows operators to instantly stop any machine from a safe distance, enhancing safety during emergencies.

Additionally, FORT's Safe Remote Control enables operators to manage heavy machinery remotely, reducing the risk of accidents and improving visibility.

By ensuring communications integrity across any network, FORT empowers customers to protect their most valuable assets—people, data, and machines—ensuring they remain safe and secure.

This role is based in Philadelphia and works on a hybrid schedule, with a minimum of three days a week in the office.

The Firmware Engineering Manager owns FORT's firmware group end-to-end (its people, delivery, and technical health) while still building firmware directly. About half your time is hands-on embedded engineering, and half is leading through the team. You own the team's development process directly, supported by the Program Management and Systems Engineering functions. You work in three directions: down and in on your team's health and performance, up and out with a real engineering voice into Product and Program planning, and across to keep firmware coherent with the peer groups (cloud, hardware, systems, safety). Senior engineers on the team own the firmware architecture, and you make sure they have the direction, the standards, and the authority to do it well. Firmware sits closest to the safety layer FORT sells, so both the technical bar and the quality process have to be strong enough to carry that level of rigor while the team still delivers at pace.

What will you own

The hands-on half. You contribute directly to the embedded stack, much of it filling the gaps around the team, so the work keeps moving:

  • Write and review production C/C++ for safety-critical embedded devices, taking well-scoped components through implementation, test, and release.
  • Implement real-time firmware for RTOS targets (Zephyr/FreeRTOS) and bare-metal environments, along with Embedded Linux user-space applications.
  • Bring up new hardware, debug hard problems with JTAG, GDB, oscilloscopes, and logic analyzers, and tune performance on constrained targets.
  • Maintain and improve the firmware CI/CD pipelines (GitLab), the test automation behind them, and hardware-in-the-loop coverage.
  • Pick up the work that would otherwise sit unclaimed in a given sprint, whether that is an unfinished integration, a stubborn defect, a driver or BSP task, or a gap left by a vacancy or a competing priority.

The leadership half. You own the group and the way it works:

  • Agile Scrum process end-to-end: backlog grooming, cadence and ceremonies, estimation, and forecasting.
  • Technical health and feasibility of the backlog, advocate for platform and technical-debt work, and decline commitments that the team cannot feasibly deliver.
  • Quality process: code review, testing standards, a real definition of done, and corrective retrospectives, strong enough to carry FORT's safety-critical bar without depending on you as the personal backstop on every artifact.
  • Workforce management: hiring, performance, and career conversations, team structure, and workload and burnout.
  • Carry engineering's opinion on technical direction, sequencing, and estimation into Product and Program forums, and surface cross-team integration risks early, particularly at the firmware boundaries with hardware, cloud, and systems.
What you will be measured on

Delivery predictability, quality, goal achievement, and retention, plus improvement over time in five team metrics: planning accuracy, estimation accuracy, velocity, defect escapes, and engagement.

What we are looking for
  • Solid, current embedded expertise across C and C++, RTOS, and Embedded Linux development, including hardware bring-up, low-level debugging, standard interfaces (UART, SPI, I2C, USB, CAN), IP networking, and Python for automation, with firsthand experience owning firmware CI/CD.
  • Technical judgment strong enough to assess feasibility, estimation, and risk, and to shape or push back on commitments.
  • Solid management capability across performance, development, and capacity planning, and comfort owning a team end-to-end with a broad scope and matching autonomy.
  • The instinct to delegate real authority and build systems rather than becoming the bottleneck.
  • Typically 6+ years of embedded software development with at least 2 years leading or managing engineers, and a B.S. in Computer Engineering, Electrical Engineering, Computer Science, or equivalent experience.
  • Nice to have: a background in functional safety or another regulated industry (medical, automotive, aerospace, industrial).