Manager, Firmware Engineering

About the company

FORT Robotics provides a control platform fusing functional safety and cybersecurity to enable secure real-time communication and dynamic safety controls for collaborative autonomous industrial robots in warehousing and manufacturing.

About this role

<div class="content-intro"><p></p> <p></p> <p>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.</p> <p>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.</p> <p>Additionally, FORT's Safe Remote Control enables operators to manage heavy machinery remotely, reducing the risk of accidents and improving visibility.</p> <p>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.</p> <p></p> <p></p></div><p><strong>This role is based in Philadelphia and works on a hybrid schedule, with a minimum of three days a week in the office.</strong></p> <p>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.</p> <h2><strong>What will you own</strong></h2> <p><strong>The hands-on half.</strong> You contribute directly to the embedded stack, much of it filling the gaps around the team, so the work keeps moving:</p> <ul> <li>Write and review production C/C++ for safety-critical embedded devices, taking well-scoped components through implementation, test, and release.</li> <li>Implement real-time firmware for RTOS targets (Zephyr/FreeRTOS) and bare-metal environments, along with Embedded Linux user-space applications.</li> <li>Bring up new hardware, debug hard problems with JTAG, GDB, oscilloscopes, and logic analyzers, and tune performance on constrained targets.</li> <li>Maintain and improve the firmware CI/CD pipelines (GitLab), the test automation behind them, and hardware-in-the-loop coverage.</li> <li>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.</li> </ul> <p><strong>The leadership half.</strong> You own the group and the way it works:</p> <ul> <li>Agile Scrum process end-to-end: backlog grooming, cadence and ceremonies, estimation, and forecasting.</li> <li>Technical health and feasibility of the backlog, advocate for platform and technical-debt work, and decline commitments that the team cannot feasibly deliver.</li> <li>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.</li> <li>Workforce management: hiring, performance, and career conversations, team structure, and workload and burnout.</li> <li>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.</li> </ul> <h2><strong>What you will be measured on</strong></h2> <p>Delivery predictability, quality, goal achievement, and retention, plus improvement over time in five team metrics: planning accuracy, estimation accuracy, velocity, defect escapes, and engagement.</p> <h2><strong>What we are looking for</strong></h2> <ul> <li>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.</li> <li>Technical judgment strong enough to assess feasibility, estimation, and risk, and to shape or push back on commitments.</li> <li>Solid management capability across performance, development, and capacity planning, and comfort owning a team end-to-end with a broad scope and matching autonomy.</li> <li>The instinct to delegate real authority and build systems rather than becoming the bottleneck.</li> <li>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.</li> <li>Nice to have: a background in functional safety or another regulated industry (medical, automotive, aerospace, industrial).</li> </ul> <p>&nbsp;</p> <p>&nbsp;</p>