EXCELLENT idea! I wish that had been the case before I went to Hynix. The engineer who interviewed me was very smart, but he didnt know shit about the day-to-day job of the technicians.
And they may not have permission to find out what other departments do. I'm regularly instructed that I need to make my designs easier for other departments to interface with. It needs to be simple so that sales can understand it and sell it. It needs to be easy for a customer with little technical expertise to use the product. It needs to assemble quickly to keep labor costs low. It needs to minimize material costs. It needs to look good for the marketing department. It needs to survive shipping, and exposure to the elements.
However, I'm not given time to simply go work in the shop or see what's going on out there, or to see what sales does over the course of a few days, to learn what their jobs really entail. The best I might get is an hour or two out of a year. It's training, which means I'm spending time away from my desk not doing engineering sorts of things. And it's training that won't produce a return in a way that accounting can easily measure, so it doesn't have any $$$ way to justify it.
So I'm left to use my imagination a lot of the time, which tends to be more of an ideal and orderly place than the rest of the world generally is. (And often my idea of "extremely simplistic" is
significantly more complex than a lot of people can handle. :\)
Or selecting the engineer to sit in on the interview may have gone like this:
"Hey we're interviewing some candidates, and I want you to sit in on the interview and help out."
- "What do you want me to do? Ask questions, listen in, or what? I've never done interviewing before."
"Just ask them about whatever the heck it is you do. You know, technical...things."
- "...yeah."