|
Thank you everyone, this has been very interesting, let me clarify what a Solutions Engineer is, because it's not really what you'd expect a "traditional" engineer to be... Solutions Engineers are also known as Sales Engineers, the title is largely interchangeable, my official title right now is Solutions Engineer, but I've been called "Sales Engineer", "Post Sales Engineer", "Pre Sales Engineer" etc... I am not classically trained as an Engineer, I have a degree in Information Systems and Technology, and most my peers that do the same thing have similar degrees. Really, I am the technical advisor to Sales and the one that drives product demonstration, product integration, product requirements gathering, product development communications, etc... From my personal assessment, my job is 60% selling and 40% technical. Solutions Engineering positions are usually also commissioned, in my case, about 15% of my annual earnings are based on how well the company does in it's goals (industry standard is closer to 20%, verified by doing research, asking peers at other companies, etc...). Now, some of the things I am responsible for are very technical. Currently working in a small high tech software company, I am the operating system engineering person. If our product needs a modification to the operating system it runs on (we sell an appliance based solution, so everything is vendor controlled, similar to Cisco, you can't install our product on just any hardware/operating system, it ships as a unified solution), I am the one that does the research, makes the changes, tests them, etc... all while doing the "normal" duties of my position. I hold a lot of the "keys" to the product, which is both rewarding and stressful at times. I hope this sheds some light on what this position really is, because a lot of folks I talk to outside of work don't really understand it. That being said, I've only had a few years out of college, however, I am also not a traditional college student. I've worked the past 10 years, in and outside the US, and slowly completed my degree because I was focused on not going into debt for it, while at the same time consistently progressing in my career. Well, that's with exception of my internships, they where required by my degree program, but really a step back from the jobs I've had before and after. It's been very hard making employers understand that just because I've only graduated recently, I do have the same experience that someone would have that had graduated 10 years ago. It usually gets easier during interviews, because I am very much a matter of fact kind of person, I will tell you what I've done and where I've been, but I think my resume has hindered me in getting past those gatekeepers.
At any rate, I don't want to rant or justify, but what I hope to do is show if this works or not. I will certainly update this as results come along, it's an experiment to me.
|