The build guy is definitely a vital role. However, a common direction in the industry is to do DevOps instead of having "build guys". For CircleCI, we like to think that the "build guy"'s role will move to writing cool project-specific tools on top of CircleCI, instead of the low-level work of actually maintaining the servers.
Being "the build guy" is an important role in delivering great products. In fact, SaaS CI offerings in my experience cater to a small subset of real world apps, none of which are usually heavily used non-trivial apps. I helped build one SaaS CI product and really hope this changes in the coming years as we abstract more 'things'. But for the time being, 'build guys' or DevOps guys or whatever the latest word is play a vital role.