SharePoint is a monster huge product, so it’s understandable that there is going to be plenty of confusion figuring out what type of position you need to fill to meet your business requirements.
Companies really need to research this more carefully or it is going to be impossible to fill your positions when you advertise like this. I’m not trying to make anyone look bad here, I am merely trying to highlight the problem in the industry – and it’ s global. No-one is getting this right. Companies are confusing the roles between developers, architects, IT Pros, super users, business specialists and trainers. Determine what you are trying to accomplish on your platform and research what roles will fulfill that. You don’t need a SharePoint developer to configure document libraries.
I often hear how SharePoint positions stay unfilled for years at a time. Yes there is a shortage of good skills in this space globally, but posting entirely unrealistic job specs is compounding the problem.
The following random job specs are sourced from Career Junction, IW, Career Web, Pnet and Jobs. Each has an explanation as to why they don’t work. And then a couple that do work :
Ok so there’s travelling involved – what kind of administrator? Server, site collection, helpdesk? What do they have to do, permanent, contract, etc etc. Nowhere near enough information here. How do you expect top notch candidates to take you seriously?
If I was looking for that many architects and developers, then there must be a big custom developed project in on the radar. Surely the most important requirement then would be technical ability, not communication and presentation skills. Again, not nearly enough information on the specs.
If you’re looking for a SharePoint Associate Consultant, then SharePoint knowledge should be compulsory, not beneficial. If you’re looking for a SharePoint person, then you need SharePoint development skills, not Microsoft developer skills. What skills do you mean? There are over 200 Microsoft products. But then it’s clarified a little with the .Net requirements. I fail to see how those degrees can in any way make you proficient in SharePoint, I would rather require SharePoint certification. They need a developer, not an associate consultant. That implies a totally different level of interaction with the platform. This spec comes across as the company not having a clear understanding of what they need. This could lead to the potential employee being shunted from pillar to post. Not a very enticing job offer.
They are looking for a developer but want that person to manage the entire environment? That’s not what developers do, that’s what architects and IT Pros do. Document library management and changing ownership? That’s something that site collection administrators and site owners do. Creation of application pools? IT Pro. Migrating websites? IT Pro. Upgrading websites? Maybe, depends if there is custom development on those sites. This spec covers 3 completely different roles.
How are developers going to grow Knowledge Management for the business? You need Knowledge Managers for that, not SharePoint developers. Web / graphics design is a completely different development competency, as is K2 workflow. How does that tie into the Knowledge Management plans? This spec covers 4 different roles and in no way explains what you will be achieving if you take this job. KM is it’s own specialised field.
Another spec that requires a supersonic human being. Developers are not responsible for network security, network specialists are. Configuring and administering the environment? IT Pro and architect. Managing permissions? Site collection administrators and site owners. That whole last bullet point – all IT Pro an architect. Developers are not meant to perform duties like this. They build web parts, event handlers and custom workflows – the only part in the spec that made sense.
Wow, that’s some training being offered by the company. I’d like to apply. Glad it’s a permanent position because that person is going to be there are very long time getting trained up to to do all that. The only thing relevant to the job title is the development of InfoPath forms. You can’t expect the same person – let alone a junior developer – to do helpdesk support, train end users, manage the servers, implement an ECM solution, and migrate and upgrade the platform. Once again, all completely different skill sets and roles. The person they are looking for doesn’t exist.
So What Works?
Yes, perfect. All ties in perfectly with what they need done. Comes across as organised and focussed.
I’d let it slide because the role is that of a SharePoint Specialist, not developer. There are people that have this range of skills.
Do you see how important it is to get this right? Do your homework. Good skills are rare! If you want to attract them, you have to be worth it. Having a flaky job spec is not a good start. It’s giving the impression you have no idea what you want or even understand the problem. Environments like this are red flags to the top skills in SharePoint.