Difference between these architecture roles?

Hey,

Im just wondering if there is a big difference between a Pre-sales solution architect and a solution architect? Both are network solution based. Am i right in thinking that a PS-SA aids the sales people and answers technical questions from customers, presents solutions, writes documentation etc. And a solution architect typically designs the solutions?! Does a PS-SA do any designs at all?

Reason i asked is because a job opportunity has become available that is a PS-SA role. I am currently in a network architect role (design only, no hands on). I enjoy the design side albeit i miss the hands on at times. i would love my CCIE R&S to give you a sense of my goals. I know architect roles generally move away from the hands on side but does the Pre-sales architect roles move one step further away?

Long term, i want to be a good network architect with my number. I am currently in my first role as a Network Architect in a 6 months contract. Would i be harming myself if i went into a PS-SA based role? previously i thought these were the same kind of roles but one with a bit more customer facing. However, the job description doesnt mention any design aspects.

Help would be much appreciated

Find more posts tagged with

Comments

down77

Just my 0.02 but a Pre-Sales Solutions Architect (PSSA) is a pseudo sales rep as well as an architect, but focused on the SALES side. Their job is to discuss and highlight a solution's features and benefits, as well as to advise on how it will fit in to a given scenario. An example of this would be if a client is currently on a "legacy" Cat 6500 Non-E infrastructure and is asking for recommendations on a migration approach to next generation technologies and technology refresh. The PSSA would accompany the sales rep to the meeting, review the organization's existing technology selection, and make recommendations on a technology selection and migration approach as well as to be a subject matter expert on the design and features of the newer technologies. Expect a lot of time researching the latest and greatest technology features, and then diagramming in visio and white boarding potential designs and solutions.

A Solutions Architect (SA) is more focused on the Design on the service delivery/service transition side of the house. While they may still have some pre-sales duties, it is much less than the PSSA. The SA would be focused more on the technical design, implementation, and approach rather than the product selection. They are the ones who help deliver the big picture from an end to end technical approach and ensure it meets the business and functional requirements. An example would be discussing and delivering technical solutions regarding protocol migrations, complex technology integrations (such as designing an OTV solution, WAN compression strategy, Complex firewall architecture, etc), performance best practices, etc.

Both roles follow the Design function of the PPDIOO model.

jibbajabba

Our Pre-Sales architects dealing with the technical side during a sale, designing, putting tender together and so on. Then the sales monkey comes along and pulls the trigger.

Our solutions architects aren't involved in sales at all. Who requested a certain solution doesn't matter to him. Can be a customer or internal departments.

Based on down77 explanation each company seems to deal with this differently

down77

jibbajabba wrote: »

Based on down77 explanation each company seems to deal with this differently

Mine was based on one of the big tech organizations (Cisco, IBM, NetApp etc). But you are 100% correct, each company treats it different.

nel

jibbajabba wrote: »

Our Pre-Sales architects dealing with the technical side during a sale, designing, putting tender together and so on. Then the sales monkey comes along and pulls the trigger.

Our solutions architects aren't involved in sales at all. Who requested a certain solution doesn't matter to him. Can be a customer or internal departments.

Based on down77 explanation each company seems to deal with this differently

This is what i have found previously. A architect get the business requirements, turns them into technical requirements, makes a design, then it goes to implementation/engineering. Obviously, its has to be accepted by the customer etc but you get the jist.

Kinda sounds like a PSSA is a technical resource for a sales guy to answer the techie questions.

I can imagine many companies interchange compress these roles into one like the OP said. I guess it wont harm going in to speak to them and see what the situation is.

ColbyG

Pre-sales is more about product/solution knowledge. A customer gives you some requirements and you do a high-level design with the most relevant products. You need to know portfolios very, very well - all the limitations, what works together, etc.

sieff

Generally a (pre-sales) Solutions Architect role gets a combination of a base salary and a commission. Closing a big deal for an acct mgr should be a nice hunk of change.

nel

thanks for the input.

So i guess to summarise using the PSSA/SA/Engineer structure, a PSSA would only go as so far as the High level design and then pass it to the SA for a low level design, who then passes it to engineering for implementation?

It sounds like a good opportunity if given the chance but I'll have to speak to them further to see how far away from the technical side it is or whether it will encompass both the PSSA/SA roles.