Just my opinion**
Being average at SQL-Server administration is very easy, because those nice folks at Microsoft have kindly pre-set all the configuration options to average. However if you want to be a great DBA you need (a) to work hard every-day, and (b) to know how it works.
Index management is a good example. Sure you can download scripts that will run every night and reorganize and rebuild them for you (my favorites are here … http://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html), but for many aspects of Index management you need an insightful eye to make sensible decisions.
Removing duplicate indexes is one of those tasks that cannot and should-not be scripted (DBA Rule#31: Never automate deletes). I use a version of this script (http://thomaslarock.com/2010/08/how-to-find-duplicate-indexes/) to list candidate duplicated indexes. But having the list is just the begining. I need to not do silly things like remove clustered-indexes, or apparent duplicates that contain includes or filters.
Getting rid of unused indexes is another of these tasks that need common sense, like knowing how long the server has been up, and therefore if those unused indexes are long-term unused or only since last weekend. And not removing system indexes is always a good thing 🙂
Then there’s the experience needed to know the difference between a good index and a mill-stone bad index, dragging down the whole servers performance by needing updates far more than ever being used.
If your company is not really serious about its data, keeping SQL-Server ticking along is so easy a manager/dba or developer/dba could do it!