Post

The Engineering Work You Don’t See

What embedded, automation, and internal tools engineers can show when the systems they build aren’t public.

A lot of software work is hard to show in a portfolio. If you build internal tools, work on embedded systems, or automate a process inside a company, the people who see the result may be the only people who can use it. Sometimes the details are confidential. The work still matters to the people who rely on it every day.

That’s why Scott Hanselman’s description of dark matter developers stuck with me. I’ve spent much of my career building software that works with hardware or supports teams inside a company. The interesting part might be how a device is tested, how an image can be built consistently, or how a problem can be diagnosed when something goes wrong.

I used to think a portfolio needed a collection of public apps to show that work. A better starting point for me is to explain the kind of problems I’ve worked on and how I think through them. I can talk about why a manual step was hard to repeat, how I approached automation, or what I checked to know a change worked. Those are things I can discuss without sharing a private codebase.

I’d like to see more portfolios that make room for this kind of engineering. Useful software shows up in many places, including some you never get to visit from a web browser.

Adapted from my original LinkedIn post. Read the original on LinkedIn

This post is licensed under CC BY 4.0 by the author.