Yen-Ming Lee

What does it feel like to be an engineering manager at Amazon: Since the RTO announcement it became popular to write shit about Amazon, but it's still one of the best companies around the world. A few weeks ago, Gilad Naor shared with the 'Leading Developers' readers 3 lessons from his time as an engineering manager at Amazon. Here is the first one, read the full article here: https://lnkd.in/dHBxv2Ha 𝟭. 𝗦𝗼𝗹𝘃𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀 𝘄𝗶𝘁𝗵 𝗺𝗲𝗰𝗵𝗮𝗻𝗶𝘀𝗺𝘀 My first meeting at Amazon was baffling. I entered a room with about a dozen Software Development Managers (SDMs) and Product Managers (PMs). Everyone sat in silence and looked at their laptops or the printed papers they had before them. It was my second day at Amazon, and I picked up one of the extra sheets and started reading. After those first ten awkward minutes, everyone finished reading and the meeting began. Why do Amazon meetings always start this way? This is a specific example of how Amazon approaches problem-solving. It is the "Good Intentions Don't Matter" approach. In a famous internal video, Jeff Bezos talks about why good intentions are irrelevant. When things don't work, it does not matter what people wanted. All that matters is fixing the problems with mechanisms. For example, many busy managers come to meetings without first reading the prep material. They all intended to read the 6-Pager before the meeting. They just got sidetracked by the latest emergency. Scolding the managers won't solve the problem. A mechanism will. This is why all Amazon meetings start with a study period. The remaining meeting time is then spent on high-quality decision-making. Meta solves the same problem by creating cultural norms. I can't count the number of times that I heard a senior leader cut off the presenter: "Stop, assume that everyone here already read the slides. Let's get to the point." This is a culture-first approach. I have seen this work well in some teams, and not work at all in other teams. At Amazon, the solution is part of the company's "operating system". ------------------------- Anton here - by now everyone is familiar with the 6-pager concept, but that "operating system" thinking can be used almost anywhere. Think about something annoying that your developers do, and how can you solve it. For example, I remember being annoyed that people don’t update the Jira tickets. Finally, after requesting multiple times, now we just take 20 seconds from the standup to update them.

56

8 Comments

Distinguished Engineers (E9) at Meta make $4m/year. That's 16x the Bay Area median ($255k) Let's break it down [output = input x leverage] We all have 24 hours in a day, so there is a cap on [input] But hey, let's say they manage to have 2x-3x more focused time, so their [input] is 2x-3x There is still 5.3x-8x to go And that's [leverage] Here is the [leverage] they have: 1️⃣ Writing Every piece of text they write is clear to everyone, and they write a lot, for a lot of people 2️⃣ They create something from nothing And that something has clear value to the business 3️⃣ They influence other Engineers around them They are often described as having a "Midas Touch" in terms of their ability to uplift and develop other Engineers around them The best indicator is that the Engineers in their teams get promoted faster 4️⃣ They are well known and have an impact beyond Meta, promoting the brand 5️⃣ They have industry-leading experience in some areas There are rumoured to be <50 E9s at Meta

13

1 Comment

Waymo is probably both more expensive and longer waits on average than Uber or Lyft today, but they are close enough, and rapidly getting better. These markets will flip to fully autonomous when the tech is ready.

2

Scaling Memcache at Facebook. In this video, we walk through the 2010 research paper "Scaling Memcache at Facebook." This paper has been very influential in companies building distributed caching systems. For example, Uber and Twitter have caching systems inspired by Memcache. The requirements of Memcache were: 1. Easy adoption, minimal APIs 2. Low Latency 3. Very High Availability (without sacrificing too much on consistency) 4. Large globally distributed system The design choices of Memcache are influenced by the above, as we will see in this video. Video: https://lnkd.in/d5kPu9UY #SystemDesign #Caches #ResearchPaper

87

2 Comments

“There’s no jobs for Jr Software Engineers out there!” NOT TRUE…But there are some major issues in today’s hiring market. 1. MISALIGNED FOUNDATIONAL EXPERIENCE: The majority of aspiring SEs are either: Recent CS grads (less hands-on exp); OR, Bootcamp grads (less theory). Meanwhile...Most enterprise companies who hire a ton of SEs are looking for CS grads that ALSO have hands-on experience already. 2. MISALIGNED TECH STACKS: The majority of aspiring SEs are only experienced in NodeJS and/or Python. Meanwhile…Most of the companies who hire a ton of SEs are using Java or C# backends. Companies using NodeJS or Python backends are often smaller and can't hire as many SEs. That’s why our Enterprise Accelerator is making a difference. We identify diverse CS grads who are hungry, and we teach them the hands-on Java skills that companies are using in the real world over 3 months. Best of both worlds 😎 If you're interested in seeing some of this kind of talent--send me a DM and we'll get you connected. Want to join our next Enterprise Accelerator cohort? Stay tuned for the next webinar in early August.

77

7 Comments

While there are certainly individual variations in skill and experience when discussing modern software development the story is much more nuanced than pure individual effort.  * software development is a team sport -- individual performance is heavily impacted by the system in which they are asked to operate in.  * we pair skill and experience to this model of understanding performance by expecting people to be able to influence and adapt in direct proportion to their seniority, aka the more senior you are the more responsible you are for the outcomes of your work, the less senior you are the more your manager and management chain are responsible.  * humans want to succeed, we're social animals who derive purpose from demonstrating skill, and working collectively. All of which is to say there is no way you have over 1000 people underperforming at your company without senior leadership deeply implicated in.  If nearly 10% of your company is failing, versus just having the market move against you, you need to fire the CEO.

150

9 Comments

Seeking Staff Engineer, Team Lead, or Architect Roles Responsibilities: Graph Structure Implementation:Transformed the flat category structure into a complex graph structure using design patterns like Model Tree Structures with Parent References, Child References, and an Array of Ancestors. AI-Powered Search: Upgraded the search system from Shopify’s default to an AI-enhanced search using Algolia, significantly improving search performance. Image Processing: Created an image labeling system using color quantization for metadata extraction, supporting machine learning algorithms to link products and images. Innovation and Productivity:Worked with different categories to optimize their workflows, fostering innovation through the adoption of the 80/20 rule to encourage engineers to focus on product-oriented and creative tasks. Team Growth and Development: Directed the significant expansion of the engineering team, focusing on effective onboarding and continuous training as the team scaled up.

5

My Journey to Securing 7 Offers for Management and IC Roles Across FAANG and Startups I’ve been considering opportunities beyond Amazon since 2020, but I was fortunate to be offered enriching experiences year after year, which kept me from making the leap. By early 2024, after laying the foundations for AWS App Studio, I decided to explore other roles within #Amazon. However, I realized that Amazon’s presence in the Bay Area was shrinking, and with its #RTO policies, the management opportunities in #bayarea were limited to just a few roles, none of which aligned with my interests and goals. A combination of limited internal opportunities, and changes in Amazon culture and policies, motivated me to explore external options. Initially, I had two interviews with a FAANG company and a startup, but I failed them miserably. Securing new interviews proved difficult due to factors like scarce roles, high competition, and increasing expectations in both technical and people-management skills. I quickly realized I needed to make every interview count by preparing more methodically and strategically. In a future post, I’ll dive into how I: a) Adjusted my job search to land new interviews consistently b) Staggered my interview timeline to maximize preparedness and increase the likelihood of receiving multiple offers c) Prepped for technical skills, as many companies now expect managers to be as technically competent as senior engineers I also decided to interview for individual contributor (IC) roles for several reasons: a) I’m still hands-on with my side projects b) Companies are reducing management layers c) I enjoy both IC and management roles d) Compensation for ICs at some companies can be higher than for managers at others e) Since I was preparing for technical interviews anyway, I figured I might as well explore IC opportunities too I segmented my job search into four categories: Startup/FAANG and IC/Management, staggering my applications to focus on startups first and then #FAANG. This approach created an avalanche effect: I started receiving IC and management offers from startups, followed by multiple FAANG offers across both IC and management roles. Here are the benefits of this approach: a) I was able to fairly evaluate startup opportunities without bias toward cash components. One startup came close to winning me over, but by that point, I had FAANG offers and ultimately decided to pursue those. b) I gave myself a chance to objectively reconsider an IC role, as I’m still mid-career c) I ensured that for any managerial role I considered, the company culture and its policies aligned well with my values. d) This approach helped me negotiate effectively and secure a top-of-market compensation package. e) I was at my best in the final interviews (both FAANG and startups) after having multiple real-world practice sessions with other companies.

40

6 Comments

A few years ago, I wrote a post on Quora about interview process for Principal Engineer role at Amazon. In that post, I shared my own experiences as the recruiter owning that hiring process, as well as tips from other Principal Engineers who had been through the process. Even today, I get weekly emails and messages from senior engineers who saw that post and want to learn more about the Amazon interview. We often end up talking about more than just Amazon. We discuss career development and interview skills in general. I really enjoy those conversations! Since 2017 (when I wrote the Quora post), Amazon has created several helpful resources to prepare candidates for their interviews. Here below are those "official" interview prep materials. I hope you find them useful. Feel free to share them with your friends who are getting ready for job interviews. The Original Quora post: https://lnkd.in/gGVBsJfn Amazon Interview Prep Repo: https://lnkd.in/gnnanGCz Now that you have a starting point, in coming weeks, I plan to write about the "softer skills" that are hard to measure but can really make a difference in interviews. I will expand on those topics. I will breakdown topics like "technical leadership assessment in interviews", authenticity, dealing with ambiguity, "active listening during interview", and other topics. I will write about 'interview preparation' itself! DM, email me on what other 'non-obvious' topics you want me to write about? PS: I'll try to keep my writing practical and broadly applicable, even though my experience is mostly with Amazon. 😀 #interviewing #careeradvise #careergoals #careertransition #interviewpreparation #interviewtips #principalengineer #amazon #amazoninterview

127

9 Comments

It’s no secret—I’m obsessed with humanoid robots. Why? Because they’re cool—they’re revolutionizing manufacturing, reshaping the labor force, and pushing humanity forward in ways we’re only beginning to imagine. (and maybe I just need more help in life. Obviously). Here’s what’s happening in the world of my favorite humie heroes: 🤖🚘 Figure has teamed up with BMW, putting their humanoid robots to work in auto manufacturing. 🤖 📦Agility Robotics has introduced Digit, their incredible bot that’s already lending a hand in Amazon warehouses. And of course, there’s 🤖 🎁Tesla’s Optimus, aiming to wrap our Christmas presents (or take over other tedious tasks) by 2025. This article dives deeper into these robotic trailblazers—and my favorite “humies.” Which one’s your favorite? I can't decide, but hopefully you'll weigh in.

8

1 Comment

If you're not a software engineer, keep scrolling. I've been an engineer my entire career and have led engineers for 9+ years. I love this profession. But there's one mistake I see mid-level engineers make too often: Not being clear about the value they're providing. There are 4 areas in which engineers provide value: Technology, Product, Process, and People. But no one gets to Product, Process, or People without mastering Technology. And I'm here to tell you there is a lot of value in the technical understanding. Don't try to scale the ranks before you build depth there. We’re engineers. No matter your title, you need to be comfortable building software. Ideally, you should love it. When you’re progressing through your career, it’s exciting to get tapped on the shoulder to lead a product, overhaul a DevOps process, or manage people. And when you get these opportunities, take them. But make sure you stay close to the engineering part of the process. Because as soon as your coding capabilities start to dwindle, you lose value. That sword needs to stay sharp. A principal engineer who is either a) not interested in being hands-on or b) no longer capable of being hands-on, can’t succeed in leading a team. Today I’m a CTO. But if my team needs me to write code, I’m there in a heartbeat. So my advice to younger engineers is: Stay close to the tech. It makes you better at Product, Process, and People. If you’re an engineer reading this, know that I appreciate you. This isn’t an easy job, and I respect you for doing it. P.S. In the spirit of this post, here's a photo of me with much longer hair from *slightly* earlier in my career.

51

7 Comments

The hardest technical decision I made at Amazon wasn't about technology. During a project, an engineering team wanted to rebuild our entire checkout system. I remember, the enthusiast team; "It's legacy code," one of my best engineering colleague said. "We can do it in 3 months." But here's what my Amazon experience taught me to ask: I asked the below Questions: 1/ Why now? 2/ What's the actual pain? 3/ What's the hidden cost? After diving deep (Amazon leadership principle in action), we discovered: - 80% of issues came from 20% of the code - Complete rebuild = 6 months minimum - Migration risks > Current pain What we did instead: 1/ Isolated the problematic components 2/ Created clear interfaces 3/ Rebuilt critical parts first Result: - 70% improvement in performance - Only 6 weeks of work - Zero customer impact The Framework I Used: 1. Pain Assessment - Current impact - Future risks - Resource cost 2. Solution Mapping - Quick wins - Medium changes - Complete rebuilds 3. Hidden Cost Analysis - Migration complexity - Team bandwidth - Customer impact Key Learning: Technical decisions aren't about the newest technology. They're about making the right trade-offs. Early PMs: What technical decisions are you struggling with? Let's solve them together 👇

158

12 Comments

Amazon-to-Google-to-Amazon #a2g2a thought of the day: interesting to see how RTO (Return-to-Office) outcomes are entirely different for the two companies. In my post today, I don't really want to go down the path of debating whether RTO is "good" or "bad". There's very emotional and valid opinions on both sides, and it affects people's personal lives in real ways. Please be respectful. Whether you agree with the policy or not, for it to actually work it does need *critical mass*. Both companies have essentially the same RTO policy (3 days/week expectation), but there's significant differences is in how the message was delivered and enforced - and the outcome. Google’s 3-days-per-week was mostly a “pretty-please, would-you, if-you-don't-mind” with no actual enforcement (but some vague threats). So most people ignored it. They still do. Leadership got frustrated and the message got less polite over time, but nothing really changed. Even as of 3 weeks ago, when I was still a Google employee, the buildings were fairly empty. That made being physically in the office significantly less useful, other than enjoying the perks of free food and massages by myself (and occasionally with 1 or 2 coworkers). Amazon’s 3-days-per-week came with actual enforcement. Amazon used badge reader data to track when people were actually coming to the office, with consequences. It does feel a bit draconian, but you can’t argue with the effectiveness of saying “we have a policy that we believe is business-critical and we’ll enforce it or else.” I appreciate that when I come to the office, I can find my coworkers there and we can have f2f meetings. There’s critical mass for RTO to actually be effective. Amazon has picked a lane. Personally, I have not figured out how to truly be productive and happy working remotely in the last 4 years. I respect and appreciate the fact that some people have, but I haven’t. I do like the option to stay home a day or two, skipping my long commute, working from a lounge chair in my backyard on a sunny day. But there’s nothing like the energy in the room of a good group meeting, or the chemistry of a face-to-face 1:1, or the enthusiasm of two engineers standing in front of a physical whiteboard drawing boxes and arrows with markers brainstorming about the future. Or the bonding of sharing a meal or a walk between buildings with a coworker. I feel energized when I’m physically in the office. It literally charges my batteries. I’ve been coming to the office 4x/week and loving it. 

183

34 Comments

Amazon SDE Interview, for software development roles that require *at least two years of experience* This technical interviews typically require you to perform coding and system design *white boarding* exercises. Expect to be asked to write syntactically correct code—no pseudo code. *Get comfortable coding with a pen and paper.* The Data structures and algorithms competency measures your ability to choose the most efficient run-time solutions. For example, different data structures are more performant for reading data while others are more performant for writing. Algorithms should be as fast as possible and, *of course, solve the problem correctly* . Look out for edge cases for which your algorithm fails to satisfy requirements. The Problem-solving competency assesses your ability to take something complex, break it down, identify a solution and translate that solution into *working code* . Explain your approach before coding, and *vocalize your thought process as you proceed* . This isn't natural for everyone, but it will help your interviewer give you good feedback and hints if you need them. https://lnkd.in/gdhdri7j

20

2 Comments

"Build in primitives" -Andy Jassy, #Amazon CEO https://lnkd.in/gHMYt7NX Happen to take the time to read this year's Annual investor letter from Andy Jassy. Deep in 2nd half, it talks about how Amazon started thinking about "building in primitives" and how it has been game-changing for them and their customers. Probably old news for some, but eye-opening for me. Definitely a good read!

2

SWE job growth declined for the first time since 2000 The SWE market has had tremendous growth. Though now is the first time in two decades we’re seeing shrinkage in the number of job openings. Gergely Orosz wrote a wonderful, in-depth article on the state of the SWE job market. Learn more in the latest issue: https://buff.ly/4f5ldDe If you’re new to my content, every week I share a spreadsheet of recently posted, hand-picked software engineering roles to make your job search a little easier. To get the weekly jobs via email, subscribe here: https://buff.ly/4hkLOh0 Photo: Live Data Technologies

7

1 Comment