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

Hello

TLDR: I started a new job in September last year, and within three months, I was placed on a Performance Improvement Plan (PIP) with impossible tasks to be completed within four weeks, essentially setting me up for dismissal. Two months prior, I had been seeing a doctor for health issues, and they advised that the PIP would likely worsen my condition. The doctor recommended taking Short Term Disability leave to focus on my health. The tasks I was assigned for the PIP were eventually completed by two engineers (1 staff and 1 Sr) over four months. My Short Term Disability leave ends soon, and I'm unsure whether to return to my old job.

Question for this community:

1. Is it a good idea to return to the same job after being put on a PIP and taking medical leave? (HR informed me that the old PIP would not be in effect upon my return from Short Term Disability leave. However, I'm unclear on how this process works).
2. I want to change teams upon my return; is this something I can negotiate with HR before trying to go back?
3. I like the company and its culture but ended up in the wrong team with the wrong manager. Is there a way I can remain employed at this company but join a different team and manager?

More Context: My manager was present during the hiring interview, where I clearly expressed my desire to move away from a particular tech stack. I was highly rated in the interview and received a generous offer, which I accepted. However, once hired, the manager assigned me to a project in the same area I wanted to avoid. Given it was a high-priority project and my first assignment, I reluctantly accepted. 1 month into the job, I faced a personal emergency requiring a few days off. I shared the reason with my manager, who seemed understanding at first. After that, the manager's behavior changed drastically. They began assigning more work, constantly switching me between multiple issues and projects, and bullying me in meetings. Despite working overtime (12-14 hours/day) to meet expectations, their attitude worsened. This was the worst manager I've encountered in my 14-year career who had unreasonable expectations as far as ramping up on the projects is concerned and it almost seems like I was hired to be fired in this situation. Note: This is not at Amazon.

Any other pointers would be appreciated. Please help.

Part 1: Before Joining an organisation

1. How can one identify the best kind of organisation to join at different point in one's career? I understand that the advice to this question may not be a prescription for all, but how can one identify places that would help them to maximize their learning and growth. For several other people, different parameters may be important for them as well such as work-life balance. Personally, I feel that WLB is dependent on a person more than that on the organisation. Thoughts?
2. Quite often we feel that growth may be fast paced at startups, but there can be startups that do and don't promote the growth of a person. Given that there is no list out there to check, how can one make the best suited decisions for their career, not landing at a place they should not be at? What kind of research can a person do before joining an organisation?

Part 2: After joining an organisation

1. Given that a person has joined an organisation, what are the kind of signals that they can identify to see whether the organisation is supportive of their career growth and is indeed the right place to be, for them?
2. On several anonymous portals, there are people from the organisation that will talk poorly about an organisation when things are not going good for them. Managers can quite often paint a really rosy picture about the place. How do you identify the honest signal from the noise all around?
3. If you find an organisation not good for you after you join there, how quick is it too quick to leave? How much time should you spend there before you can make a judgement about the same?

I worked on backend for 10+ years and was a Tech Lead before switching to iOS for the last 10+ years. I was offered an E6 position at a Big Tech company, but I asked to be down-leveled to E5 due to imposter syndrome since I mostly worked at smaller startups and didn't know what to expect. When Leadership later found out that I have backend experience, they started pushing me to do backend. Is it easier to get to E6 doing only iOS or doing both iOS and backend? I'm much faster coding iOS than backend since I know the Xcode shortcuts, a lot has changed in backend over the past decade (e.g., AWS, Kubernetes, etc.), etc.

1. What are the key relationships you need to develop to increase your influence within the organization?

2. How can you demonstrate your expertise and value to others without stepping on toes or appearing overly ambitious?

3. What are the unmet needs or pain points within the organization that you can address to gain credibility and visibility?

4. How can you leverage the principles of reciprocity and mutual benefit to build alliances across different teams or departments?

5. What communication strategies can you employ to effectively share your ideas and persuade others without formal authority?

Fitting into an Established Organization:

1. What is the prevailing culture within the organization, and how does it manifest in day-to-day operations and decision-making?

2. Who are the key stakeholders and decision-makers, and what are their expectations for new members of the organization?

3. What informal networks or communication channels exist, and how can you effectively navigate them to build relationships?

4. How can you demonstrate respect for existing norms and traditions while also introducing fresh perspectives and ideas?

5. What initiatives or projects can you undertake that align with the organization's goals and also allow you to showcase your skills and contributions?

6. How can you seek out mentors or advocates within the organization who can provide guidance and support as you integrate into the company?

1. How do pull requests and pull request comments look like with an increasing level of seniority?
2. Are pull requests for senior engineers not expected to have any comments for improvements? If yes, then what kind of comments should be there?
3. Also, have seen some principal engineers not sharing their pull requests as they are quite high in seniority and merging it directly. Do you recommend that? If not, who should review PRs for very senior engineers if the team does not have engineers at that level?

I'm contemplating moving from Canada to the US, hoping to secure a Staff role. My sole reason is money but I do not want to sacrifice work-life balance or mental health for that. A few extra hours of work each week in the initial few months of transition are expected and acceptable.

1. Is it a pipe dream to expect work-life balance at Staff+ roles that pay $0.5mil/year?
2. How stressful are these roles? I understand that ability to handle stress varies by individual, but it speaks volumes if most folks at Staff+ roles feel very stressed.

I want to take an honest shot at tech entrepreneurship in a few years. As I'm working on developing behaviors expected at Staff-level, I want to specifically focus on skills which will help me become a good entrepreneur down the road. Feel free to mention skills that map to any other level or where level doesn't even matter, as long as they relate to tech entrepreneurship.

I’m an E5 on a platform team at a Big Tech company. I'm under aggressive timelines to create a proof-of-concept (POC) for a partner team. My skip-level emphasized the importance of this POC as well as its timeliness to me.

Our team's E6 is coding our platform infrastructure and is slipping his dates. The E6 said his infra code should be production ready in 2 weeks, but claimed there should be enough there to unblock my POC. I tried to forge ahead, but my POC is now delayed because I spent so much time trying to work around the deficiencies in our platform infrastructure. I eventually decided to prioritize some other parts of the POC to avoid losing more time while the E6 is taking his time with the infra work. How much of this should I communicate to our partner team's stakeholder? I'm hoping that I'll be able to hunker down to get the project back on track without slipping our dates. Another E5 on our team told me that he doesn't like to air our team's dirty laundry outside our team, so he usually says everything is fine until the last week of the project when he suddenly flags delays. Is this a good strategy? Or should I be honest and upfront with cross-functional partners external to my team?

After 10 years as a full stack SWE and eng manager, I pivoted into AI while working at Shopify, and was recently laid off as Head of AI at a collapsing pharma startup. Title is nice, but I only really have two years experience in ML. While it is high quality experience (training and shipping models and LLM apps at web scale)-- I'm feeling a bit scared. I don't have a ton of savings and two kids so I need something soon.

I'm deeply passionate about language models, for the first time in my career working with a particular technology has felt like a real calling-- staying up nights and weekends just to learn and build. My first research paper ever was published at NeurIPS last year.

However, I'm feeling fairly unconvincing as an ML engineer after the layoff. Probably the perfect role would be something in between web and ML. So now we're at the question:

Given that I'm pretty desperate to land anything (3 mos runway before pulling out of investments, wife really against this) I'm wondering how to approach my search:

1. Go all out for AI Engineer Roles (passion forward)
2. Go for senior / staff web dev roles (safer, maybe, given 10+ yrs exp)
3. Go for 1 or 2 plus eng manager roles
4. Go for all of it at once

Some confounders:

I have referrals at Google and Microsoft, but don't want to burn them on ML roles if I'm obviously unqualified having only 2 years ML. I know I can absolutely add value wherever I land, but these feel like precious gold to me, and I don't want to get tossed out of the running for playing it silly. I can likely get some at Meta as well, but again, I don't want to play myself going for stuff that's just inappropriate. This has never been an issue in the past, I've been able to land stretch roles or at least get the interview but stakes are different now and my confidence is lower.

I am a good eng manager, and would do it again, but I have a feeling it's an altogether different search. Is there a way to increase the surface area of possible roles by applying to manager jobs too-- without splitting my energy?

Anyway, its helpful just to think out loud, would appreciate any advice here. Current plan is to create 3 resumes, start blasting applications and networking to get the interview funnel spun up before the leetcode grind.

Thanks.

Any recommended resources that I should invest as part of my education budget?

I am Backend software Engineer and I am interested in moving to Staff software engineer role in future.

Currently, I hold a high senior position (~ L6) within a large tech company. At this point in my career, I often find myself grappling with the decision of whether to focus on advancing as an individual contributor (IC) or transitioning into a management role.

Although I genuinely enjoy mentoring junior engineers and helping them grow in their careers, I have a strong aversion to certain aspects of management, such as the frequent meetings that come with it. Given my introverted nature and my passion for staying closely connected to technology, I don't believe that a management role would be the best fit for me.

Conversely, the idea of progressing as an IC to roles like Principal or Senior Staff can be quite daunting. I grapple with feelings of imposter syndrome, wondering if I can meet the necessary standards and I am concerned that it might negatively impact my work-life balance.

I would greatly appreciate any advice or insights from the community regarding this situation.?

I am a Senior Software Engineer at a big tech company, and I was reached out by a recruiter at a big-tech equivalent company and decided to give it a shot (also for a Senior SE role). I'm in the final interview stages and expect to receive an offer soon.

My recruiter said I've received excellent feedback overall from all of the interviews. I honestly believe that I would be more suitable for a Staff-level role given the work they are planning to do and has a close alignment with what I'm doing now (working towards a Staff role).

I have a few days until I receive an offer; I'd like to know whether I should kick off the discussion now or post-offer?

I'm an E5 at a Big Tech company. My team's working on a very ambiguous project. 3 opinionated, vocal engineers (2 E6, 1 E5) tend to sidetrack our brainstorming discussions by playing devil's advocate to shoot down ideas. How do I drive these meetings forward with this dynamic? We often rehash the same discussions over and over. When we're close to reaching a decision, oftentimes someone would throw a wrench into things. Moreover, some engineers require upfront planning and want to finalize all the details before committing, while others prefer to defer the details to future milestones. Both my manager and team are getting frustrated, but are unsure how to fix this.

I'm an E5 iOS at a Big Tech company. Our team's E6 backend and E6 iOS tend to dominate our team discussions, often talking over each other. I get the impression that the E6 iOS wants to be the smartest person in the room and enjoys micromanaging all the details, but the E6 backend enjoys challenging him. When I proposed a solution to one of our project's challenges, the E6 iOS quickly shot it down but could not propose any alternatives. The E6 backend challenged the E6 iOS to explain why my idea wouldn't work, but the E6 iOS just talked in circles. It seemed like the E6 iOS just didn't like it because he didn't come up with it himself. How do I avoid making the E6 iOS feeling threatened? I'm a bit hesitant to contribute to team discussions due to this dynamic, but my EM wants me to contribute more.

What is the role of Staff Engineer at a early stage startup where infrastructure is on an average setup? In terms mobile application it is standard app with migration scope to react native but there are no takers for migration at all (only product release need)

Here how can staff engineer play a role and how to deliver product and engineering goals with awareness to large eng teams?

I joined as IC5 about 2.5 years ago. So far I've done well, EE and GE, probably EE this year - at lot down to the great advice in this community. 1 year ago my previous manager put me up for low confidence promo which I didn't get and now my new manager is doing the same this cycle.

I value WLB which is currently ok to decent and as such I've never really asked about promo to either manager, just general growth areas. Also I've been quite put off IC6 by reddit / blind, I've heard a lot of second hand stories of stress and higher chance of PIP at that level due to higher expectations and smaller higher caliber pool in the stack rank. I need to avoid being in the bottom 15% of a pretty exceptional group.

One other datapoint about me is that I'm a somewhat anxious person and I cannot simply land another comparable tech job since I'm remote and based in EU - hence my appetite for risk is probably lower than average when compared to my peers.

I'm looking to hear some stories of people who have made the transition... what sort of impact did it have on your WLB and stress levels? any regrets? was the additional comp worth it? Has it gotten easier over time?

Finally my manager tells me that promos are lagging and no major changes are needed (except additional org contributions) Was this true in your experience?

Thank you

I completed my final rounds at Meta. I heard back from the recruiter on the same day pretty quickly that they would like to set up a call and asked for Meta references. Is this a good sign? How important are the references?

How much of ML experience is needed/looked at during Team Match, if particulary interested in joining a team doing ML? Are Hiring Managers particular about this requirement during TM? This is for a E5 and E4 levels.

I am starting to prepare for system design questions. I would like to know if anyone has thought of grouping/categories when it comes to similarity among those problems?

For example, ecommerce (amazon) and service delivery platform (doordash) based problems has common trait of search, one can easily use the same solution across both the systems (to search for the products on amazon and to search for restaurants in doordash)

Also is there any list of must know system design problems for interviews at senior/staff level?

Direction: Strategy formulation and road mapping are key, along with influencing and collaborating with other teams. How I could promote proactive inclusion of ideas on other teams’ roadmaps and engaging with leadership to drive product decisions. It’s also important to consult with managers to identify tasks that create the most impact, whether they are big or small. Engaging in strategic and road mapping discussions can be highly beneficial.

I have Staff interviews lined up with FAANG companies and would like to learn from the best resources out there. What has helped you the most in your journey/experience?

I am very much aligned and aware with needing to show impact or been seen as an SME to have visibility to move up to a staff level.

My question is one of logistics. How is this possible when you have more work to do than fits in 40 hours, let alone finding extra time to do these other things? For example if you have at least 30 hours of coding, 5 hours of code reviews or scoping documentation, 5 hours of meetings, an additional 5 hours of random things (CI broken, helping colleagues, ad hoc issues etc), where do you even begin to find time for these extra things? Especially when all of the above is barely considered meeting expectations?

I will also clarify that I don't want “get better at coding” as a valid answer. No matter how good you are, you still need to understand the many systems involved which can take a while and if you constantly have to tackle new areas, there's always discovery.

My question is more around how do you ask or “show” you should have time to work on other things. Whenever I would approach my manager with well thought out proposals, buy in, and even timelines the answer was always later.

I've been a Data Engineer for most of my career and my observation is that scope as a Data Engineer can plateau and therefore I see a lot more L4/5 DE's than L6+. I think it is because you don't impact the bottom line directly and regularly.

At FAANG's I've worked at so far, finding new scope can be difficult even when you are working with stakeholders: it is "easier" to scope/build a product (i.e. SWE work) and show metrics of success to add value vs building a data pipeline which may be limited to them having a reporting need for example which often isn't the case especially in a more established firm.

I moved into a partner facing DE role to help more with scope/stakeholder exposure. The highest impact project I worked on so far is influencing an internal team to change the way we measure a particular metric. This involved mostly stakeholder management and nothing more complex than SQL queries from a technical standpoint. While it was fulfilling, this is also something I 'stumbled' upon and is rare due to challenges like partner scope/vision is limited/slow (their leadership can change and therefore you projects/ideas can), technical challenges of automating things because of larger concerns (e.g. privacy, lack of infra on their side which you have no control over) and so on (you generally have even less control than an internal DE).

In my current role, I am generally able to derive projects, but (in my opinion) they are limited in scope/value: i.e. build a pipeline, deliver an analysis. Therefore, even though the projects 'ticks the boxes' for an L5, it is not really driving a 'transformation' as an L6+ would. I also directly asked my manager what are some of the hardest problems we have, and have been told we have a lot, yet, I'm not hearing or seeing them.

Given the situation, would you:

1. Move to a SWE role internally at FAANG for a more established path 'up' (not sure this resolves the scope problem especially at FAANG as I think SWE-DE's can almost be even harder to get to L6+ on because they generally lack stakeholder visibility and focus on more top down work?).
2. Seek roles outside of FAANG where the scope of the work is already scoped to L6+ e.g. Airbnb so the 'heavy lifting' has been done in terms of scope.
3. Refine your scoping strategy within you own team, and if so, how?

Note: my motivation is to thrive at work, this isn't for a promo, just incase the post comes across as promo-focused. :)