Hardware development engineer skills for your resume and career

One skill that is timeless is the ability to communicate effectively, such as taking a complex design process and distilling it into intuitive slides or reports that lend themselves for senior managers to process in order to come to a decision. An engineer who has that ability will always have some tools in his/her toolbox that makes that individual attractive to a company and to the local technical ecosystem, thus a ripe target for headhunters who willing to champion them to companies looking for top talent. Moreover, speaking and writing well also comes with a vital component of diplomacy, especially in the context of increasingly distributed company workforce: the ability not just to get on with colleagues from different parts of the world, increasingly heterogeneous in terms of gender and possibly sexual preference, but embrace them for who they are. This is often maps to opportunities to travel, as some collaborations lead to meetings face to face, post-covid.

This embrace of heterogeneity is even more relevant in that technical problems being solved are increasingly multi-disciplinary, so that an engineer may need to interact with biologists, physicians, clothing or furniture designers, mathematicians, lawyers, and so on: in my own case, I have to wear a multitude of different hats, while recognizing someone who is a perfect fit for one of those hats when I meet that individual, and making the most of that opportunity to build a truly competent team. Engineers must be able to hold a meaningful, respectful conversation with any of these counterparts, not just discuss code or circuit design. I would advocate that they spend time reading, to maintain their vocabulary and stay abreast of the world around them.

Another one that I advocate is the ability to tap into a revolution that has occurred in parallel with the advent of Internet and cellular technologies, these past 30+ years: the explosion of open-source software tools. I am a committed proponent of open source, as a former contributor to them while previously employed at Kitware (a pioneer in this area, behind VTK, ITK, CMake, and myriad others). I see job ads in Indeed.com that specifically ask for the ability to work with these tools, since they save work and make it possible to produce a prototype in much less time than developing it completely in-house. This ability does not just presuppose the ability to program at a competent level, but other abilities: the ability to track bugs that not be in the calling program, but in the open-source software library itself, the willingness to get answers in the community of developers, the eye for details that extends to graphical processor units that result in accelerations an order of magnitude or better, and so on. These go way beyond writing a self-contained algorithm. Hardware designers may also have similar tools, based on broad standards, Arduino, and the prevalence of 3D printers that make it possible to physically replicate digital models.

Finally, a vital skill is the willingness and ability to keep learning, while embracing revolutions that take place at breathtaking pace. The latest one is the reliance on deep neural networks (DNNs) to synthesize algorithms that can learn and adapt to their data, with much faster performances than feasible with the previous algorithms that DNNs have replaced. The point to make here is not to embrace neural networks in a proximal sense, but that we cannot anticipate what will come next, downstream of DNNs. Graduates of 2021 have to be willing to keep their curiosity and work ethic enough to be responsive to the next wave of technologies, and embrace them for the opportunities that they represent.