At SaaS, we currently have developers in India, Pakistan, Argentina and in the US in California and Arizona. Some are in intact teams. Some are individual contributors but none work in a central office.
I remember at one point I worked in a company where the CEO thought that if he didn't see the people working, they weren't. At SaaS, we only hire people who are so passionate about their work that we can't stop them from working, even if we wanted to.
This people policy mirrors our development methodology. If the code exists that we need in a robust SaaS platform anywhere in the world, we won't build the code. We search out best in breed technologies and leverage them for our clients.
At the same time, we hedge our bets with indirection layers and service level integrations that mean we can swap our almost any component of our solution without service interruption. This is also true of our developers. We have them write code, in such a way, that another qualified programmer can pick it up and run with it.
The key to our success here is the "master programmer" model. We hire both master programmers and entry level programmers but the master programmer, not the project manager, decides how a specific software development task is parceled to their group. Our entire goal here is to support the productivity of the master programmer since for whatever reason, they pump out 4-5x more code than their counterparts on the team.
So, in the end, we have a distributed people model that mirrors our distributed solution integration methodology. We have found that this dramatically reduces overall costs to everyone while maintaining the excellence of the work product. It's a global world and we want to position us and our clients squarely in the middle of the innovation revolution.
No comments:
Post a Comment