EDIT: fixed the title; casual -> causal. I am clearly not ever going to be headhunted by any editing or proofreading companies.
I was not looking for a job change, but one found me. There has been persistent headhunter (Google, Microsoft, Facebook, Amazon, …) interest over the years, but any interesting job available also required relocation. I also wanted something compatible with my part time studies, as I have been working 80% part time at IBM to accommodate those studies.
I was contacted by the founder of a new startup. As a long time salaried IBM employee, I am surprised that the possible instability of a startup operation was of interest, but they made a convincing case for the future success of their product ideas and company. Their salary offer was also significantly higher than what I make at IBM, which sure didn’t hurt.
With interesting work as a prospect at this company, an attractive salary, no relocation required, and none of the negatives of current IBM HR practices, I took this offer after a week of deliberation.
Pros of working in DB2
One week of deliberation, especially when I wasn’t looking for a change, is a short amount of time to decide to say goodbye to a company that I’ve worked for about 20 years, which is almost half my life! Both my kids were born while working for IBM, and are now almost grown. I have a roots with the people and work that I am leaving behind.
I did a lot of really fun work in my years with DB2:
– Implemented multithread support and associated reentrancy retrofit of DB2’s Unix client code.
– DB2 Linux porting work, including portability reengineering.
– DB2 64-bit port. This was a project of massive scope. We can now eat terrabytes of RAM for breakfast.
– Development and maintenance of DB2’s internal mutex and atomic implementations, and associated memory ordering mechanisms.
– Lots of fun parts of our platform stackwalk and related post mortem factilities.
– AIX/TPCC performance and exploitation liason.
– DB2 contact for xlC and other compiler coordination.
– Lock-free reimplementation of DB2’s reader-writer mutex. The performance of our original reader-writer mutex code sucked for a number of reasons (including use of an mutex within the mutex.) This was a from scratch implementation where we used a single atomic to track the reader and writer linked lists (indirectly), the reader count, the writer held bit, and a writer reserved bit. This code has stood the test of time and remains one of my proudest creations.
– Implementation of DB2’s asynchronous IO abstraction layer. It’s hard to believe that it wasn’t that long ago that we did all our IO synchronously. This bit of code hides an impressive amount of operating system centric code from our high level development consumers, while squeezing maximum performance from each system.
– Development and maintenance of many other aspects of DB2’s operating system abstraction layer.
– Lead of project branch integration team during internal transition from the CMVC version control system to clearcase.
– Ad-hoc build tooling and makefile maintenance as required.
– Technical owner of DB2’s coding standards
– DB2 pureScale project (distributed shared disk database): Implemented various duplexing, failover and reconstruct aspects of the communications between the DB2 engine and the shared buffer pool and lock manager component.
– Lots of other stuff along the way that took me into various components of DB2.
I started straight from school in ’97 with a low salary (somewhere around $50K CAD). My salary and band rating both progressed very rapidly from there. There were also frequent bonuses in those early days. I was clearly perceived as being of value.
I also really enjoyed the people that I worked with in IBM. I’ve worked with so many very competent and skilled software developers over the years.
So, the pros include:
– Lots of fun and challenging work.
– What seemed like a decent salary.
– Almost nobody else to work for in the Toronto region for whom I could do systems and low level programming.
– Part time options for my educational project and extra time off with the kids.
– Awesome fellow developers. It is humbling and rewarding to work with so many really smart people.
– Working for a startup carries the risk of complete failure.
So why leave?
Many of the reasons to leave DB2 mirror the reasons to stay:
– Fun and challenging work.
– Better salary.
– Flexibility offered for part time work if desired.
– Opportunity to continue to work without relocation, and without having to do something boring like web programming, phone app development, java coding, …
– A collection of really smart developers.
– Staying at IBM can pigeonhole me and leave me viewed as a one trick pony.
– Expectation of a stock distribution and/or bonuses with success.
– The chance to work for a small company, shaping things instead of being a nameless drone.
– No inhuman IBM corporate HR policies to have to observe or be impacted by.
Fun and challenging work.
Now that I have started with LzLabs, I am starting to get a glimpse at just how aggressive and visionary this project is. The scope of it is very impressive, and I’m going to have a lot of fun working on it. My work is likely going to be some combination of concurrency, porting, and build & test infrastructure. These are all things that I am comfortable with and enjoy working on.
I was very satisfied with the rate that I achieved my maximum full time equivalent salary at IBM.
I was not satisfied with the way that it stagnated after that. I had not had a raise in a long time. Living in Canada it seems that food costs have 2x’ed in recent years, as have gas prices, hydro bills, and many others. My IBM salary was clearly not even tracking inflation.
The offer I got from LZ certainly made up for that stagnation.
That said, I probably could have asked for a lot more. I got heavily berated by an ex-IBM buddy for accepting the offer I got from LZ, which he said was way too low. He had the good fortune to have been canned by IBM. He’s since moved around and found just how low IBM Canada pays in comparison to others, and is now making $200K USD on the west coast. While my new LZ salary is significantly better than my IBM salary, he said that I shouldn’t have accepted anything less than $240K USD given my skills, and would have easily gotten that, even without requiring relocation. This was surprising to hear. I was clearly pretty clueless about the going rates for the sort of work that I’ve been doing.
My buddy recommends that I get away from LZ in short order (i.e. 6 months) if it shows any signs of not becoming a superstar player. It sounds like I could definitely profit by such a move, but I’ve never been primarily motivated by money. I’d rather play this new game long term and see where it goes.
IBM Canada capitalizes on the sort of salary comparison cluelessness that I had. It also capitalizes on what used to be a monopoly on systems and low level programming work. Without anybody else local to work for they have been able to keep salaries low.
With the ease of working remotely becoming so pervasive, IBM won’t be able to play this game as effectively anymore. This is clearly evident by the mass migrations that seem to be occurring (not even counting the frequent IBM purges).
One trick pony.
Loyalty to an employer used to be considered a virtue. I am not sure that is the case anymore. I left on my own terms, but should I have been fired from IBM, I think that the fact that I worked in only one place for 20 years would have hurt, not helped. Leaving IBM has a positive optics impact on my resume for future work.
Part time options.
I’ve started full time with LZ. I’ve been offered the chance to go back to part time in the fall when school starts again. The LZ founder has said of this
“You are going to have so much fun that you won’t have any desire to continue with an attempt to become a failed physicist. We have lots of those working for us already.”
Although this sounds like it is condescending, he is proud of his collection of very smart people, including all his “failed physicists”, which he said in a way that it sounded like a complement to their intelligence.
One of the LZ hiring strategies is to ask new hires “who is the best/smartest developer that you have ever worked with” (I can’t play my role in that game for a year since I was an IBM band 9). Judging by the interactions that I have had so far at the company, I can confirm that I am in with a really good group.
Inhuman IBM HR
I’ve mentioned that I really enjoyed the people that I worked with in DB2 and IBM. There are so many truly on the ball experienced developers in the pool. It was a real loss to leave IBM and not be able to continue working with these people anymore.
However, in recent years, I have seen IBM treat many of those skilled and experienced developers as disposable. Again and again and again, the most experienced developers are tossed like trash when the firing purges occur. These are in many cases guru level developers with irreplaceable knowledge. Some call this agism, but it may be more accurate to call it salarism, because I think their true crime was getting paid too much in the view of HR that is eying three new hire recent grads for the same total salary (or perhaps three employees in an offshore IBM lab where salaries are uniformly less).
As a 20 year employee, I had only 5 years before I also hit the apparent disposability threshold. Given that, the risks of a joining a startup that might fail are severely minimized. Worst case, if the start fails, then I am left looking for a job, which is probably also an inevitability if staying on at IBM. The only real loss in that case is the IBM severance that I walk away from by leaving voluntarily, and the new larger salary should compensate for that, provided I sack some of it away for a rainy day.
When I did a final walk around of the lab, saying bye to so many people I had worked with for so long (some that I had never even met in person!), I observed many that had reached or surpassed what I thought of as the 25 year purge threshold criteria. There is no apparent sane rationale for who gets to stay and who gets the knife. That uncertainty for those who remain must be very hard to deal with. Some who I talked to did not even have this perception of disposability, which was interesting to observe.
Tossing employees who have expired is not the only example of cutthroat IBM HR I have seen. In one case, a co-worker who had become the goto guy for a complex component of our code had the bad fortune of getting a promotion too close to one of the firing purges. There is an internal ranking scheme within IBM, and in recent years, anybody with a rank three was toast when the purges ran. Unfortunately, a promotion usually means you are dropped temporarily in rank, since you have to compete with more experienced developers once you have your new band rating. In this case, the promotion in question, reducing the employee rank from 2 to 3, which put him into the automatic firing bucket. It seems to me completely insane to spend five years training somebody, and then essentially fire him for a promotion.
I have also observed two cases where IBMers were fired within what seemed like months of returning to work after having recovered from cancer. That’s a callous action that demonstrates the people with their fingers on the triggers truly don’t think of employees as people. They are resources. Just are just numbers to be shuffled in spreadsheets. Observe that I refuse to use the cowardly term “Resource Action” (or worse RA, or RAed) for firing that IBM HR employs. I am guessing that this a term invented so that HR employees feel less sadistic when they have to run a spreadsheet computation to see who gets the knife. I won’t miss that sort of corporate sadism, and it was a strong factor associated with my choice to leave IBM.
Weighing all the factors.
Looking at all the pros and cons, it seemed clear to me that joining LZ and leaving IBM was in my best interest.
It was certainly a scary move. I don’t even have a salary or real job offer since LZ is not yet incorporated in Canada, and I am currently working as a contractor. Now that I have started, things are no longer quite so scary.
This was a huge change, and has happened really fast. All said, I am happy to have been able to leave on my own terms, and am going to have fun playing a new game at LZ.
Would I work for IBM again in the future?
I had trouble with the binary “Would you work for IBM again” question that was part of leaving IBM feedback form. Having enjoyed my work and the people I worked with over these years, my first instinct was to answer yes, and I did so. However, corporate IBM would have to reform the way it treats its people significantly to be attractive again. I suspect IBM is too large for that to ever occur.