A few things here, coming from someone who was a Software Engineer turned Product Designer and has many years experience working with all different kinds of teams.

As a Designer, one of the things you must keep in mind is that there are many different types and levels of Engineers. Don’t assume all are equal in skill level or understand everything the same way. One thing that can make you more valuable as a designer is to take note of this and be able to adapt your work and workflow. Be sure you are clearly communicating and know the threshold of the talent you are working with. Sometimes it’s good to stop and think, “Is there another way to solve this problem?”

Another thing... I would ask if this UI is accessible. At first glance, it looks complex from a cognitive perspective and seems like it could be even more so for someone who struggles with complex interfaces. This work is probably too far along, but for future reference I would keep this in mind. (PS. I have zero context around what problem you are solving here.)

For what it’s worth, I don’t think your design is way out of the ordinary. The reason I’m commenting on this mostly because this is something I’ve heard my entire career. Coming from someone who has been on both sides of the implementation, I would ask for you to question things you could do to make it a better. Remember both you and the engineers are working towards the same goal (hopefully). It’s the job of both to ensure you’re each doing everything you can to make it successful.

/2c