Chapter 1: My Journey as a Software Engineer

In this discussion, I want to share my perspective on a rather unexpected topic: why I would refuse any offer for a promotion to a senior engineer role at Amazon, even if Jeff Bezos personally approached me with the opportunity (a position that could bring in around $750k annually!).

Yes, you read that correctly. If such a scenario were to occur, my polite response would be, “Jeff, no! How did you even get in here? You don’t work here anymore!”

Currently, I hold the position of L5 software engineer at Amazon, categorizing me as a mid-level engineer. I was recently promoted and, from my very first day, my aim was to excel in my role, rise to mid-level status, and then continue striving for further advancement. My dream was to become that exceptional software engineer who would eventually make it to senior engineer and possibly principal engineer, earning around $500,000 a year, and showcasing my total compensation to strangers online.

However, I quickly came to a realization — I am, in fact, an average programmer. I have always been average and was never the standout coder in my academic days. I simply put in a lot of effort and spent ample time coding. When I began collaborating with some of the most skilled engineers at Amazon, I recognized that I could not match their dedication and technical abilities. This led me to a crucial question: did I want to compete with them? My answer was a resounding no at that moment.

Many individuals overlook this aspect, but as you climb the corporate ladder in a large tech firm, the workload can become overwhelming. From conversations with several senior developers, it seems that many are clocking in at least 60 hours a week due to the multitude of projects and meetings they juggle. This doesn't even account for the extensive effort required to attain the senior engineer title at Amazon.

Once you achieve the mid-level L5 status, it becomes a terminal position, meaning you can remain there indefinitely without any obligation to pursue a promotion. Transitioning from L5 to L6 can take anywhere from 2.5 to over 6 years, as you must consistently demonstrate your involvement in high-impact projects and perform at a senior level.

I've spoken with engineers on platforms like Twitter and Blind who left Amazon due to frustration and burnout from striving to reach the senior L6 rank. They shared insights about the political nature of the promotion process and how heavily it relies on the significance of the projects your team is engaged in at that time. If those projects aren't noteworthy, your chances for a promotion diminish significantly.

For instance, a colleague from my previous team has been a mid-level L5 engineer for seven years. He is an exceptional programmer, deeply knowledgeable about the codebase, and is a tremendous asset to his team. Interestingly, he manages to work only 10 to 20 hours a week during quieter periods.

He does not feel inferior for remaining in the mid-level role and is genuinely enjoying his life.

Ultimately, my goal is to perform well as a software engineer while maintaining a reasonable work-life balance. I prefer to clock out at a normal hour rather than exhaust myself into the night, leaving me drained and devoid of a life outside of work. This is why I am contemplating foregoing the $500k senior engineer salary in favor of personal freedom, and I believe I would find contentment in that choice.

I encourage everyone to think about this trade-off: Are you willing to sacrifice your time and well-being for the possibility of a higher salary? For some, the answer may indeed be yes, and that viewpoint is completely valid.

This decision heavily relies on various factors, including the team you are part of, the projects currently underway, and whether your environment encourages striving for that promotion.

Regardless of what decision you arrive at, remember that your time is your most valuable asset.

The first video discusses the reasons behind the speaker's decision to avoid a senior software engineer position at Amazon, offering insights into the work culture and expectations.

The second video outlines six compelling reasons why the speaker has chosen not to pursue a software engineering role at Amazon, providing an honest take on the challenges faced in such a position.