Recently, I’ve been delving into the role of the “design engineer” and have created a map to better understand this discipline, the concepts it encompasses, and its relationship with other fields.
Thread
This is a cool idea. Have you given thought to what you might consider explicitly _outside_ the scope of design engineering?
Yes, I did. for example, design systems is almost completely in the head of a design engineer but still needs a bit collaboration with engineering that’s why the bubble slightly exceeds the scope of design engineering.
Also, certain concepts like functional constraints and tokens extend outside the user experience bubble.
ah I see. It seemed like all of the actual tasks/responsibilities sit inside of design engineering here though, or am I misreading that? Like what would be a UX task that _design engineers_ explicitly don't do? or Engineers?
I'm asking because from my experience making the transition into design engineering, I've noticed this never gets defined. As you interview from place to place, the things that companies expect you to do seems to balloon indefinitely.
Once you add up the role expectations from a few different employers, you wind up needing to be proficient at everything from UX research to full-stack development. I think it would be useful to draw an explicit line in the sand on where the expected expertise should end.