Onboarding Q&A and Videos

I just joined a new company (7 months of industry experience) and I want to make sure I can come in quickly and make an impact. More specifically, I want to become a quality contributor to the team as soon as I can.

To put this into context, the question refers more to people who have already been at the company for a while, not onboarding engineers.

In my experience working only at startups, almost all learning has been the responsibility of the employee. There is a "spike" period where the engineer is given time to come up to speed, but it has always seemed to me a bit careless for managers to just give someone a list of technologies and say "learn this."

I guess this question is really a proxy for asking: how does FAANG approach "bootcamping" engineers on a new and important stack? Are workshops, training courses, and L&D actually effective? Suppose that I am a senior engineer who wants all the junior engineers in my team to learn how to use AI assist tools like Copilot, how would I approach making this mandatory if I really think it's a technology that's as crucial as git?

Context:-

1. My team is going to work on a new project which involves upgrading a service and migrating/enabling all of the dependents to use the new service.
2. This service provides a business critical functionality for our teams and the new version attempts to solve a lot of high impact pain points with the previous version.
3. We have just inherited this service and none of us have worked with it or any of its dependents before. We have some support from the previous team that worked on this project but only in a consultation capacity.
4. This is a project that has been attempted multiple times by various teams over the years - unsuccessfully or with little progress. My perception is that it's going to be a difficult project with low-moderate chances of success.
5. There is a lot documentation but most of it is somewhat outdated. There are a lot of PRs as well but these are for the unsuccessful attempts so I'm not sure how impactful it would be to go through them.
6. The plans for the previous attempts only had internal milestones for the team and a single big-bang completion milestone for stakeholders.

Questions:-

1. How can I identify smaller, independent high-level milestones that are relevant for external stakeholders?
2. How can I come up with broad estimates and capacity requirements for the external and internal milestones if I'm not clear on what these milestones would require for completion?
3. How can I think about de-risking this attempt of the project and improving the probability of success?

How can I map out what to do in the first 90 days in a new role (staff and senior staff) and a new job (given factors like new codebase, new processes, people, and work ethics), especially when the domain and coding language are also new?

I'm in the onboarding phase. I was assigned a starter task and have been working on it. I haven’t done the work of asking questions on design choices (that part is pending).

I want to be ramped up after a week and am wondering how to spend the time. Should I go in-depth on overall architecture? Or spend time working on the codebase? Or is there something else I should do?

I'll be starting at DoorDash relatively soon, and I was wondering what 1 on 1s I should set up on top of the one with my manager. More specifically, are there meetings I should make recurring vs. 1-time ad-hoc? For context, I'm an iOS engineer.

I just started working at a new company. I am still going over the general onboarding process for all employees.

How should I go about introducing myself to the team & manager? Should I ping them on chat to say Hi & asking them to add me to the meetings? My whole team has about 16 members.

Thanks in advance!

Hey guys,

I'd appreciate some advice since I'm having the first month in my new company. So far it seems that many processes are neither formal or automated, and there's also a lot of documentation missing. In one of the tutorials and also in my discussion with Rahul, the advice was to not rush towards suggesting improvements right away. However, in my company I see a lot of room for improvement and I have some ideas on how to make things better. What would be your approach?

I'm a new engineer at Snap, and my first month here is for onboarding. My team does internal tooling, and I have my first major project already lined up.

My manager said this should take an L4 engineer 1-2 months with a lot of help from the tech lead. This tech lead is a senior engineer pushing for promo.

The stack is a mix of Java, Go, and Python - I'm a back-end engineer on the team. However, I'm transitioning from a field that's pretty far from back-end. I'm wondering how I can make this transition as soon as possible and make sure I onboard well into the team?

My question is when should I reach out to help someone. If someone new joins, and if it is clear that task might be difficult for person, or there is some context needed etc, and they fail to ask, should you help them? Reaching out early and helping might be hampering their own learning, also at risk of hurting someone's ego. But If I am in other person's shoes, I would appreciate all help so what is right balance here?

Also, should you helping be more visible or private? If it is public, other people can add extra context as they like, but maybe in private conversations, person can ask more follow up question, assuming they are afraid to ask dumb questions. To be more specifically, by public I mean team channel in slack and private would one-one chat.

I'm new to my company, so I'm asking questions to bring myself up to speed. However, something I'm wary of is becoming a burden - I assume you don't want to ask the same person every time for help. Any tips on how to figure out who I should ask my question to minimize the chance of this happening? I want to make sure I get along well with my team.

I have been on a half a year long break due to unemployment and recently secured an offer at Meta as a senior. I'm a bit stressed about hitting the ground running after coming back from a hiatus, especially because I'll be joining as a senior and am coming as a mid level engineer from a non-faang company. I have a month long break still left before my joining date and I wonder if there is something I can do to set myself up for success.

Additionally how would I go about finding a mentor specifically who has had a good amount of experience working at Meta already?

What concrete things do I say, in a conversation with my manager to "set expectations"?

Do I say something like "I would like to ____ expectations this quarter, is it sufficient to complete project A & project B?"

What if I am new to the company, and unable to contribute meaningfully to a significant project, or there is downtime when no projects are available?

Can I say I'll fix some unknown volume of bugs this quarter?

I recently joined my team, and I've been sort of overwhelmed picking up this new tech stack which may be leading to some procrastination. I literally have to Google for everything I want to write. Twitter also has certain in-house technologies, which are pretty challenging to learn. I also started working on a critical project recently with strict deadlines due to headcount shortage.

I saw this as an opportunity to make an impact and am trying my best, but I wish I had more time to get acquainted with the stack. I feel like I lost a few days last week unraveling through the ambiguity and getting context, so I didn't make progress with implementation as much as I wanted to.

I am kinda anxious that I will miss my delivery in the first project which is not setting a right impression. In my experience, there is no excuse for missed delivery and it will treated as a red flag. It's a newer company for me and my org is revenue-generating. Given the phase Twitter is going through, this project is critical and hence I am hesitant to push back on the timelines too.

I also see mid-level and junior engineers on the project moving way faster than me right now, because of their tenure and familiarity with codebase and that can be disheartening.

Lastly, should I be transparent and discuss with my manager if I feel a few days haven't been productive? I don't see any way that will help.

I see most of my colleagues ask tough and deep questions. My questions are not that great a lot of time. I am ramping up in a new role for past couple of months.

I'm mid level, new to the company.

I got assigned a chunk of a bigger project owned by a staff level engineer, let's call him X, who has worked on the product for a long time and has a lot of context.

Things that were new to me: the language, the tool chain, product context. The codebase is several years old.

My skip level manager (1 level above my direct manager) once encouraged that I should aim to finish my work in less than 2x the amount of time it would take X to do it (but besides this I received no pressure, or reminder to push for this target from managers).

This was overly ambitious. I worked longer hours and harder than anyone around, including weekends but still could not finish it in 3x the amount of time initially estimated.

The staff engineer overestimated what I can do too. He's very willing to explain but I had a hard time mapping his high level explanation to what happens at the code level.

I could not tell if the standard here is high or the task is too hard. So I leaned towards putting in more effort rather than voicing my concern.

I also did not have a good sense of "are these unknown parts of the code base grok-able with a little bit of time or do they require a lot of time?" to estimate time spent up front.

In the end I got some barebone thing out and he took over. Still took him a couple more weeks to get the thing finished. Along the way he solved some problems I'm sure I have no chance of solving in that timespan.

With this evidence I was sure the task was legitimately too hard for me and was comfortable letting my manager know my opinion.

Back up a little bit, when I started working on the project, my manager knew I could not stick to the original timeline set by the engineer and encouraged me to take my time to learn the codebase. What is puzzling is my manager did not tell the engineer about this unrealistic estimate. The engineer reports to a different manager and has been around way longer than my manager.

Maybe there is some politics going on that I'm not aware of.

Anyway this has been a very stressful experience.

What could I do better? What should I do to mitigate any harm done through this experience?

Hi all, I am going to transfer to Tiktok as a lead MLE next month.

I have 2 months notice period and I was wondering if anyone has any checklists on what I should do during transition so that I can start fresh and ramp up quickly.

I come from FAANG background and going to a startup-ish culture is an exciting but scary prospect for me (especially with the reduced work life balance).

Tips and checklists of links to Taro videos or other resources are welcome. Thank you

As I'm starting to join a team soon(and knowing this answer varies by team, level, and company), I'm wondering how long does onboarding take and what does it mean to be fully onboarded within your team

I am moving to a faang company in a month for a staff level position (serving my notice period).

Since I have my freetime, what should I prepare to ensure I have a good ramp up?

I want to make sure I start the job with a good note and quickly make impacts. It has been 4 years since I transferred, so my capabilities to adapt might be rusty

Any checklists or advice would be great. Thank you

I am onboarding at a new company. Sometimes, I feel I am completely lost when my teammates were explaining something to me. The reasons I can find may include

1. I am lacking the understanding of the architecture or the context
2. Their explanation uses phrases I do not know what they mean or how they work

In this situation, how should I respond to my teammates? Thanks in advance!

I'm going to be joining Amazon soon and the team I'm on is going from 4/5 people a month ago to I believe 9/10 people (counting me). Our team is going to be comprised of SDE 2's and 1's (I'm an SDE 1).

I'm wondering what's the best way to have the best onboarding experience during this time.

While it will be nice that I will have a decent amount of people who will be in the same boat as me in terms of onboarding, I'm also worried that my manager and more senior teammates won't have as much time for things like 1 on 1s, answering questions, helping me onboard, etc. if they're also helping other people on our team in addition to their own work.

I've been struggling with onboarding at my new job.

I'm part of a new team; my only other teammate recently joined. Many related docs are not in English & the translation is weird & confusing often. This makes revamping up independently super hard for me. I try to find that concept in an English doc from any other team, and that's my way of understanding something. But it puts a lot of overhead because I basically now try to understand the work of a lot of related teams too. And often it is much more time for me.

My manager has a lot of people report to her. I had a 1-on-1, and I explained the situation. She asked me to ping her for help. I often have stupid questions, and I feel weird asking her directly. So I asked her to assign me an onboarding buddy from the related team. But from her reply, it seemed like I should talk to everyone on the team & figure it out. I think she wants me to be more independent.

Now I ping people in my team or close teams to ask for help. I have found most or nearly all people to be super-helpful, and they relate to being in the same situation once. But I feel guilty about asking people for help. I feel it doesn't do much for them. As with most, I don't have a team meeting where I could thank them & their/our manager would notice it.

How should I better navigate this situation?