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

I know this is a broad question and depends on personal choices. I'm wondering if you could provide some insights on choosing between IC and manager paths.
What are the factors to look into?
How fast or difficult is career growth in both the paths?
How do the work-life balance and day-to-day life look like in both these paths?
My eventual goal is to start a startup. Does having managerial experience help here or being strong senior/staff IC help here better?

I have a follow-up coding interview with Meta after the Onsite rounds. Under what circumstances is a follow-up round requested? Is it because there were some strong hire rounds and some weak hire rounds? I am looking to gather inputs/tips on how I should be preparing for this interview. Would this interview be different from the other coding interviews that have already been completed?

I am thinking about finding a position at another company. But I am concerned about how to find something suitable. I am considering moving because I would like to work and learn at a company that practices better code quality: better separations of concerns, better testing. I've learned recently that code quality corresponds closely not only to speed of development, developer happiness, but, also stress. I don't know though how I would know about code quality from the interview process. I can imagine maybe asking multiple engineers from the company what they think during the interview process. Maybe ask engineers that I've worked with before from the company. Also, some companies may be reputable like Google. Or maybe some famous engineers work there like ThoughtWorks.

I am currently a Staff Engineer at a company, and I've worked for almost 6 years there. I've also been promoted at the company. I think there are factors that are important for me that keep me there. A flexible vacation policy that is actually flexible as I've usually taken about 5 weeks off a year, commitment to remote work, flexibility to set time off during workdays. On the other hand, even though I am one of the top committers to our code repository, I am not sure if I am getting credit for that here.

One thing that worked really well was that I started at this company when engineering was around 30-40 people. That meant work time was stable unlike an early startup, but the company was at an early enough stage that I really got to know a large portion of the code base, over multiple functional areas, before the code base kept growing and new teams were formed.

Regarding programming language / framework, I would prefer Scala. I also would like to learn ZIO. But I think that's secondary to the factor regarding code quality.

Could you give me advice as to how to search for jobs given the different factors that I've listed?

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?

Hello folks,
I have an upcoming Staff ML Eng. interview with Meta. Could someone please suggest some good resources for behavioral preparation? I have finished the join taro course.

I’ll be starting as an E6 at Meta, working on internal tools. Currently, the headcount is really low, and people only have 60 days to match, so I decided to go with the first team I matched with, even though it’s not the most exciting option.

I’m committed to doing a great job in this role, but I’m a bit concerned about the potential impact I can have and how that might affect my performance reviews (or get me PIPd). Is this something I should be worried about? Any advice on how I can maximize my impact on a team that might not be seen as highly impactful?

I have been with my current team (a platform team) for about almost 3 years now, and I believe I have build good relationships with others in the org. I am thinking about projects that can get me to E6.

So far, the projects that I come up with, feels underwhelming after talking to more senior IC. The IC either think there the ROI is not high enough, or the project is too much of BE. For other ideas, it feels like that I would have scope collision with other ICs. I sometimes feels too tired to churn through more ideas. I am not sure if this is normal, or if I would be able to succeed in my current team to get to E6. How would you decide it is time to change teams?

I just watched . Great material! In a couple of session, it was mentioned that Infra teams works differently, e.g. there is not as much XFN. Can you shed some light on how Infra team promo works?

Hi All

Some companies have a project deep dive interviews as part of the hiring loop interviews and I was looking for any good resources about how to structure and be well prepared for these interviews. Appreciate any pointers.

Note: I have seen this predominantly for Staff+ positions.

Thanks

Rahul

Put on an exciting Staff level project for the last 6 months. Now, asked to make a tough choice - move out of Org or stay in current Org and give up scope.

Pros of moving:

• Scope: getting multiple jr level engineers to carry out the scope I created.
• Exciting product.

Cons of moving:

• Current manager turned down the scope expansion.
• Have built relationships within current team. Enjoy working with them (more familiar)
• Less depth AI/ML work but more product heavy (which is high impact as well but slightly less interesting from ML standpoint)
• Lots of unknowns with new team - unknowns beyond staff scope IMO

TLDR; What would others in the same situation recommend? From taro courses, Option 1 seems better. But there are unknowns especially with current manager refusing the offer.

Recruiters often mention that a staff engineer interview involves a deeper dive compared to a senior software engineer interview, but it's not clear how much deeper it needs to go. Are there any resources that can clarify this?

Hi

I am thinking that if I also start to show the basics of a staff engineer, it might be helpful to reach a senior engineer status.

Curious to hear about what archetypes you think AI teams follow.

For ex: I think Specialist, Tech Leads are pretty common for AI teams. But we probably have a few archetypes like fixer that are slightly different in the skillset (dig through data, analyze common usecases).

Did meta have any additional archetypes for AI eng types?