Slinger's Thoughts

May 19, 2009

Do employers know the difference between SharePoint Administrators and SharePoint Developers? Is there a difference?

Filed under: SharePoint — slingeronline @ 11:11 am

The job market lately has had me a little concerned for the stability of my position where I work as a SharePoint Administrator.  (I also handle other IT duties, but SharePoint is my bread and butter.)  Because of the job market, I decided that I would look and see what other opportunities were out there.  I noticed something disturbing.  Firstly, there are a lot more positions for Developers than there are for Administrators.  That’s not so disturbing in itself, but when you look at the job descriptions for each, there are striking similarities.  Go ahead and check it out for yourself.  Go to one of the top job search engines like career builder or monster, and enter in “SharePoint Administrator” for a job search and look at some of the requirements of the positions.  Now do the same thing with “SharePoint Developer.”  The thing that I have noticed is that for almost all of those positions listed, it seems that the companies have no idea what they actually need.  I think that Microsoft, or some of the more well known SharePoint genius-gurus, should lay out specifically what the difference is between an admin and a developer for the benefit of these companies so that they can ask for the appropriate qualifications for the position they are trying to fill.

Even though I am not one myself, I have absolutely nothing against developers.  I have counted on their expertise on more than one occasion and I am ever grateful for their input and advice.  I would imagine that developers wouldn’t want to deal with the more mundane aspects of managing a SharePoint site however, and would rather focus on what they excel at, such as creating new webparts and features for the rest of us to use.  Without the developers, my job would be much more difficult.  Administrators, on the other hand, are often asked to do things that may be beyond their capacity.  Not that they don’t have the ability or desire; but rather they don’t have the experience and training.  I know I don’t, although I would love nothing more than to be a developer, and every time I learn something that I post here, I am that much closer to being able to consider myself a developer. (I have a long way to go.)  I thought what I would do is create a guide from my experience as to what the difference is between a SharePoint developer and a SharePoint Administrator, that hopefully someone will pick up and use so that instead of assuming that the two roles are interchangeable, there could be a clearer understanding of what the responsibilities are, what they should be and the tools that should be used.  If I miss the mark on anything, then please by all means, let me know.  Keep in mind, none of this is official, and I am not an MVP so don’t take any of this as “approved” or “certified.”   

Just to demonstrate the communication failure, below is a listing of the job responsibilities of a “SharePoint Developer” for an ad listing I found on Career Builder.

Provide day-to-day support of Microsoft Office SharePoint Server 2007 in a highly collaborative team
• Systems administration, maintenance, and synchronization of the MOSS 2007 Farm servers which
o The Production environment which consists of a pair of load balanced web servers and a backend 
services server
o A Model Office (QA, Staging) environment which consists of a pair of load balanced web servers 
with the services integrated
• Candidate must interface well with IT and user management, in-house developers and 3rd party systems 
• Application of Service Packs and Updates within a predefined maintenance window 
• Provide end-user support and troubleshooting of all of these environments.
• Migrate custom development code to the platform servers
• Stay abreast of related technology and recommend future system enhancements, software purchases or
system upgrades.
• Provide technical input to assist in development of project plans for projects that intend to use these 
environments as development platforms.
• Provide technical input to assist in development of project plans through detailed work breakdown 
structures and timeline estimations
• Provide written and verbal status reports to IT management and be able to effectively set expectations 
with users
• Be able to multitask several competing requests by gathering or estimating task priorities

If you look closely, that developer position is actually not for a developer, but for an administrator.  I figured I would narrow the field a little bit and search for a position for a “SharePoint Administrator” and I found the responsibilities listed below.

  • 3+ years of experience working with Microsoft SharePoint 2003 / 2007
  • MOSS technologies
  • Broad experience with the .NET Framework to include ASP.NET 2.0 / 3.5
  • Web services, XML, SOAP experience
  • Ability to interface with clients and gather requirements and facilitate meetings
  • Ability to develop and administer sharepoint systems
  • Strong competency in Visual Studio Tools for Office, Windows Workflow Foundation, Forms Server and Excel Services
  • Experience with DataSourceControl, DataSourceView, Membership and Personalization

    Maybe it’s just me, but that looks an awful lot like something more suited to a developer.  (I am fully qualified to be a SharePoint Administrator, with a certificate and everything, and I couldn’t do most of what they listed without some serious back-up.)  There is obviously some kind of disconnect between what employers are asking for and what they need.  It seems that the only people who know the difference between the different types of SharePoint people, are SharePoint people.  That’s disappointing, and which is why I decided to put this little reference together. Below is how I see the job responsibilities should be laid out.

    First I will go with what I know;

    SharePoint Administrator

    1. Responsible for Servers in SharePoint farm
      • Includes set-up and configuration of SharePoint Services on Servers, maintenance of Web Front End Servers, Indexing Servers, and some aspects of maintaining Database servers. (In smaller companies like mine, the job of SharePoint administrator also inherits the job of Database administrator, and this should be accounted for in deciding compensation.)
    2. Creation and maintenance of Sites and Site Collections, as well as all associated databases and services, such as Shared Service Providers, and Extended Authentication providers if needed.
    3. Set-up and maintenance of Outgoing and Incoming e-mail services
    4. Qualification, Installation and Maintenance of any Plug-in, Feature, Web Part, Template or Solution, including 3rd party software or applications.
    5. Responsible for back-up and recovery practices, and maintaining integrity and reliability of access to information.
    6. Responsible for set-up and configuration of Excel Services and InfoPath services (If available).
    7. Responsible or establishing and/or maintaining end user access policy and permissions.
      • This may also include the ability to delegate permissions authority to other users, as deemed appropriate.
    8. Responsible for implementing and maintaining search services, including defining search scopes.
    9. Responsible for implementing and maintaining user profile properties, including “MySites” functionality.
    10. Responsible for coordinating and implementing best use practices, and communicating with company management best use scenarios.
      • Best use practices may include creating simple workflow processes and simple site customization.

    Basically, from the way I see it, Everything that is on the Central Admin page of a SharePoint site, and some of things that can be accomplished with SharePoint Designer, should be the responsibility of the SharePoint Administrator.

    For a SharePoint Developer, that could start with this simple phrase.  If you MUST use Visual Studio to create or design some aspect of SharePoint, you are a developer.  If it simply can’t be done by any other means, and Visual Studio is mandatory for you to do your job, I believe that would qualify you.  I’m not a Developer, so I will probably miss most of the below requirements by a long margin, but there does need to be some clarification, so here goes.

    SharePoint Developer

    1.  Responsible for design, creation and implementation of custom webparts, .NET user controls, custom Master Pages, custom Layouts, custom Event Handlers, features, solutions,  and templates to be used in a SharePoint environment.
    2. Responsible for integrating non-SharePoint related services into SharePoint applications as needed.
    3. Demonstrates a proficiency in any of the following; XML, CAML,  XSLT, HTML, DHTML, ASP.NET, C#, ASP, JavaScript, style sheet/CSS

    Most of these I gleaned from the “SharePoint Administrator” job listings, so I’m sure that more needs to be added. I would very much like to see a standard applied to the title of SharePoint Administrator as well as SharePoint Developer so that companies have a better understanding of what their own requirements are. I would also like to abolish the term SharePoint Architect, or at least limit that to the select few who made the nuts and bolts of SharePoint, like the original programmers.  Hopefully, a little bit of clarification from the SharePoint community will help these companies find the individual who is the right fit for the positions they need filled also.

  • Advertisements


    1. Great post.
      Some times the employers realy want to employ someone both good at administration and development, and usually the developers use SharePoint a lot, it’s possible that they can do some admin work.

      Comment by Zhang Mingquan Mike — May 19, 2009 @ 8:15 pm

    2. I’ve always been of the opinion that a developer needs to know his platform inside and out – how else can he ever know if he’s building the proper solution for the problem?

      This is doubly so for SharePoint, since there is so little SP info floating out there as “common knowledge”. So, a SP developer must also be able to act as a SP admin – even if your company has separate people as the SP admins, chances are, the developers are going to be the admins for the dev servers or at the very least, the SP instance running in their local VMs.

      Comment by Greg Hurlman — May 20, 2009 @ 9:23 pm

    3. Excellent post. Tiffany Songvilay had a podcast in January on this subject as well.

      As a two-hatter (developer and admin) I don’t mind so much the positions that require both skill sets, but I have seen some postings where they say they want it all, but really what they want is more of one or the other.

      Comment by Jim Adcock — May 20, 2009 @ 9:36 pm

    4. You forgot the information architect stuff ;-)

      Comment by Thomas Vochten — May 20, 2009 @ 10:24 pm

    5. This has also been discussed at developer VS. customiser too.

      Comment by Jeremy Thake — May 21, 2009 @ 12:35 am

    6. I dont agree with SharePoint Developer point #1 – Responsible for design. I disagree, there is a lot more to design that just making it look pretty. Things such as user experience, user interface as well as making it looks nice. In my experience I have never seen a great coder who is great at design – different mind sets.

      Comment by PinkPetrol — May 21, 2009 @ 2:59 am

      • Excellent comment, PinkPetrol! I’ve noticed the same.

        Comment by Dan — December 3, 2009 @ 9:53 am

      • I agree with you specially all customers need special requests that’s need a developer to enhance and collect some SharePoint features and make an integration and more , it’s not only design for sure !!

        Comment by wael mohamed — February 7, 2010 @ 8:28 am

      • Like you, I alos dont agree with the 1st post.
        why would any developer what to be an administrator? They would not. They would not want to be called or be on call when the farm goes down or whether a document is buried in some sharepoint library or my calendar is not in synce, or I can approve a document… seriously, do any developers what to be bothered this way? I don’t think so

        Comment by Fausto — September 21, 2011 @ 8:12 am

      • I agree. Although I have worked with web designers – SharePoint design is a different animal. As a SharePoint developer i am typically handed a design in pure HTML which I than have to integrate into the basic SharePoint HTML wrapper and layout. Although 2013 allows for design packages to make this easier…I haven’t found it works as advertised. A true SharePoint designer needs to understand how to work with a SharePoint sites HTML layout and understand the control ribbon, web controls, master pages and the core.css.

        Comment by John Mimiaga — August 6, 2015 @ 4:24 pm

    7. @Greg – Although I agree that Devs need to know how to administer too, there is a big difference between knowing how to, and doing it day in, day out.

      There is also a major difference in attitude. Getting Devs to worry about CAS policies, etc. – they just want to get it in and working. Admins care about having the system robust, stable, and safe. Dev’s can have a relatively short relationship with a system, admins can be working with it for years.

      I think you’re right, they don’t know the difference, or employers want all in one (probably under the belief it will be cheaper).

      I’d also add, I think with SharePoint Admins need to know a bit about coding.

      Comment by andyburns — May 21, 2009 @ 3:01 am

      • I didn’t realise that I had stirred up so much! And I do tend to agree with most of you on most points.

        From what I’ve seen, regarding companies that don’t know what they want, one possibility is that they want a SharePoint Developer but only want to pay for a SharePoint Admin, or vice versa. (Being an Admin, I think developers should earn more.) I think any developer worth his salt would know the platform he was developing for, and the inner workings and intricacies of it. I also agree that an Admin should know at least some code. I don’t have the knowledge to write my own code, (I’m still learning), but I can edit someone else’s code to tweak it, change it just slightly to my needs, etc.

        Something else I happened upon in some of my searches, was a position asking for 5 years of experience with MOSS. Any one want to guess how that’s possible? I’m currently looking for a time machine so that I can fit that qualification…

        Comment by slinger — May 21, 2009 @ 6:10 am

        • I fully agree, Slinger. In fact I am probably your tech clone as far as my skill level. I just had a phone tech interview with a guy looking for a SP Admin, and grilled me on my .NET experience. Sorry, I know PHP (Linux). But, I have 3 yrs exp with SharePoint Administration. Sorry, not quite 5 years in with MOSS (dripping sarcasm). Great post!

          Comment by Dan — December 3, 2009 @ 9:59 am

        • Typical HR department canned response when they put together a job announcement regarding the years of experience. Good point, MOSS hasn’t even been out for 5 years.

          I agree with you regarding SP Admin vs. Developer. I am an Admin and still learning. I would like to branch into the Developer side.

          Just like in the military the best officers are those who served as enlisted. I think the same approach should be followed here. Developers should spend time as an Admin first. Just a thought.

          Comment by Mark — December 18, 2010 @ 2:31 pm

    8. Who are SharePoint Developers and What they do?…

      I came across an interesting article today regarding ShareP ……

      Trackback by Chaks Blog — July 7, 2009 @ 5:17 am

    9. […] Do employers know the difference between SharePoint Administrators and SharePoint Developers? Is there a difference? « Slinger’s Thoughts Do employers know the difference between SharePoint Administrators and SharePoint Developers? Is the…. […]

      Pingback by Do employers know the difference between SharePoint Administrators and SharePoint Developers? Is there a difference? « Slinger’s Thoughts « Training and Certification — July 22, 2009 @ 11:46 am

    10. Hi,
      Excellent Post, many developers dont know the differences between administrator and developer; very nice article.


      Comment by Venkatesh Suagana — December 1, 2009 @ 1:50 am

      • Actually, I thought I knew the difference before I was job hunting. Then I began to second guess myself.

        Comment by Dan — December 3, 2009 @ 10:01 am

    11. I have been attending the New York City SharePoint Users Group more frequently than usual the last 6 months, and this topic, and more details tied to it, have been at the center of most of the meetings, save discussions of 2010, of course.

      The question I would like to see answered here would take the discussion further, asking something like “Do Employers Know the Difference Between Developers and Application Specialists or Information Architects?” System Administration in the companies I’ve been with had to, given volume considerations alone, focus on Database considerations and Farm Administration: development work on the client side has been done by someone with lost of applied knowledge of all existing web parts, (custom or OOB), and how to customize parts, or refine data sources and layouts to bring the site to life, or make the refinements needed to make it truly usable.

      The Job Title for these individuals is not common knowledge yet, “IMHO”, but it needs to be, and the sooner the better. Employees are increasingly of the belief that if they didn’t develop a custom web part, or hire a set of developers that could, that they did not increase the ROI and value of the site. My experience is that nothing could be farther from the truth, but getting out the details and the use cases to make a compelling case for this is not something I’ve seen, or expect to see soon. This was a great article. I would love to see it get changed to “Part I”, and have the author take the deep dive into “Part II”, and get it right!

      Great job, folks.

      Bruce Byers

      Comment by Bruce Byers — December 11, 2009 @ 11:02 am

      • I would love to delve deeper into it, however my personal experience is very limited, as I am only an administrator. I’ve built a few farms, and have been an admin for two companies, but that’s it. If someone else wants to take a shot at putting together an entire categorical listing of the different SharePoint roles and responsibilities, I am all for it. Fire me an e-mail and we’ll see what we can come up with. With SharePoint 2010 right around the corner and everything that they have wrapped into it, I’m sure there is going to be a need for even more granularity in SharePoint responsibilities….

        Comment by slinger — December 14, 2009 @ 9:11 am

    12. I love your post about the administrator / developer stuff. I am an administrator and have programming skills, but not like a programmer. Why do the hiring people want both skills in the same person? I think they are very different. Plus most admins don’t get time to program, but often wish they could spend more time writing code. I am looking for work as an administrator in the Houston Texas area. But all I see is developer / administrator roles.

      Comment by Henry — February 13, 2010 @ 4:41 am

      • Hi Henry

        Iam Srinivas from India.I am looking in to the sharepoint admin jobs ,So can you guide what are the initial tasks should look my career in sharepoint admin.I have basic knowledge of sharepoint developer.Can u pls mail to is my gmail address.

        Comment by srinivas — October 10, 2011 @ 8:12 am

    13. Great Post….I have always put off learning sharepoint because of job descriptions like above. I assumed there is no different between a sharepoint admin or sharepoint developer.

      My focus is Exchange Server, but I would like to learn how to integrate the two

      Comment by Mike — February 14, 2010 @ 4:18 pm

    14. […] Who are SharePoint Developers and What they do? May 21, 2009 Chaks Leave a comment Go to comments I came across an interesting article today regarding SharePoint Administrators Vs SharePoint Developers […]

      Pingback by Who are SharePoint Developers and What they do? « Chaks' Corner — February 28, 2010 @ 3:45 am

    15. Excellent post! I just saw a job that needed a systems admin but wanted to be SP developer. I have seen this kind of mismatches in a lot of job postings for other stuff too, as I see it fit I think the hiring manager sends the requirements to hr and then hr ads to that in the idea of adding more value to the person they are looking for and definitely they have no clue of technical needs so they google it and add what they find without knowing what it means, well thats my explanation on it, i guess. Mostly this system works for non technical jobs. Anyway hope they realize the confusion they are creating.

      Comment by Rayman — March 18, 2010 @ 10:48 am

    16. Exellent post Man, employers really don’t know the difference between SharePoint admin and a developer. I think Idia only as all Indian employers wants to get both the jobs done from a single person(admin and dev) , but they do not understand that the Dev engineer can not do the admin part well as it requires basic understanding of many thing( not only Sharepoint)

      Comment by Suchak — March 22, 2010 @ 7:04 am

    17. Thanks for all the posts. I am a .net web application developer and was out to see how i would fit somewhere in sharepoint opportunities. I came across this and understood a few basic things.
      And about the job posts, my understanding is that, the positions is listed by the middle vendors(most) who dont have any technical attributes. Hence they just copy paste from their previously created requirement stuff. For them, word “Sharepoint” is what all matters..
      -Note, my understanding might be entirely wrong

      Comment by public — April 8, 2010 @ 11:30 am

    18. You are explain the nice difference between sharepoint Admin and sharepoint Developer.
      the share point concept is new most of the people dont know for about that. I am sharepoint administrator. there is good job apportunitis in this technologies.

      Himanshu Mulay

      Comment by Himanshu Mulay — August 5, 2010 @ 6:06 am

    19. Kudos!

      Very helpful!!!

      Comment by Daniel — September 16, 2010 @ 8:30 am

    20. Hi!
      First of all, I would like to thank you for this wonderful post which explains the difference between a SP Admin and Developer. I have just started out with SharePoint and I am yet to get into grips with it. What I would like to know is the prerequisites to be a SharePoint Admin. It would be really helpful if you could give me a kind of guideline or any tips which will help me realize my target of being a SharePoint Admin.
      Thanks & Regards

      Comment by Mohammed Shammas — October 15, 2010 @ 8:12 am

      • Can u gimme the same ………..for sharepoint admin…

        Comment by srinivas — October 10, 2011 @ 8:14 am

    21. Still Very Interesting that this post still has traction. I think I probably will revisit this in a future blog post, especially now that SharePoint 2010 is out and we are seeing all of the new changes that it brings. It’s on my to-do list.

      Comment by slinger — October 15, 2010 @ 9:11 am

    22. Nice Post as many people are very excited with SharePoint but don’t understand who is suited to be a SharePoint administrator.

      We are going to use your role descriptions to select the right person to get trained to become the SP admin.
      You have a typo on bullet point 7. Missing an “f”.

      Thanks for posting your thoughts!


      Comment by Guillermo — November 4, 2010 @ 2:12 pm

    23. […] first things first.  If you haven’t seen it or read it, go here and read my blog post about SharePoint Roles.  Read the comments too while you are at it. Okay […]

      Pingback by SharePoint Roles Revisited. It got better, and worse. « Slinger's Thoughts — November 9, 2010 @ 10:20 am

    24. Great post,

      thanks so much

      I work in recruitment (don’t give me grief guys) i’ve obviously tried to get an understanding of what i’m looking that’s why i’ve arrived at this site searching the difference myself (apparently i’m looking for a SharePoint Admin).

      I agree that clients don’t know what they are looking for half the time and many inexperienced or even experienced recruiters won’t question it because they think the client knows.

      On a “SharePoint Adminstrator” job description i have much of it fits in line with the SP admin description above but it says:

      “Architect, design, implement and support mission-critical software solutions based on Microsoft technologies”

      and required experience it say’s

      “At least 1 year experience in use of the visual studio .NET toolset, configuration of the .NET framework, developing and deploying web services, and configuring and assessing Internet”

      to me those duties and that experience would be of a Developer can someone confirm, i’d really apprecaite it.

      (PS: anyone in Oz looking for a rle :-P)

      Comment by Kevp — November 16, 2010 @ 4:57 am

      • For the Architect, design and implement I would ask your client what that entails. As far as the need for .Net, ask your client why they need it. If it turns out that they just copied from another add, they are contributing to the problem. You may want to point them to a resource that could tell them specifically what they need. (They may actually need two positions filled, instead of just the one.)

        Comment by slinger — November 16, 2010 @ 8:30 am

    25. Greetings I recently finished reading through through your blog and also I’m very impressed. I really do have a couple concerns for you personally however. Do you think you’re thinking about doing a follow-up putting up about this? Will you be likely to keep bringing up-to-date at the same time?

      Comment by Marlo Osborne — November 19, 2010 @ 1:08 am

      • I did post an article recently that kind of glosses over all of the SharePoint roles. It doesn’t list out all of the responsibilities because there is some flexibility for each one depending on the company’s needs. If I was properly motivated (“have enough free time”) I might edit that post and give some example job listings. I am starting to get the sense that is what people are really needing.

        Comment by slinger — November 19, 2010 @ 8:17 am

    26. Slinger,
      Could you refer 3 or 4 Sharepoint administrators to me please? I have an urgent need for professionals with that skillset…

      Comment by Franck Nanie — August 23, 2011 @ 9:38 am

    27. I am also a recruiter looking for a SharePoint Administrator. I was lucky enough to ask our current admin what I should be looking for and he made the distinction between admin and developer. That’s how I ended up here. The discussion has been quite helpful. It will help me to accurately describe what we need.

      Comment by Saundra — September 15, 2011 @ 10:49 am

    28. i am a fresher in sharepoint .. Thanks for the guidance given..

      Comment by surya varma — October 10, 2011 @ 11:22 pm

    29. Commented on this not long ago ..

      Comment by Mark Freeman — October 21, 2011 @ 5:24 am

    30. I truly appreciate this article post.Really looking forward to read more. Much obliged.

      Comment by Brogan Reddick — February 1, 2012 @ 10:49 am

    31. Well, I just stumbled upon this and well, although it was posted in 2009, guess what? Not much has changed. I think there definitely needs to be distinction and your statements were dead on. I am an SharePoint Administrator, not a developer, but have their place, but they are not all in one! Cheers!

      Comment by Kathie — March 7, 2012 @ 8:17 am

      • Whats worse about this…is know recruitment companies are not even considering it.
        I recieved this the other day:
        Looking for someone with Sharepoint Admin skills for migration, 2007-2010 and adminstration of large Farm with
        SQL experience, and .net Developer skills for the Sharepoint Apps.
        55K 58/k earnings.

        really? comon… this has to be a joke.. but it was not..

        Good luck on finding someone.

        Comment by F.Cepeda — March 7, 2012 @ 8:31 am

    32. hi i have finished sharepoint admin and development and i got microsoft certification for development but only thing is am a fresher but am stuff in there any way to enter into the company.please reply to my mail id–

      Comment by manimekalai — March 9, 2012 @ 8:10 pm

    33. Great post, nothing has changed since then.

      Most of job descriptions would suit a “all in one SharePoint Expert” ,
      doing everything from architecture to development, ending up doing something that makes everyone frustated and unhappy …

      Comment by Frustration — March 20, 2012 @ 7:34 am

    34. For a recruiter, it is the most fascinating and quientessential information as they would be provided with a professional vision to differentiate administrators from developers.

      Comment by Vishrut Buch — May 4, 2012 @ 9:37 am

    35. I am a SharePoint Administrator with the necessary Microsoft certification, if anyone knows of a SharePoint Administration position opening please let me know on I have end-user, power user and the designing certification to my name.

      Comment by Jacques — June 4, 2012 @ 2:17 am

    36. Sharepoint developer
      Programmer! Should know dev most languages used for sharepoint (C#, .net, javascript etc) and visual studio and Sharepoint Designer. None of the other jobs should be responsible for development. Asking for a combo Dev/Admin is looking for trouble.

      Sharepoint Consultant
      Know how to install and configure sharepoint using the wizards. Know basic management of content and site collection features.

      Sharepoint Administrator/Farm Administrator (same thing cuz if you don’t know how to work with a farm, you’re not an admin, you’re a consultant)
      Consultant + Sharepoint and only Sharepoint. All things Sharepoint (nothing outside of should be expected from this person). Know how to install, configure, deploy and support a SP farm manually (without wizards) from top to bottom. This person should not be responsible for infrastructure, that should be either a general systems admin or…

      Sharepoint Engineer
      Admin + able to plan, install, configure, deploy and support the infrastructure that sharepoint is built on. Including Win Server roles, SQL server/biz intelligence and exchange. Engineer may know how to buld/connect other MS systems like System Center and such, but that’s really the purview of…

      Sharepoint Architect
      Engineer + plan and configure systems integrated with sharepoint such as CRM, ERP, SAP. This is the most senior sharepoint person and should know everything above but only be responsible for planning and integrating the overall systems. Should not be working on sharepoint farm installations. You can get that done cheaper.

      Sharepoint Project Manager
      Project manager that knows how to delegate the roles as explained above.

      Sharepoint Business Intelligence Manager
      No such thing.

      Comment by Oldbay — June 14, 2012 @ 10:36 am

      • Forgot to say, Great post! Glad someone out there sees the same thing going on. So I’m not just crazy :-)

        Comment by oldbay — June 14, 2012 @ 2:43 pm

    37. nice informative post.
      Am a dot net person, with around 7 year exp in c#. Wanted to get into SP.
      Would it be easy for me to get into sharepoint administration by self learning and videos on youtube?
      planning to download the MS VMs.

      any pointers to this regard would be highly appreciated.


      Comment by Prashanth — June 23, 2012 @ 5:18 am

      • don’t download the MS VMs if you want to learn admin. Create them from scratch. Install and provision your farm and apps from the ground up without using any wizards. Good luck.

        Comment by oldbay — June 29, 2013 @ 8:17 am

    38. Great Post!

      I’ve noticed SharePoint seems to think that all developers and administrators can do away with testing.
      SharePoint Tester, there are so many sites that have issues, broken links, missed spells, 508 accessibilities and security issues.
      Not to mention that validations of a form or info path etc.., workflow and BI logic that does not work per customer requirement.
      Just because it is a web site, that it is not required to be tested.
      Please, add SharePoint Tester as one of the job requirements. SharePoint 2013 has added Mobile apps and SharePoint Plus for iPad, it will be very interesting with the tester.
      Thanks for sharing and collaborating.

      Comment by — February 20, 2013 @ 12:22 pm

      • Great Point! I definitely need to add some roles to the SharePoint responsibilities list, and that is definitely one of them. I don’t know if I will edit this post, or just write and entire new one, but I will definitely keep that in mind.

        Comment by Jay Strickland — February 20, 2013 @ 12:27 pm

    39. […] Do employers know the difference between SharePoint Administrators and SharePoint Developers? Is the… This is a great discussion which aligns with discussions on this site on the roles needed in SharPoint teams.. I have also discussed this here […]

      Pingback by SharePoint Development Weekly Roundup (26May) | — September 25, 2013 @ 4:11 pm

    RSS feed for comments on this post. TrackBack URI

    Leave a Reply

    Fill in your details below or click an icon to log in: Logo

    You are commenting using your account. Log Out /  Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out /  Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out /  Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out /  Change )


    Connecting to %s

    Blog at

    %d bloggers like this: