[Part 1] Software Engineer Onboarding: Embrace Your Lack of Knowledge

Don't be afraid to NOT know something. Ask questions.

When you first join a team, there's a lot that you don't know, and that's ok!! No one expects you to know the codebase, the context, and the structure within your new role. Your goal is to gain context through your questions. 

- [Asking Questions Is NOT A Sign Of Weakness](https://www.jointaro.com/lesson/YIL3iK8fmSwhWP0PASqe/asking-questions-is-not-a-sign-of-weakness/)
- [Overcoming Imposter Syndrome - You Have Much More Value Than You Realize](https://www.jointaro.com/lesson/dTSdd4ozp298jH3glvnx/overcoming-imposter-syndrome-you-have-much-more-value-than-you-realize/)
- [How To Find A Good Team With Career Growth Opportunities](https://www.jointaro.com/lesson/UGIUC9zaGccK0tOarBri/how-to-find-a-good-team-with-career-growth-opportunities/)
- [Alex's Guide to Effective Communication](https://www.jointaro.com/playlist/hVdLQQzfslaYarLSCmmy/)

This is part 1 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go to part 2 of the masterclass here](https://www.jointaro.com/lesson/jr0iHuUCGW5lCdBndEpO/part-2-software-engineer-onboarding-learn-the-workflow/)
- Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Check out the [Formation.dev discount](https://www.jointaro.com/perks/) for Taro Premium members

[Part 4] Software Engineer Onboarding: Understand Strategic Decisions

Learn the business to make good strategic decisions.

By the time you're a month or more into your job, you should start execution on your projects, but you should continue gathering context about your team and company. You should document key decision points in your work, and reflect on who is involved, how long various steps take, and the level of detail various stakeholders ask for.

------

This is part 4 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go back to part 1 of the masterclass here](https://www.jointaro.com/lesson/IYZRmwp33E3TBeFQFr9c/part-1-software-engineer-onboarding-embrace-your-lack-of-knowledge/)
- Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Check out the [Formation.dev discount](https://www.jointaro.com/perks/) for Taro Premium members
- [How To Figure Out If A Team Is Important To A Company](https://www.jointaro.com/lesson/9OwPRwFFSMvEoVj6Zt5Q/how-to-figure-out-if-a-team-is-important-to-a-company/)
- [How To Find A Good Team With Career Growth Opportunities](https://www.jointaro.com/lesson/UGIUC9zaGccK0tOarBri/how-to-find-a-good-team-with-career-growth-opportunities/)
- [This Is How You Get Feedback - Making The Process Smooth](https://www.jointaro.com/lesson/aGuxjGbFjYb34ofhRxjs/this-is-how-you-get-feedback-making-the-process-smooth/)

[Part 3] Software Engineer Onboarding: Understand Tactical Decisions

Learn the product to make good tactical decisions.

Within the first few weeks of your onboarding, you should have have fixed a few bugs and . Now it's time to slow down a bit and do some reflection on the decision-making process and priorities of the team.

- [How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/how-to-build-deep-relationships-quickly-in-tech-12172022/)
- [The Crucial First Step To Building Relationships That Everyone Misses](https://www.jointaro.com/lesson/YPniDFNQqoHEpYHC9JEq/the-crucial-first-step-to-building-relationships-that-everyone-misses/)

This is part 3 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go to part 4 of the masterclass here](https://www.jointaro.com/lesson/JFvfEoKshdPWuiCuy3GY/part-4-software-engineer-onboarding-understand-strategic-decisions/)
- [Go back to part 1 of the masterclass here](https://www.jointaro.com/lesson/IYZRmwp33E3TBeFQFr9c/part-1-software-engineer-onboarding-embrace-your-lack-of-knowledge/)

[Part 2] Software Engineer Onboarding: Learn the Workflow

To make the hard work easier, learn the workflow and process first.

**A big mistake new engineers make**: they dive in directly to a project and start landing code/landing impact. You goal is be curious about the testing and deployment procedures, along with the workflows and processes. One way to do this is to deliberately pick the simplest possible bugs and code changes to make, so you can exercise the workflow. 

- [Use Code Review Feedback For Hypergrowth](https://www.jointaro.com/lesson/aBRgdYpUfnUpoyWG4qZC/use-code-review-feedback-for-hypergrowth-meta-prodigy-engineer-story/)
- [How To Write Better Code Faster As A Software Engineer](https://www.jointaro.com/lesson/iYpRj8XfyzCSaTYnce3y/how-to-write-better-code-faster-as-a-software-engineer-11192022/)

This is part 2 of a 4 part series from Daniel about how to **most efficiently** and **most effectively** onboard into a new team or company. What should you spend your time doing in the first few months of joining, and how should that change based on your level? 

This masterclass covers this topic from the perspective of Daniel Tomko, a 20 year Big Tech veteran. Daniel spent 11 years at Microsoft and 8 years at Meta in various senior IC and management positions. 

- [Go to part 3 of the masterclass here](https://www.jointaro.com/lesson/7l4Nr4hQf8Pv8zfGZwh4/part-3-software-engineer-onboarding-understand-tactical-decisions/)
- [Go back to part 1 of the masterclass here.](https://www.jointaro.com/lesson/IYZRmwp33E3TBeFQFr9c/part-1-software-engineer-onboarding-embrace-your-lack-of-knowledge/)

Every Senior+ Engineer Must Decide: IC vs Management Track

There is one good motivation to become an engineering people manager: to help people. If that's not the priority, you should not become an EM (and you should avoid working with those types of managers).

Daniel toggled between individual contributor (IC) and manager several times in his career. His most fruitful experience was as a very senior IC engineer at Meta -- he had the influence + context of a manager, but none of the headache associated with the job. 

Connect with Daniel on [LinkedIn](https://www.linkedin.com/in/danieltomko/)

Related content: 
- [Questions You Can Ask To Evaluate An Engineering Manager](https://www.jointaro.com/lesson/VOQc7vIzQ4STtw7UrB29/questions-you-can-ask-to-evaluate-an-engineering-manager/)
- [How Do Effective Engineering Leaders Help Their Teams Achieve More?](https://www.jointaro.com/lesson/xGJDCG7VL4hcZaq5XL92/how-do-effective-engineering-leaders-help-their-teams-achieve-more/)

Here's Why You're Doing Interview Prep WRONG

Most people do very shallow interview prep that doesn't actually help them learn. Lists like Blind 75 and Leetcode 75 are not enough to truly master the technical interview for Big Tech companies. 

In this video, Daniel proposes the "proper" way to master the coding / DSA interview so that you can walk into interviews and feel more confident. There are no shortcuts and no memorization -- instead, it's about going beyond the solution for a problem, and then understanding the nuances and process to get the right answer.

- Connect with Daniel on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Checkout Formation as part of [Taro Perks](https://www.jointaro.com/perks/)

Relevant Taro content: 
- [Effectively Learning Data Structures And Algorithms (DSA)](https://www.jointaro.com/lesson/XwpMMY3ss97zOrXJQ7Xr/effectively-learning-data-structures-and-algorithms-dsa/)
- [Struggling With DSA? Don't Worry, That's Healthy!](https://www.jointaro.com/lesson/SPWYdMAu5XQX8ds9MxXc/struggling-with-dsa-dont-worry-thats-healthy/)
- [Masterclass on DSA interviews](https://www.jointaro.com/lesson/V4sTACzfOh22nMVcUV3w/how-to-ace-your-big-tech-interview-data-structures-and-algorithms-7172021/)

Why Chasing Promotion Could Hurt You

Daniel has never gunned for a promotion when choosing teams or projects. In fact, he's actively turned down promotions he was offered at Microsoft and Meta (Philip Su famously down-leveled himself at Meta so he was no longer a Director). 

Here's why chasing a promotion could end up causing more stress and end up hurting your career in the long run. 

- Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)
- Videos from [Philip Su](https://www.jointaro.com/tagname/Philip%20Su/)

Related video: 
- [Taro Premium Session: Mentoring Meta Engineers From E3 -> E5](https://www.jointaro.com/lesson/EX9563YnxcJb62cCmetg/session-5-mentoring-junior-swes-e3-to-senior-e5-in-just-25-years-at-meta/)
- [Rockstar Software Engineer Story: SW2 -> Principal In Just 4 Years](https://www.jointaro.com/lesson/Lvf1TDKt1R4ZJSCr9BVv/rockstar-software-engineer-story-sw2-greater-principal-in-just-4-years/)
- ["Is there something as growing too quickly?"](https://www.jointaro.com/question/o9oyCcIjWT4Xa6w1Eau5/is-there-something-as-growing-too-quickly/)

When Should You Switch Teams Or Companies? - Daniel Tomko's Perspective

Daniel Tomko spent much longer at the companies in his career compared to most engineers: 11 years at Microsoft and 8 years at Meta. Within these companies, Daniel did various team changes.

- Switching companies has a higher "transaction cost" compared to switching teams.
- At a large enough company, you have tons of interesting technical challenges and people to work with.

Connect with Daniel Tomko on [LinkedIn](https://www.linkedin.com/in/danieltomko/)

Other relevant resources: 
- [How to approach a team switch conversation with my manager?](https://www.jointaro.com/question/XFQqRINGf9JvW3xmnVHa/whats-the-best-way-to-approach-a-team-switching-conversation-with-my-manager/)
- [How To Figure Out If A Team Is Important To A Company](https://www.jointaro.com/lesson/9OwPRwFFSMvEoVj6Zt5Q/how-to-figure-out-if-a-team-is-important-to-a-company/)
- [How To Find A Good Team With Career Growth Opportunities](https://www.jointaro.com/lesson/UGIUC9zaGccK0tOarBri/how-to-find-a-good-team-with-career-growth-opportunities/)
- [What's it like working on an ads team?](https://www.jointaro.com/question/GCCIkaBVUpPxGCF4MjRL/what-is-it-like-working-on-ads-teams/)

Explore "Daniel Tomko" on Taro