*Title: Sharepoint Architect*
*Location: Indianapolis, Indiana*
*Duration: 1 year*
*Possibility for 2 openings*
Job description attached
*SharePoint 2013 is required*
This is someone who has done *custom development* on SharePoint (CODED
development), this is not the same as those that have done out-of-the-box
configurations of SP. Those developers are not a fit.
- Have they architected a *coded* SP solution, ie. Solutions that used
Visual Studio solutions in them (C#/.NET background)
- In older versions of SP, this person would have coded custom
webparts. Custom webparts are no longer allowed in the cloud. Apps are
used now (SP2013)
They will be able to explain the differences between SP 2010 and SP2013.
Someone who has just been doing out of the box configuration would probably
not know the difference.
This person understands the role that a SP Admin does… interacts with Farm
Administrators. Some of the tasks they do overlap
- Understands servers, load, code on a page
- Will understand cloud and connectivity issues… impact that developed
solution has on them
o i.e. understanding the impact a webpart has on a page (like time it
takes to load), understands WHY you need to have site collections.
Have been responsible for the development and design of *enterprise
solutions… Farm level solutions*
Would know Central Admin
They will know how to integrate their SP site with other environments
(different systems outside of SP)… BDC (Business Data Connectors)
Thanks and regards
Sr. Technical Recruiter
Sage Group Consulting Inc
Phone : 732.767.0010 x 312
Email : *jvam...@sagetl.com* <jvam...@sagetl.com>
Linkedin : https://www.linkedin.com/pub/j-vamshi/a8/b02/b4
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/reqsresumes.
For more options, visit https://groups.google.com/d/optout.