Transition from IT Pro to Sales Engineer: How?
-
A technical salesperson is a sales engineer and a salesperson combined. Generally you get a little less of each as it is extremely hard for one person to be really great at both. But it is easier having it all in one because you deal with one person rather than having the obvious "one person pushing a product that they don't understand" and the other "person who can't make a sale answering the actual questions."
@bsouder is a technical salesperson. He can do IT work and he does sales. He doesn't use a sales engineer.
-
Sales Engineer is not a normal title. The standard industry title is Presales Engineer. It is a technical resource that is only available as part of the sales process. Not a technical resource that you have access to after a sale is made.
-
It's ok, if @ajstringham ever tries to sell me a product I can just search a few IT forums and find out what he *really *thinks of it
-
@Carnival-Boy said:
It's ok, if @ajstringham ever tries to sell me a product I can just search a few IT forums and find out what he *really *thinks of it
Yes, he is probably a bad choice for a customer facing position as he tends to be rather vocal about what he does or doesn't like in products. That's a good thing, until you want to be in sales and companies care a lot about whether you can tow the company line. Being in sales means you are the face of a company and have to maintain the facade at all times.
-
@scottalanmiller said:
@Carnival-Boy said:
It's ok, if @ajstringham ever tries to sell me a product I can just search a few IT forums and find out what he *really *thinks of it
Yes, he is probably a bad choice for a customer facing position as he tends to be rather vocal about what he does or doesn't like in products. That's a good thing, until you want to be in sales and companies care a lot about whether you can tow the company line. Being in sales means you are the face of a company and have to maintain the facade at all times.
I refuse to maintain a facade, or lie. If I don't like something, I will say so. I would never work sales for a product I didn't believe in. I'll support something I don't like, and I won't tell the customer who has already purchased it that I don't like it. However, I would never be able to work sales for my current employer. I couldn't bring myself to try and sell it.
-
I think a sales engineer is more of a "fellow" type job and isn't something you can set out to do per-se, but that's very limited knowledge.
Do you enjoy sales? I think maybe testing the waters for 6mos before you set your heart on something might be a safe bet. I always steer clear of anything commission-based, but you may really like it.
-
@ajstringham said:
I refuse to maintain a facade, or lie. If I don't like something, I will say so. I would never work sales for a product I didn't believe in. I'll support something I don't like, and I won't tell the customer who has already purchased it that I don't like it. However, I would never be able to work sales for my current employer. I couldn't bring myself to try and sell it.
That's highly admirable and a great personality trait. It does not, however, point you down the path of sales. Sales, as you know from Staples, means selling what you are told to sell and not what is good for the customer. Even when you work for a company you believe in their current sales initiatives might not align with your values. You have to push the products they want you to push whether to support a failed product line, empty old stock, get interest going in a new line, etc. You might believe in it, you might hate it, you'll not get to pick and choose ahead of time.
-
@MattKing said:
I think a sales engineer is more of a "fellow" type job and isn't something you can set out to do per-se, but that's very limited knowledge.
As a "fellow", I don't think that they are that close typically. But maybe. But I totally agree that it isn't something that you set out to do necessarily. It's a career that you fall into, not one that you target.
-
@scottalanmiller said:
@MattKing said:
I think a sales engineer is more of a "fellow" type job and isn't something you can set out to do per-se, but that's very limited knowledge.
As a "fellow", I don't think that they are that close typically. But maybe. But I totally agree that it isn't something that you set out to do necessarily. It's a career that you fall into, not one that you target.
Oh of course, it was more just relating to the "falling into" job type, and not so much as where they relate on the totem pole.
-
@scottalanmiller said:
@ajstringham said:
I refuse to maintain a facade, or lie. If I don't like something, I will say so. I would never work sales for a product I didn't believe in. I'll support something I don't like, and I won't tell the customer who has already purchased it that I don't like it. However, I would never be able to work sales for my current employer. I couldn't bring myself to try and sell it.
That's highly admirable and a great personality trait. It does not, however, point you down the path of sales. Sales, as you know from Staples, means selling what you are told to sell and not what is good for the customer. Even when you work for a company you believe in their current sales initiatives might not align with your values. You have to push the products they want you to push whether to support a failed product line, empty old stock, get interest going in a new line, etc. You might believe in it, you might hate it, you'll not get to pick and choose ahead of time.
Staples used to try to tell me what to sell. They VERY quickly gave up on that when they realized letting me do things my way resulted in happier customers and better sales. That being said, if we had clearance stock, or stuff we needed to move, I would alter my approach, on the basis that it still fit the customer's needs well. If it was a matter of preference, and Y was just as good as X, and I just normally preferred X, I'd push Y. But I never just sold something because we were out to meet a goal or were instructed to. When you put the customer first, and focus on meeting their needs over the goals of the company, you usually walk away meeting both. If you strive to fall into line perfectly with unrealistic corporate expectations, then you're going to lose both the sale for the company and the satisfaction of the customer.
-
It's my goal to get to sales engineer. Now for what that will be, I don't know yet. But based on this thread, I'm realizing I'm not going to get there anytime in the next couple years, or even likely the next decade. For now, I work the helpdesk and work my way up the chain of support to get to engineer. I need to get that half nailed down first, and the sales portion will follow.
-
One of the reasons that I like working for a non-reseller MSP is that I get to play the "sales engineer"-like role but I do so as a representative of the customer, not of the vendor. I love Dell's R720xd server, for example. But their VRTX is a joke, at least for use by the SMB market. If I was a Dell SE, I would be required to push the VRTX and to potentially push it even when it makes zero sense. I'd be required to sell the R720xd in conjunction with a silly 3-2-1 architecture.
But because I am with a non-reseller MSP that works for the customer, I get to recommend the R720xd when it makes sense and I get to warn about the VRTX to protect the customer. No matter what initiative Dell has going on, I am free to do the best thing for the customer. If Dell doesn't bring out a good server in the future, I have no reason to recommend any Dell at all.
(I'm using Dell as an example here because of the huge dynamic in how much the R720xd is great and the VRTX doesn't make sense for normal businesses and carries crazy risk that no one likes to talk about. I don't believe in recommending server vendors at all, no value in it. Recommend a category of them and specific models from each but let customers pick the vendor of choice.)
I get to do all of the sales engineering type stuff that SEs do but without the compromise to integrity necessary to be an actual sales engineer.
-
@MattKing said:
Oh of course, it was more just relating to the "falling into" job type, and not so much as where they relate on the totem pole.
Oh gotcha, yes that makes sense.
-
@ajstringham said:
Staples used to try to tell me what to sell. They VERY quickly gave up on that when they realized letting me do things my way resulted in happier customers and better sales.
I remember us having conversations where you were forced to sell completely awful, overly expensive solutions because it was what Staples stocked when there were cheap, reliable solutions that they could have picked up from Amazon that were far better.
-
@scottalanmiller said:
@ajstringham said:
Staples used to try to tell me what to sell. They VERY quickly gave up on that when they realized letting me do things my way resulted in happier customers and better sales.
I remember us having conversations where you were forced to sell completely awful, overly expensive solutions because it was what Staples stocked when there were cheap, reliable solutions that they could have picked up from Amazon that were far better.
There were times I told people to pick stuff up on Amazon, but the compromise I won't make is in terms of a quality product. If Staples sold product X for $50, and it was $25 on Amazon, I didn't tell people that. However, if Staples said product X is the greatest thing since sliced bread and I have to sell it, but I knew it was crap, that was different. There were plenty of times I told people Amazon had product X cheaper and that we would price match it for them. They didn't like that, but I did it all the time. I always sought to get people the best products at the best prices. Staples said sell product X? If I didn't think it was a good product, I couldn't have cared less. I wouldn't sell it, and I made sure all my techs didn't sell it. Some didn't have my knowledge, and took Staples' word at face value. But I always preserved my own technical integrity. As my knowledge grew, that definition changed, which is inevitable.
-
The example you're thinking of is Sophos, in their actual endpoint protection, for $90/PC/year. While I agree that the price is steep, think of the alternative. Sure, you can get Vipre for $15/PC/year. Webroot EP in a 5-user license is $25/PC/year. However, then the customer has to manage all the backend stuff. The $90/PC/year was in a small part for the product, but mostly for the management of the console. Your average home user pays a premium for business-level protection, without requiring any of the knowledge to manage it themselves. I still stand by that being a good value, albeit not the cheapest solution.
-
@scottalanmiller said:
I get to do all of the sales engineering type stuff that SEs do but without the compromise to integrity necessary to be an actual sales engineer.
That has to be about one of the best jobs in the world! and yet you still have a day (or is it night) on wallstreet?
-
@ajstringham said:
The example you're thinking of is Sophos, in their actual endpoint protection, for $90/PC/year. While I agree that the price is steep, think of the alternative. Sure, you can get Vipre for $15/PC/year. Webroot EP in a 5-user license is $25/PC/year. However, then the customer has to manage all the backend stuff. The $90/PC/year was in a small part for the product, but mostly for the management of the console. Your average home user pays a premium for business-level protection, without requiring any of the knowledge to manage it themselves. I still stand by that being a good value, albeit not the cheapest solution.
No, the example I was thinking of is when you had a farmer bury a cheap switch in the yard and run CAT5 and power underground between consumer routers rather than skipping all of that and saving a few hundred dollars and running fiber. We talked about it and how the farmer was getting screwed because Staples didn't sell the appropriate gear but he trusted you so you were able to sell him a ridiculous solution that I'm sure has shorted out and caused a fire by now. He lost money, wasted effort and took on actually electrical risk all to end up with an unstable, pointless solution when doing the right thing was super cheap and simple (and safe.)
-
@Dashrender said:
That has to be about one of the best jobs in the world! and yet you still have a day (or is it night) on wallstreet?
I'm really a solutions architect. That's the broad category that lets me do those roles internally.
-
@scottalanmiller said:
@ajstringham said:
The example you're thinking of is Sophos, in their actual endpoint protection, for $90/PC/year. While I agree that the price is steep, think of the alternative. Sure, you can get Vipre for $15/PC/year. Webroot EP in a 5-user license is $25/PC/year. However, then the customer has to manage all the backend stuff. The $90/PC/year was in a small part for the product, but mostly for the management of the console. Your average home user pays a premium for business-level protection, without requiring any of the knowledge to manage it themselves. I still stand by that being a good value, albeit not the cheapest solution.
No, the example I was thinking of is when you had a farmer bury a cheap switch in the yard and run CAT5 and power underground between consumer routers rather than skipping all of that and saving a few hundred dollars and running fiber. We talked about it and how the farmer was getting screwed because Staples didn't sell the appropriate gear but he trusted you so you were able to sell him a ridiculous solution that I'm sure has shorted out and caused a fire by now. He lost money, wasted effort and took on actually electrical risk all to end up with an unstable, pointless solution when doing the right thing was super cheap and simple (and safe.)
The solution was sound and worked. Fiber would have been an option, but you are right, it's nothing I would have been able to implement. However, when you talk about time, materials, and labor, I don't think it would have been cheaper, or easier.
