| > I was repeatedly asked if an engineer was around to explain the product before I had a chance to say more than hello. > let's focus on the other assumption: that because a person has a non-technical role, she is fundamentally incapable of assessing whether she is able to answer your question. > While we’re at it, I’d like to dispel the notion that people in non-technical roles don’t have technical skills. From the VBScript and complex spreadsheet wrangling required to perform analysis of key organizational metrics to mastery of numerous different specialized softwares and systems in order to perform basic functions of the job ranging from accounting to people operations, non-technical employees must have a bevy of technical skills at the ready every single day. It's difficult to recognize what you don't know. As an engineer, I feel like I didn't understand jack a year ago. A year from now, I'll feel the same way about my current level of understanding & skill. Between now and then, I'll speak with confidence about topics I think I understand but probably don't fully grok. Earlier in my career, I was "semi-technical" with more [technical] experience than the OP. Looking back, I really didn't understand the product to the extent I thought I did. A little knowledge can be dangerous. YMMV. edit : if you down voted, care to explain? |