Pros
In my previous company, I was sick and tired of politics, legacy code base, patchy software practices and a race against time to "somehow" deliver the software to customer. You would always wish to do the right thing, but wont simply have enough room to do so. To add to the pain further more, there were a bunch of managers who didn't have a clue about the code or the product.
Now, I was offered a job at Air-watch as a senior developer in R/D, I quit that organization with a sigh of relief. May be, because I have seen the 'dark side', I am in a position to appreciate the goodness here at Air-watch. At air-watch R/D, I quickly realized the following.
Pros:
-- If you have a passion for programming, you have really interesting problems to solve.
-- The only "real" process to follow is source control practices.
-- The job requires you to have strong understanding of software engineering. To quote a few:
- Networks and protocols
- Cryptography (Asymmetric key and Symmetric key), Security and Authentication Models
- Concepts on embedded storage options and remotely securing computing resources.
- Mobility is at heart of all that is done.
-- One has the time and space in the organization to spent on reading and research.
-- Fairly large code base, which is ever increasing. There is no concept of customizing something special for the customer. Features gets added to the base product itself.
-- Everyone codes, fresher to top level manager. Ultra flat organizational structure.
-- New products and features are always in request. You really get to create stuff.
-- Many a time, you get to work with programming veterans. For example, this year one of the senior most programming folks in the company flew in to deliver amazing series of lectures on programming concepts to freshers and senior folks.
-- The team members are simply amazing. There is collective thought.
My share of rant:
-- If you are not passionate about programming, air-watch R/D is not the right place to be. One need to be ready to read, try out code to strengthen one's understanding. If your priority is not software development in work hours, look for a a services organization elsewhere.
-- Bad code puts a team in jeopardy - poor souls need to maintain the crappy software resulting from point above.
-- you need not be a rocket scientist at all - All that is needed is solid basics in computing and a strong desire to learn more.
Cons
-- Yes, Yes, more salary will make me more happy!
