David ex Machina

via  Pixy YC has the slogan “ make something people want ,” a seemingly obvious statement that is as powerful as it is simple. Though it is insufficient to build generation defining products. Take a summer blockbuster movie, this is a product that most people will want, it is built to entertain the masses, and you will be entertained! But you will not come out a changed mind. Servant-style product development also feels uncreative. Don’t get me wrong, it’s a very valuable skill to ascertain what people want versus what they say, and many incredible products are built this way (thank you Coke Coffee ). But it takes away some of the fun when boiled down to “tell me what you want me to make for you.” It takes perseverance. To go a little deeper, products that “make something people will want” tend to be more disruptive. People did not know they wanted to ride in cars with strangers to get around town, or sleep in a stranger’s home for relaxation. Someone imagined it, and now people...

Having worked in the tech industry for the last 10 years, I have performed a variety of roles including: Software Engineer, Product Manager , and Engineering Manager . I often get asked by colleagues and friends to describe the differences between the roles. Many often wonder whether they should switch roles, and how I decided to switch roles throughout my career. Given the frequency, I decided to write down my take, so others may benefit and use it to better guide their own careers. Below is my primer on the role of an Engineering Manager in a software company. The primer is organized from high-level responsibilities (the what) down to the low-level tasks (the how) required for competency. It is not an exhaustive list, but should set reasonable expectations. Top Responsibilities Team Plan An EM is directly responsible for the long-term health and sustainability of the organization they manage; in terms of both people and product. This requires managing the day-to-day work and p...

Having worked in the tech industry for the last 10 years, I have performed a variety of roles including: Software Engineer, Product Manager , and Engineering Manager. I often get asked by colleagues and friends to describe the differences between the roles. Many often wonder whether they should switch roles, and how I decided to switch roles throughout my career. Given the frequency, I decided to write down my take, so others may benefit and use it to better guide their own careers.  Below is my primer on the role of a Product Manager in a software company. The primer is organized from high-level responsibilities (the what) down to the low-level tasks (the how) required for competency. It is not an exhaustive list, but should set reasonable expectations. Top Responsibilities Product Vision At the highest level, a PM’s main responsibility is creating a vision for a product and setting the direction for the team. The scale of the problem should scale with the PM...