Your resume is not only for recruiters

Back in 2008-09 one of the seniors shared a tip that one should update resume even when not actively looking for a job change. I never realized the full value of that advise at once. Later I started following on that advise and used to update my resume generally every year in the month of November or December until 2015. I was caught up in dilemma which I suppose many must be facing about how little or how much more information is sufficient to be added in a resume. During that struggle I learnt what different things common people and extraordinarily successful professionals do to make resumes creative and impressive. At one point of time, I even took paid services of one of the leading job portals and fortunately quickly realized that it was surely a waste of money and time. The resume they presented was merely based on packaging jargons and hot keywords which search engines can help recruiters quickly find relevant profiles.

In the process leaving that bitter experience behind, those variety of tricks/techniques, the merits and demerits aside, I really started liking visual resume techniques. After iterations and improvisations finally in 2014 I ended up creating one visual resume which impressed me, most importantly convinced me.

Since then, I started believing your resumes are not only to impress recruiters, but one must also give importance to create resume which,

  1. Reminds, how far you have come through
  2. Helps you with impressive visual snapshot or a mind map of your journey and key milestones, which ultimately
  3. Motivates you subconsciously to visualize future path positively based on your current pursuit towards it

So here is my latest iteration after a gap of few years.

My career timeline

Thanks if you have stayed till here. Please do let me know your thoughts and comments how you approach your resume.

My SharePoint Revision

Let me begin Looking Back…

SharePoint Products & Technologies have biggest influence on my career & personal growth. Thanks to my Technology guru Sanjay Vyas,  I had opportunity to work very early on SharePoint during late 2001. At that time the beta release was called “Tahoe”. The final product came out as SharePoint Services & SharePoint Portal Server 2001.

Since 2001, I worked very actively hands-on on all versions (2001, 2003, 2007 & 2010). I also had chance to work on other related products like SQL Reporting Services, Fast Search For SharePoint 2010 and few others. I did different roles & grew professionally,

  • As beginner Explored the product with trial & error. Understood How Technology Should Be Learnt.
  • Did Implement Intranet for my first company. Learnt What it Takes To Implement Technology for the Business Purpose.
  • Worked as Technical Support Engineer. Understood How Customers Look at Same Technology or Solution Differently & How Important It Is To Give Quality Experience When They Face Issues.
  • Lead the Team Of Support Engineers. Learnt What It Takes To Lead With Technical Skills & deliver Value To Business.
  • Act as escalation point for the Professional SharePoint Support.  Realized How Working Efficiently With Vendors & Partners Is Critical To Business. Also How To Be Proactive in Starting New Operations Help Succeed.

Looking forward…

During 2011 till now, I gave myself time to gather other experiences (non-technical) by testing my comfort zone outside SharePoint. In that pursuit I stayed deliberately away from hands-on SharePoint 2013 work & experiences.  Now that I have gained those intended experiences, I thought of revising my SharePoint knowledge.

I decided a timeline for 7 days & at least couple of hours every day. Of course it was tough to put entire revision in that short span. I had to try something & I did following,

  • Step 1 – I thought of writing down what all I can think when think of SharePoint.  The list below may not be complete however the intention was not to write everything about SharePoint. It was just to do my memory dump.


Component / Concepts / Dependencies / Terms.


ASP.NET, Authentication, Authorization, Apps, App Parts, App Development, API, AJAX, Application Server, Active Directory, Analytics, Access, Architecture, ADFS, Application Pools


Blog, BLOB, Breadcrumb, Business Intelligence, Business Data Connectivity, Backup, Big Data, Browser Support


Cloud, Content Database, CAML, Content Types, Content Management, Crawl, Columns, Calculated Formula, Content Editor Web Part


Databases, Document Sets, Document Library, Deployment


Event Handlers, Enterprise Search, Excel Services, Excel With Power Pivot, Event Viewer


Foundation Services, Farms, Features, Forms, Forms Authentication, Federation


Global Deployment, Groups, GAC, Gatherer


HTTP, HTTPS, Homogenous & Heterogeneous Farms, Help


IIS, InfoPath, Index Server Role, Indexer, Internet Of Things, Integration


Jscript, JSON


Knowledge Management, Keywords,


List, Library, LDAP, Locations


Metadata, Master Page, Meeting Workspaces, Mobile


Network, Navigation


On Premise, Office 365


Portal, Permissions, Project Management, Project Server, Performance Point Services, Protocol


Queries, Quick Launch


Restore, Recovery, Records Management,


Security, Search, Site Collection, Site, Social, SQL Server, SQL Reporting Services, SharePoint Designer, Solutions


Team Site, Topology, Tools, Timer Jobs, Troubleshooting, TCP/IP


Users, User Profiles, Upgrade Paths, UDP


Views, Visual Studio, Visio Graphic Services


Windows Server, Web Server Role,Web Gardens, Web Page, Web Part, Web Service, Workflow,







  • Step 2 – Whatever I was not able to recollect well, I did specific search/reading/watching videos to get back the understanding.

At the end of week I felt happy about the amount of stuff I could revisit with this method. Some people may have already tried this kind of approach so I am not claiming something new. However I do want to share that this approach helped me not only revise SharePoint but also assess so many other things I knew & worked during my career till date.

It’s good to have this inventory handy to build focus areas, strengths & areas to be improved up on.