I noticed many members on here (340 out of 800), and on LinkedIn work as “SharePoint Architects” (I do as well). On my SharePoint travels I have met many SharePoint Architects and am often quite amazed how different the role is!
I have seen SharePoint Architects covering all manner of tasks, including these :
- Code Reviews
- Coding
- Deciding on 3rd party tools
- Deciding on application architecture (If there is one).
- Deciding what features in SharePoint to use to meet a requirement.
- Designing Server Farms and Topologies
- Designing an Application that will placed on top of SharePoint
- Performance Testing
- Requirements formulation
- Selling SharePoint to the business
- Demonstrating customisation to the business
- Costing, Scrum Master, Product Owners, the list goes on and on.
- Speaking at conferences
In your experience …
- What exactly should the ideal SharePoint Architect be ?
- Do you have a job description you can share ?
- Should they really be developing and designing as so many do ?
- What is “architecting” ?
- In fact, is there such a role in SharePoint at all ?
- How does it differ from the role of a Senior Developer, or even a SharePoint consultant ?
(Visited 29 times, 1 visits today)
I don’t mind at all, everything on my website is available for use by the SharePoint community. Thanks for referring people to it. 🙂 Hope it helped. I haven’t updated those job specs in a while though, so just adapt to your special requirements and new version of SharePoint.
(Visited 1 times, 1 visits today)
