Senior Engineer Career Development Videos, Forum, and Q&A

I have been contemplating this switch for a while, but have concerns related to the following:

1. Are TPMs more prone to lay-offs?
2. How tough is the switch from TPM back to SDE in case I don't like the TPM role later?
3. Are TPMs less respected than SDEs? I have this fear that this switch might be career suicide for me.

1. What are the things you can suggest to reduce the turnaround time for onboarding a new engineer within the team?
2. What are the things that can enable them better?
3. How does this differ based on the stage of their career at which the new hire is in?

Hello, I have 3 years of experience and I'm an SDE II at Amazon. The Q1 promotion results are out, and I'm surprised to see many fast-track SDE III promotions. It seems to me that when the time is right and stars align, SDE III promotion can be quick, and if you stay in one team long enough, it wouldn't be hard to get to SDE III.

80% of my team are SDE IIs, and I don't see my possibility of SDE III promotion in the next 2 years unless:

1. I find some big opportunities that bring huge revenue to the organization
2. There's a major reorg, and I'm assigned to a new team, and the new team expands
3. My current team shrinks for some reason, I stay, and my team grows again. Interestingly, my team's senior manager and 2 senior engineers actually fall into the third bucket.

What do you think? Should I just relax, keep pace, and grow my skills, hoping for a promotion by job hopping when the market recovers?

What should I think about and focus my efforts on when I get a project and a role that's of (1) bigger scope and (2) tighter deadlines than I'm used to?

Context

A reorg has suddenly thrust me into the TL role for a very high-profile project on a new team. This project is part of OKRs 4 levels up the chain and has the eyes of several director level people across different functions. From what I've heard, this project already suffered from "too many cooks in the kitchen" syndrome, and on top of that, this project has delivery date set in Q3, which is quite aggressive from our org's standards.

I've landed in this position because I was transitioning to this team prior to the reorg, AND the EM/TL/PM/2 L5s has been reorg'ed out, and they needed someone who had previously TL experience and was willing to do it.

I've previously TL'ed a team of 4 people, with important but "normal" priority projects. This is clearly a great opportunity for me, but I am afraid I'm not ready to handle it and I'm at a bit of loss as to what I should be focusing most of my effort on. With the tight deadlines I have, I feel like every day will be a battle so any advice on how to approach this will be appreciated.

I have one other L5 supporting me who I trust very much and a new EM who's rumored to be very good. We currently have 4 SWE including me and we'll be getting more at least 4 more engineers, with lots of adjacent teams helping out. I do also have good standing and connection in the org overall and I know how to get a "normal" project in our org over the line (I did an in-org transfer).

What I'm thinking about right now

1. Knowledge Transition: since a lot of critical members of the team are leaving and I am taking over, I feel the biggest priority in the near term is to absorb as much knowledge from them as possible. So far, they have some prototypes, and I wanted to get my hands dirty, so maybe I should focus on is to understand the work that's been done really well, and the design choices that's been made already?
2. Gather support: I feel like biggest personal risk is that I don't know how to show up in higher-stake meetings with directors. Is it any different? Where do you all see the risk is?
3. Enable the team: I know the biggest responsibility I have, more than anything, is to make sure the team is able to work on the project and help us deliver this. Aside from the L5, I don't know a lot about the people. I feel I should putting my focus on ensuring they are as successful as possible, not focusing on my own technical knowledge as much, for us to succeed. Is that a good way to think about it?
4. Self-management: I anticipate I'll be very stressed and pulled in many directions. I already feel this way. What are some tools I can leverage in "crunch time"?

I am recently joined Meta as E5 software engineer machine learning generalist. Before Meta, I was machine learning engineer at a semiconductor company with not much tooling and pressure. I am in a completely new domain and in a fast-pace software company. What do you suggest to ramp up quickly and survive the first performance review?

I am curious if there are any strategies or techniques for better problem understanding. Personally, I struggle with comprehending problems, whether they are coding or business related. I often need to read through the problem multiple times to fully understand it, which may be due to my attention span. I sometimes feel stupid, but I am confident that there are techniques I can learn to improve my understanding of problems without belittling myself.

I have realised over the years that I have gained good amount of technical knowledge but I lack great communication skills (in terms of expressing my thoughts). This was okay till I was working as software engineer as my task involved more of coding work which does not require explaining things to large audience. Now as a Senior Engineer my task revolves around making design choices, explaining pros/cons of selecting an approach etc. I realised that even though I am confident on my technical approach, I sometimes fail to express myself and the approach in the right way during the discussion which led to times when my approach is discarded and others as selected as they express themselves better. I need some suggestions on how to improve on this aspect as this will be crucial part going forward in my career.

I am an engineer in my 30s and have heard that unlike a doctor/lawyer, who become more valuable with age, it's the opposite in tech. I've also heard getting on the manager track is a way to prolong your prospects (although this isn't necessarily the track I'd want to take). Curious on your thoughts on this topic.

Hi all, I'm prepping for a behavioral interview and have gone through the courses on behavioral interviews and communication. They were both super helpful, so thank you for that!

I was wondering if anyone has developed any ideas for how to respond to a great weakness. Often, it feels like people use this as an opportunity to humble brag (e.g. "I don't take enough breaks", "I can fixate on a problem too hard", etc.). Maybe these are terrible examples...

In the past, I've gone with "I don't multitask" because I mostly try to focus on one task before moving on to another. But I also don't want this to land poorly when interviewing at a startup.

Any thoughts or suggestions?

Hi there, I'm a senior engineer and I'm looking to apply to startups. I feel like this is a different ballgame compared to working with recruiters at big tech as there is no resume. For example one of my top choices has a job posting that simply asks me to submit my linkedin, github, or website link. How can I stand out?

Many of their engineers are on linkedin, so I can try to start the conversation that way.

Their backend is golang, so I've been working on building backend golang projects and putting them on github, as well as making youtube videos about my process. When I feel like I have enough of a portfolio, I could apply with my github link.

I do use their product, so maybe there is something I can do with that. Maybe I could make a simple website where I introduce myself and link to everything - github, linkedin, live demos of my projects, etc.

Any thoughts? Thanks.

I've been working as a Sr Fullstack Engineer for 2 years at a Series B startup. I've never received negative feedback, actually, I thought everything was fine until last week. My manager told me that I need to improve my Problem-Solving skills and ask better questions, she kind of implies that I'm a candidate for starting a PiP.

I agree that I struggled in the last 2 months (they switched me to a new project where I'm the only engineer and my manager only has 20% of her time for me), it's been super challenging but I'm trying to make it work. That means that I'm putting in more hours than I should frequently, and I'm starting to feel demotivated and depressed.

Honestly, this feedback took me by surprise, as no one told me anything about my performance during the last two months, I thought that even when I was struggling, they were fine with it because it's a new project and I'm basically on my own and no one is there that I can reach out to for help.

• I have ~6 years of experience and I come from a non-traditional background.
• Her feedback is vague, she says that I need to improve my backend skills, but she hasn't told me exactly what's lacking. "backend" is a big word.
• My manager told me that I should think about how to get better and that is on me to come up with an improvement plan. This feels wrong to me, isn't that her job as a manager? how can I create a plan for myself when I don't know what she wants to see from me?

How can I better navigate this? Should I start looking for a new job? I like my job and it would be sad to leave.

What do you think?

thanks.

One of my colleagues from university recently completed his final interview round with SDM & Senior SWE. It has been five business days since then, but he hasn't heard back about whether he was selected for the role. He mentioned that the interview was supposed to be with HackerRank but encountered issues, so they used Google Docs instead. He said the questions were exclusively on basic Java and little bit of algo. He completed all five questions, except for one where he didn't notice a bug in the line, and another where his syntax was incorrect, although his logic was sound. His recruiter has been consistently responsive, which I told him is a good sign. I want to know what is taking them so long, whether they are considering rejecting him because of his mistakes or if they are planning to give him an offer.

hi,

I just started. I've never been at a company this big. I have worked at a 1000 person place before it shrunk (it grew from 3-500 while I was there) and 65 and 500 person shops.

How do you suggest I ramp up? It's so many people and so many layers of code and tech. I have a good amount of experience in data/ml and also eng. I don't think I'm a 10x engineer but I am pretty proficient at getting things done.

What should my plan be even with holiday slow down coming? People are super nice and I don't feel crazy pressure to ship something rn but I put a lot of pressure on myself and want to do well.

I also know code quality is even more important at bigger companies trying to deal with scale. How do I make sure I can keep up?

I know Alex has talked about his experience mentoring 10-20 folks at once and handing out work to people as he went. Videos have talked about "decentralized power" where you figure out how to do something really well and then hand it off to someone else so they grow AND you grow by managing it.

I'd love to hear more folks' experience about how this has gone! I imagine there are some stories where this has been an easier process than others. For instance how have you handled a scenario where you hand someone something and then they dropped the ball because they were too busy? Or what about a scenario where you had a clear vision but early on during handoffs you didn't have a system in place to communicate all the details that you knew but they didn't - how did you fix this?

I'll also share my two cents on this one - hope to discuss more in the comments!

Hi,

I got promoted last half to IC5 and have been leading impactful work streams within our team. I am enjoying my new role and work. In our last 1:1, my manager asked if I wanted to lead a very high priority org level initiative that has impact across multiple teams and suggested this could be a potential staff level project. While this is a great and unique opportunity for promotion, I am also nervous about taking this up because:

1. I am scared this might be more challenging than I am ready for and failing this would put our Org's key launches in risk.
2. I just got promoted and didn't want to actively pursue promotion as I wanted some time to settle in and become a solid IC5 first.

Wanted to get your thoughts on this and what you would do in my position? And if I say no, should I be worried about my manager passing me up for potential opportunities in the future? Thanks!

Background Context

About 7.5-8 YOE, worked at a F500 before and a med tech startup before that. I'm an iOS Developer to be more specific.

I recently joined Apple as an ICT4/Senior SWE, and this is my first time joining FAANG. So far I’ve been assigned a couple of basic tickets which I landed ahead of schedule, and my manager is unsure of what I’ll be focusing on as Apple is wrapping up its last week of feature dev for the year.

I am extremely stressed. And honestly, for no reason other than I’m placing this stress on myself. I feel like I need to prove to my team and manager that I am in fact a senior level engineer, but since I am already at the level I guess there’s no need to? My colleagues who are mostly all a level below have been on this team for years and obviously can code circles around me. What I’m failing to find is what Rahul and Alex call “the engineer who everyone gravitates towards” on my team. I don’t think we have a dedicated Staff Eng, but rather a few senior SWEs (and even that I’m not sure of since everyone’s title is hidden), and honestly I have no idea what the expectations are of me, and I think that also attributes to my stress levels.

My manager says to just sit tight and has given me a few tickets that are supposed to help my designated Apple buddy - who has been amazing btw - and these tickets are fine and all, but I guess I’m just not sure if I can actually perform at the senior level at FAANG. From all the videos on Taro it seems like at the senior levels there’s a lot of leadership and design going on (which held true at my last company), but frankly in the past couple weeks I’ve been here, I’ve only seen engineers across all levels chugging out code as fast as they can (maybe that’s something specific to Apple).

Not sure if Apple just values "solver" archetype or if this is normal and that it's going to just take me a few months to ramp up and get used to everything. I think there's also quite a bit of imposter syndrome going on - I know I deserve to be here, I just need time to deliver more work and for my manager to give me some feedback.

I know I'm very fortunate to be in the position that I am, but I just want to take care of my mental health while doing the past I can to make sure I'm taking care of my career.

I’ve been e3 for about two years. my manager put me for promo last two halves but it didn’t go through .(due to a bunch of reasons which are ambiguous , the feedback I got both times was - you’re doing 4 work but we have a quota) I believe there was some politics involved but that’s water under the bridge.

I’m going to reach e4 end of this half. I’ve lost trust in my management chain. I do think my team may have good opportunity and everything else is good but I don’t think my manager is invested in growing me.

I’m very ambitious and would like to get to e5 asap. What would be good ways to set myself up for success?

I’m a female engineer (E5) at a Big Tech company. I worked closely with a male colleague on the same team for a while. He’s also E5. After our team’s manager resigned, there was a re-org and we ended up on different teams. His team had some attrition, so he recently asked if I would like to join his team. I’m happy with my current team, so I said no.

Over time, there’s been a growing undercurrent of very personal questions and crossing of professional boundaries.

Some questions he had asked me (he asked these very aggressively and kept pushing for answers when I gave hand-wavy responses to some of them):

• What did I do with my company stock? How much did I sell? Where did I put that money? What’s my financial strategy? We both joined pre-IPO, so our stock was worth a lot at one point.
• Do I own a house? Where is it located? When did I buy it? How big is it (square feet as well as number of bedrooms/bathrooms)? How much is left on the mortgage?
• Do I have a boyfriend? Do we live together? When did we meet? How did we meet? What does he do for a living?

Moreover, he keeps asking me to meet him in-person. Back when we were on the same team, I had skipped our in-person offsites due to COVID worries. I’ve never met him in-person, and am now extremely hesitant to. My spidey senses are going off.

He also asked me to communicate via WhatsApp instead of our company slack. Then he sent me a TikTok video with a sexual innuendo. When he recently asked me to use a non-company Zoom account to zoom, I declined and said that I don’t want any more sexual jokes. When he asked me if I’ll report him to HR, I asked him to keep things professional.

We’re in the same org, so I may need to work with him at some point. How do I enforce professional boundaries here? I don't want to go to HR unless absolutely necessary.

I'm working on myself to perform like a senior software engineer at a FAANG company, and by doing your courses and following you on youtube, I understand that being a good at debugging is one of the greatest qualities.

But I am facing couple of problems.

• I work in a project where the technical debt is huge, the documentation is complicated (sometimes in code, sometimes on google drive, sometimes in the form of an algorithm written in French by a non-technical person).
• Only people who have been working with code for 3 years or more seem independent (And they only have time for themselves), thus, many of us sometimes feel lost.
• A lot of money has already been invested and it is in production. So no time to rewrite the services, where more than 100 people contributed.

Do you have any advice or steps to deal with this type of problem? I know that among the FAANG there is a 0% chance of having this case, but still, any advice will mean a lot to me.

I’m considering leaving a startup because of 2 things I’ve seen on Taro:

1. faang+ as a long term investment in your career
2. .

2019 Goal of Joining a Startup

• Learn a lot about how to be a good software engineer

• Be an early employee at a startup that makes it big

• Quickly become an Engineering Manager because I like working with people, helping others

2023 Thoughts on Staying as an Eng Manager or Joining Big Tech

• Dream of being an EM, is happening on small start up scale with a growing number of reports who like my management so far

• The dream is to be early at a unicorn and that is close, but

  • The new standard should be 10B not 1B

  • Doing this with a first job is not necessary and high risk

• In 2-4 years I’d likely still be a engineering manager from a no-name startup

• L5+ engineer in big tech may fit well with my personality right away based on Taro, where I love collaboration, helping people, product and technical challenges

  • I like not just spending 80% of my time heads down coding and that may be possible and expected right away in big tech, no need to be a manager

• Getting a 2 FAANG+ badges on my resume over the next 4 years would be more way more worth it than even a million dollar payout from a startup

  • Could have many doors opened for high level roles at startups OR faang depending on what I feel like at the time

  • Big tech stock offer may also easily be worth 1M in 4 years

Priorities 2019

• Supportiveness of team

• Growth opportunities

• Company prestige

• Maximum outcome (Risk)

• Compensation

• Company ethics

• Product space

• Technical space

• Work-life balance

• Level/title

• Benefits

• Location

• Stability

• Remote work

Priorities 2023

• Supportiveness of team +0

• Work-life balance +7

• Compensation +2

• Company prestige -1

• Growth opportunities -3

• Stability +7

• Company ethics -2

• Remote work +6

• Level/title +1

• Benefits +1

• Location +1

• Product space -5

• Technical space -5

• Maximum outcome (Risk) -10

Taro priorities video is

Startup Stats

• 150 people, 25 engineers (doubled from a year ago)

• Fall 2021 had 50% investment at 250M valuation

• Dec 2022 450M valuation

• Revenue has since doubled in last year to 125M

• Profitable per years with 20% gross margin

• Growing industry

• Not venture backed, so not expecting 20x growth

• Estimated in 2-4 years to sell for 1-2B

How to evaluate a startup video

Current job stats

• Team lead for a year after 2.5 years as Software Engineer

• 0.1% equity, 100k cash

• 18th employee, 4th engineer

• Dream of being an early employee at a unicorn, seems close

• Would lose all stock if I leave before acquisition/ipo

• Biggest point for discussion: ***2-4 years of being manager at a small startup may not qualify me to be an EM in big tech***

FAANG+ Offer

• L4 equivalent

• 190k cash, 350k stock over 4 years, 60k sign on bonus

• Work life balance is supposed to be great

• Great food, big tech lifestyle that I’ve always heard/dreamed about

• Would work to be promoted to L5 in 1-2 years, then manager a year after that.

• Being a new person at a fresh company sounds very exciting now, I know the business fully and the tech stack of the current place to the point where many things Ive see before and feel stale/boring

Questions

1. Based on my write up about values, priorities, liking collaboration, would I like being an IC L4 coming from being a manager where I have solid tech skills but strong soft skills that I enjoy using.

2. If I stay at the start up would I be able to get a big tech EM offer with 3-4 years of management experience at the start up? Note this question shows what I’m learning now as a manager.

3. Should I down level myself from L5 to L4 if I think I could get the offer at L5 but am not sure about the certainty of success? (Question asked separately )

Sometimes people forget to follow up on their Action Items from meetings. They sometimes misremember meeting decisions as well. To mitigate this, I usually take detailed meeting notes in Google Docs and tag people on the Action Items they're responsible for. However, we don't always have meeting notes (e.g., for an ad hoc situation). What are some best practices for avoiding misunderstandings?

I just finished up my final technical round (went well) and the recruiter reached out wanting to chat about salary expectations before the offer stage. During my initial call with the recruiter, she did ask me about salary expectations. I deferred by saying fit and potential impact are most important to me and that I'd like to defer until I learn more. Now that I've already interviewed, I'm not sure how to handle the conversation with the recruiter. It seems wrong to give a number before getting an actual offer, but at the same time, my initial reason for deferring talking about salary is no longer valid because I've already gone through the interview process. Any advice on what should I do here?

I'm an Android engineer working on an infra team, and like every other Meta E4, I am working towards the E5 promotion. Because of this, I'm spending a good amount of time building up the non-coding skills needed for the people/direction axis, doing things like XFN alignment and project management.

My question is how "all-in" should I go developing these behaviors: How much of an engineering excellence commitment do I still need to maintain? How often should I still be landing diffs?