While doing research for each of my 6 books, I’ve read many career books for software engineers.
I’ve noticed it again and again: If you swap the word “engineer” for “designer,” 99 % of the advice still applies. In career planning, collaboration, and politics, designers aren't unique in most of their struggles.
However, there are ~10x more engineers than designers worldwide, so there are naturally more (and better) resources for them.
So, to escape the daily "8 tips for your portfolio" posts, follow engineering, business, and product people. Read books and subscribe to newsletters by non-designers (e.g.
, , , Lara Hogan, Kate Huston).Extra benefits of this approach:
Beyond a certain point in your career, the ROI of learning about engineering/business/else is higher than doubling down on design.
Some aspects of the design role were taken from other roles (e.g. the dual career track from engineering), so you can see what's coming before it reaches design.
Example for management
If you're considering becoming a design manager, the best materials to read are books for software engineering managers. For example:
Become an Effective Software Engineering Manager
Engineering Management for the Rest of Us
The Manager's Path: A Guide for Tech Leaders Navigating Growth and Change
To grow your design career, check out my books for progression to senior and beyond.
This is a great point Artiom! I try to do that myself as a writer as well. I like reading books about designing and business and other skills that can benefit me as I move throughout my career. It’s also super crucial to have a backup plan when things don’t go as expected.💪❤️
Thanks for the mention!
I agree with your take, there's something called skill stacking. The strategic combination of multiple skills, rather than specializing in just one, creates a more valuable skillset