As it is almost 9 months ago since I decided to move to VMware to become a Consultant within the Professional Service Organization (PSO), I thought it is time for a short recap!
Apart from that, I’ve noticed that the PSO services are quite unknown here in Switzerland which also made it kind of difficult to find a lot of useful information about it, back then when I’ve decided to apply for my current job. Therefore, the intention of this post is not only to provide more insights in to PSO for possible candidates who may be preparing an application for a similar job, but also to explain our services to customers which might be interested in requesting our support for certain topics. But as always, please read my disclaimer first 😉
Professional Service Organization
First of all and before I’ll dive in to my current role, I’d like to briefly explain what the professional service organization, short “PSO” is, and how it interacts with other divisions within VMware.
In general, PSO can be considered as a “post-sales” organization which comes in to play mostly after a customer has bought or is already owning particular licenses or products. With different types of professionals like Consultants, Architects, Project Managers, Technical Account Managers (TAMs) and so on, PSO supports customers to leverage their existing or planned VMware infrastructure in the most efficient and valuable way.
Consultants, Architects and Project Manager are usually providing services and expertise within topic and time limited projects whereas TAMs supporting the customer typically over a longer period of time to ensure ongoing customer satisfaction even after a project has been delivered successfully. This means, PSO can be requested for very specific and limited project scopes like for instance a new deployment of a monitoring infrastructure based on vRealize Operations Manager, up to very complex and time intense projects like the development of a fully automated cloud infrastructure using the whole VMware SDDC stack.
If you are interested in getting more detailed information about the professional service organization and the different roles within, I encourage you to check out the official PSO website or directly the PSO service catalog.
As you now got a brief understanding of the PSO organization itself, I’d like to tell you a little bit more about my current job as a Consultant.
As mentioned before, along with Architects, we as Consultants are usually working within different types of projects depending on what the customer’s needs are. Basically, a Consultant can be considered as a subject matter expert in one or more of the following areas:
- Data Center Virtualization
- Cloud Operations
- Cloud Automation and DevOps
- Networking and Security
- Digital Workspace
I’m currently focused on the areas of Data Center Virtualization as well as Cloud Operations which includes working with a broad variety of VMware products/technologies like vSphere, vSAN, vROps, vRLI etc.
Okay, so far so good, but now let’s get a little bit more practical about my daily work. As mentioned before, as consultant you are a subject matter expert who provides not only know-how about specific products or technologies, but also understands how they integrate among each other and even with third party solutions to provide an added value for the customer in form of a combined and well designed architecture to satisfy one or many use cases.
And here it gets specially interesting… To be able to deliver benefits with the help of our products and solutions I’m doing consulting on, on one side I need to be able to understand the customer needs as well as their use cases in order to translate them in to a technical solution on the other side. Of course, as mentioned in the previous section, the stated use cases and requirements are ranging from pretty basic up to very complex ones, depending on the project or the engagement you are working in. Sometimes it is about the implementation or integration of one particular product/technology and sometimes it is about designing and building complex solutions consisting out of N interconnected systems to meet the project goals. And in some cases it is even about consulting and guiding the customer through strategic decisions or reviewing his concepts and give advises.
As you now know a little bit more about the role itself, I’d like to also explain you briefly why I’ve dared to do this move 😉 But let me give you a little bit of context upfront.
I’ve originally worked for a local hospital as a Systems Engineer in the areas of Virtualization and Storage. Then, 9 months ago I took the step and moved to VMware and therefore went from a local Swiss customer company to an international vendor which was kind of a tough transition in the first line. Obviously there are huge differences in terms of working culture, but let me explain why it was absolutely worth it in my opinion and why I’m enjoying working for VMware!
First of all, if you are not used to it (as I was at this time), it needs kind of an adjustment period until you have fully adapted yourself to work in such an international environment where everything is so decentralized. The team is spread across countries and sometimes even across continents. However, the culture within VMware is awesome as everybody is helpful and supports you wherever he/she can regardless of team boundaries. Nobody is there because he has to be there… Everybody I met so far was very passionate in what he/she is doing here at VMware and this is extremely motivating and creates an unique atmosphere… At the end of the day, everybody is pulling at the same rope!
Second thing to mention, especially for technical people, is the huge diversity of projects you probably be able to work in. Projects in different industry sectors with different requirements and different environments are going to extend your technical horizon in an incomparable fashion. But not only the projects itself, but also the almost unlimited amount of resources and know-how within the company will allow you to literally ingest unlimited amount of knowledge.
Third thing I’d like to point out here as it kind of goes along with the previous point is the whole story with traveling. Understandably this scares most of the candidates a little bit at first just the same as it did me. Of course, I won’t lie here, these jobs require a certain level of flexibility as most probably you will cover a whole geographical area within your role. But what takes you a little bit of extra effort on one hand, gives you the possibility to get in contact with other cultures and people on the other hand and allows you to work within interesting projects like mentioned in the previous section.
And last but not least I’d like to mention the development possibilities within VMware. I’m not only talking about technical development, but also about career development. Even if you’re interested to jump in to a completely different role within VMware, you get supported in order to fully utilize your individual potential.
To summarize this post…
If you are a customer: Definitely take a note of PSO and consider our services and offerings the next time you’re about to initiate a project or if you just want to review your current environment and get some inputs there. Also comprehensive health checks can be requested to verify your infrastructure setup/architecture is aligned to the VMware’s provided best practices.
If you are a interested candidate: Prepare yourself for an exciting journey in the world of virtualization and cloud 😉 But also be aware that you have to be ready and able to go beyond a typical “9 to 5” job. Furthermore I would recommend you to check out the official job portal of VMware or simply follow VMware over the common social media channels like LinkedIn and co to receive updates and stay informed about current job opportunities.
Hopefully this post helped a little bit and if you have further questions, please feel free to use the comment section below!