Re: In a nutshell
>My experience, as a (non-HP) developer, is the reverse. Pre-sales really know the technical details of the product and can help the customer create a good solution, often with the developer's' help. It's the post-sales guys who come in to do the install and setup and screw that up, usually due to an inability to read the documentation. Then they come crying for help to the developers.
As with all things, it depends on the person. I've worked in both roles and have seen pre-sales create a "solution" which is never going to work, because they've fundamentally not understood what the product is supposed to do, or misconfigured it, e.g. not configuring hot spares or allowing for parity in a storage system, or forgetting licences or something like that. It happens.
And in post-sales, you're right; sometimes the guy who's supposed to be configuring it isn't an expert and doesn't know what he's doing. So he'll make fundamental errors that will come back and bite later.
It's all down to experience foremost, and education. I've been in the situation (when working for a large company, not HP, the other one) and my boss has said "I want you to be the expert in product X". "Great, so I can get some training?" "No, there's no budget (even though the customer is paying 6- or 7- figure sums). You'll have to work it out yourself".
Then there's the fact that when companies like this reinvent themselves, they sack all of those with the skills because they cost more.