Building Software in a Hardware Company

Marissa Mocenigo

Senior Engineering Manager at Taxfix



As a software engineer, working in a hardware company has different challenges and obstacles. Longer lead times on hardware can cause delays or blockers for software development milestones, without delaying deadlines. Testing can be limited by the availability of devices. Once the hardware is manufactured, software might be the only option for adapting necessary workarounds.

Actions taken

Bring together hardware and software engineers early to brainstorm and document risks and solutions.
It’s never too early to start documenting risks that may result from hardware design or failures. There may be some cases where software can provide a simple workaround, and it helps to prioritizes potential pain points that cannot easily be solved with a software solution.

If possible, create a virtual testing platform that replicates the hardware.

Everything should eventually be tested on the actual hardware, but it may take several iterations to get a feature working properly. Many early hardware startups only have a couple, if any prototypes, available for testing and small, early hardware runs can be expensive to produce. Creating a virtual version of the hardware can unblock software development and can also reduce the need for mass testing devices.

Create resource calendars to book hardware devices.

This tip probably seems relatively trivial, but I’ve seen so many places fail to do this and struggle with who has what device where and for how long. As above, it’s important to test on the hardware but availability can be limited for many reasons. Use the company’s calendaring system to book devices similarly to booking a meeting room. If marketing needs a device to take to trade shows, they should be sure to book it in advance. If an engineer needs a device for testing, they know who to ask if all the devices are booked up, and they can plan around availability when working on a feature.

Document a common understanding of shared APIs.

This is important at any company, but it’s even more important when bridging across hardware and software. Ideally, this will allow you to parallelize tasks as much as possible. Front-end engineers, for example, can start developing features and mock up calls to the device that can then be implemented later.

Lessons learned

Working at a hardware company has some of the same challenges as working in any software startup; however, some challenges can be exacerbated by timelines, coordination, and collaboration. The focus of many of these actions is communication, and ensuring a close working relationship and good communication between hardware and software engineers is at the forefront of success.

Be notified about next articles from Marissa Mocenigo

Marissa Mocenigo

Senior Engineering Manager at Taxfix

CommunicationSoftware Development

Connect and Learn with the Best Eng Leaders

We will send you a weekly newsletter with new mentors, circles, peer groups, content, webinars,bounties and free events.


HomeCircles1-on-1 MentorshipBounties

© 2024 Plato. All rights reserved

LoginSign up