The invisible side of design engineering
Design engineering is still a bit more ambiguous than something like product design, software engineering or product management. It sits at the intersection of design and engineering, but if you ask ten different people exactly what it means to be a design engineer, you might get ten different answers.
If you were to judge by looking at social media, you might think it’s mostly about building animated eye candy components. That’s pretty far away from the truth though.
The invisible
It’s understandable that the visual side gets the most attention. It’s tangible, easy to share and easy to react to, and when done well, interactions can completely change how an experience feels. But there are other parts of design engineering that are just as important, if not more, but don’t get nearly as much attention.
Things like accessibility, responsiveness and performance. Things that are not “interesting enough” to be shared on social media. Edge cases that only show up when people actually start using your product. That’s a lot of what my day-to-day work as a design engineer actually looks like.
Why it matters
There are many factors that affect what you do day to day. At an early-stage startup you might touch almost every aspect of building a product, while someone at a large company might work in a much narrower area. And while the work might look different, a lot of the principles remain the same: we’re building things that are supposed to solve real problems and be used by all kinds of people.
As a design engineer, your responsibility is to make sure the experience is great. Sometimes that means building a beautiful animation. Sometimes it’s spending an entire afternoon fixing an accessibility issue only a few people will notice. Sometimes it’s obsessing over making the landing page load just a little faster.
It makes sense that the visible side of design engineering gets most of the attention. But a lot of what makes a great experience is invisible.