I’m beyond excited to announce that I have joined ThoughtWorks. Since my acceptance of the position, I have been asked by many colleagues, friends and family; Why ThoughtWorks? I was even asked the same question by ThoughtWorkers during the interview. A week before I start, I’m asked the same question by ThoughtWorks’ People Support department (to highlight my answer in the new hire newsletter).
The truth is, there is no shortage of reasons or answers to this question, especially if software is your craft. In fact, I always felt tempted to answer: “Duh, it’s ThoughtWorks.” However, after all this time, I realized that I didn’t accept the offer because “Duh, it’s ThoughtWorks.” I applied and interviewed with ThoughtWorks because of it. I accepted the offer for different reasons; reasons that didn’t cross my mind until 3 or 4 weeks after my offer acceptance.
Ok, let’s back up a bit. I thought I knew ThoughtWorks, the company, fairly well. My ideas of the company were essentially about Martin Fowler; one of the most insightful people in the software industry. My ideas revolved around building great software with great developers while learning from them along the way. However, I was lucky enough to have worked with great developers in past jobs and also learn from them. In fact, there are tons of companies around the world that hire the best-in-class developers. So, why ThoughtWorks?
It really boils down to this … First, ThoughtWorkers brought out the best in me during the interview process. I felt like I was set up to succeed, even though it was the most radically different interview that I have ever been to. At the end of the full day interview, I felt like they learned everything they could about me. And I certainly learned much more about them than I ever did before.
They asked thought-provoking questions that are purposeful and meaningful. I felt respected as an engineer, but most of all, I felt respected as a human being. Which brings me to the second point … it was obvious that everyone I met at ThoughtWorks had a strong desire to make a big social impact. It was obvious they cared about how technology fits in to advance social and economic justice.
In fact, the first hour of my interview was all about ideas on advancing social and economic justice. What’s incredible about this is that ThoughtWorks doesn’t just say we care about it, they actually do engage in lots of pro-bono projects that serve humanity. To my surprise, during my first week with ThoughtWorks, I was involved in an ongoing social impact program by teaching low-income adults how to code in a real agile setting, helping them develop a real world mobile app. Read Roy’s Social Experiment for more information on how ThoughtWorks got there.
During week 1, ThoughtWorkers are actively trying to set me up for success. From sending me kind regards and good-luck messages to useful resources to involving me in pairing on code reviews for potential hires, and teaching me about the process from the inside. I’m beyond impressed by the level of transparency, thoughtfulness and thoroughness that is visible in everything ThoughtWorkers do. I even got to review the notes from my interview with ThoughtWorks (strengths and weaknesses). How awesome is that?
By the end of week 1, I’m inspired and excited to come to work. I’m excited to see where this journey takes me, personally and professionally.
People Matter Most by Martin Fowler.