Career Advice About Walmart

I've received a verbal offer from Meta for the Android role and I'm in a team matching phase right now. I've a couple questions:

• My recruiter mentioned that team matching is taking a lot of time these days and suggested me to take a team that's available and later could think of changing the team. What should I do here wait for the right team or take a team that's hiring right now?
• Does anyone have any recommendations for teams at Meta which are layoff proof, has interesting and promising projects coming up and a good mobile engineering foundation?

I received a verbal offer from Meta for the Android role and I'm in a team matching phase. Recently team matching has been a lot of struggle and could take weeks or maybe months. Last year a lot of hiring managers posted on LinkedIn about hiring for roles and I did exchange a conversation with them. Is it wise to ask the hiring manager on LinkedIn about open roles in their org and then telling my recruiter about it or I should go with a team that the recruiter helps me to connect with?

Hi joining as a senior software engineer in a company where the tech stack is totally different. How to adopt well so that I can do well in the job as well as go to next step.

I'm going to leave my current company in a month as I have accepted an offer from another company and I'm currently working on the H1B transfer step. H1B transfer should take three weeks at the most. Recently my org had a restructuring and my manager has been changed leading to newer project and new team member and nowadays I spend most of my time onboarding myself onto the new project. I have couple of questions here:

• What's the right time to inform the manager about my next move?
• Should I give my 100% into the onboarding? I feel low-key guilty on adding more burden to the team by doing work which will add no value at the end.

Hey folks,

I just finished Alex's Master The Data Structure and Algorithms Interview course. One question stayed with me when Alex went into how important it is for discussion on edge cases and alternate approaches in the Getting To The Next Level section. If we know that the interview will last for another x minutes when we get the coding question, which one of these options should we take?

1. Completely go berserk with edge cases and alternate solutions that you can potentially think about - and have an engaging discussion with your interviewer about the tradeoffs associated with each of the approaches, to the extent that, the interviewer does not care to see you write code (they conclude you're a DSA ninja)

2. Just take the x minutes to limit your scope, write your plan, and write the code.

I think option 2 is more prudent if x <= 25 minutes but otherwise, I will go with option 1. Having said that, I know Alex talks about folks who did this when he was the interviewer. Was this for x > 25-minute durations too?

Thanks!

When it comes to software engineering or landing out features or doing tasks I feel I excel in them but when it comes to showing my task to a wider audience I don't think I do a great job at it. Does anyone have any tips on how to do effective demo of your work?

I'm specialized in mobile engineering anything specific to it would be very helpful.