Onboarding Q&A and Videos

Hi All,

Would love to get some advice on how to ask highly pointed questions during a 30 minute conversation with a hiring manager to get the maximum info out of him regarding the team culture and the product.

Regarding my preferences...

I would love to stick fully on the Backend stack. I have experience working with Python, NodeJS, Typescript and a bit of Java, I have experience working with Infra and databases as well. I get excited working with data at scale but do not have stellar industry experience with it such that I can start being impactful on day 1.

Since this will be my first time at a big tech, I want to optimize for a decent to moderate enough ramp up time, good wlb and not being super heavy with oncall at least for my first team.

Once I get used to the pace, I'll jump around to start optimizing for impact, visibility and scope.

Here is what I have in mind for my Hiring Manager meetings but feel free to add/subtract from this.

1. Basics, what is the product/org
2. What is the team size and team structure (how many E5s, E4s etc) and tech stack.
3. What is the code velocity like on average for an E5.
4. Give me a brief idea about what the first project you have in mind for me, if not tell me about a project an E5 is currently working on.

I'm a new staff engineer at Meta, and I know that the bar is high for E6. In particular, an E6 needs to be able to have a large influence on the roadmap and team charter, leading and creating very substantial projects.

All that being said, I want to start crafting and executing that vision as soon as I can to hit the ground running, but I'm unsure on exactly how to do that with Meta's more bottoms-up culture. At my previous job, things were more top-down (i.e. leading with authority, where software engineers work on things because their manager/leadership tells them to). How do I lead the team with this almost opposite engineering culture?

Should I be focusing initially on quick wins or higher-impact, high-priority projects that could potentially take longer?

Situation:

I recently started a new position and I'm facing challenges with my manager's communication style. It's making my onboarding process difficult and I've noticed it's affecting our team's culture.

Evidence:

1. On my first day, there wasn't a structured 1:1. I received a call with scattered instructions about completing 4 PRs by the end of week 1. When I mentioned needing time for machine setup, signing up for health insurance and mandatory trainings, my concerns were dismissed.
2. By day 4, I hadn't been assigned an onboarding buddy. When I tried initiating a discussion, my manager seemed to think it was unnecessary. During an impromptu meeting, I wasn't given a chance to speak.
3. My manager suggested working during my vacation. During that vacation, I injured myself but hadn't completed health insurance formalities to see a doctor.
4. In the first week, I saw my manager confront our designer aggressively during a standup.
5. In week 2, I was abruptly reassigned to a different project without clear communication to other stakeholders.
6. During week 3, my manager had a heated debate with our team lead during standup. When I tried mediating, I was told I could leave the call.
7. Again in week 3, I was told to drop everything to complete a security training by the end of the day.

Environment & Manager:

Speaking with peers, it's clear I'm not the only one feeling overwhelmed. Our onboarding process seems disjointed and the team's morale is low due to constant shifts in priorities. This all seems to link back to our manager's communication style.

Seeking Counsel:

While I understand I'm new and might not have the full picture, I believe this issue is beyond just my experience. I'm looking for advice from:

1. Someone within the company with the authority to effect change.
2. Someone who has dealt with similar situations before.

Questions:

• Given what I've shared, how would you handle this situation?
• How can I maintain high performance when it feels like there are barriers?
• How should I approach giving feedback to my manager?
• Are there any strategies to improve my current situation?

Desired Outcome:

With your guidance, I hope to find a sense of balance and detachment, focusing on my role while navigating these challenges.

I genuinely want to make the best out of my current role and contribute positively to my team. Your insights and advice will be invaluable. Thank you in advance.

Hi all,

I am a newly hired Senior Software Engineer. I worked at FAANG before but have never been in a senior role. I am currently in week 3 of my new role. My manager gave me expectation to ramp up in 3 months but with very little further guidance. The codebase is huge with very little and mostly outdated documentation.

What do I need to do to ramp up as fast as possible and position myself for promotion to Staff within next 1-2 years? I read that there are people ramped up within 1 month into their jobs on Taro. Hope you can share your tips and tricks.

I just joined Target at a Principal level. My manager is spread very thin and wants me to take initiatives and has told me to start networking heavily in the first few weeks. My plan is to create an Onboarding doc and share it with my manager. I'm going to use this doc to manage expectations and use it to review together 3 months down the line. How can I structure this doc? What pieces of information are more relevant/vital for such a doc. Any pointers?

How does it differ from an entry level engineer to the head of engineering level at each of the levels, given the scope grows as well at each level?

• Software Engineer
• Senior Software Engineer
• Tech Lead
• Staff Software Engineer
• Principal Engineer
• Head of Engineering
• Director of Engineering
• Vice President
• CTO

How do each of the levels ensure they are onboarded as quickly as possible to have maximum impact ?