The First Thing You Need To Do To Set Yourself Up For Promotion

Which of the following is the foundation for your promotion plan?

Why is understanding your strengths so important towards your tech career growth?

Don't Waste Your 1 on 1s. Build The Relationship

Why should you build the relationship in 1 on 1 meetings?

True or false: Small talk is okay in 1 on 1 meetings to break the ice and learn more about the other person's life outside of work.

Why are deep relationships needed in tech, especially at senior levels?

One-on-one meetings are a foundational tool for building trust and social capital within a company. Especially in medium to large organizations, relationships drive execution—and one-on-ones provide a structured, intentional space to cultivate those relationships.

- **Build social capital early**: Scheduling one-on-ones with key teammates—engineers, designers, PMs, and adjacent team managers—early on helps lay the groundwork for future collaboration. This “trust bank” can be drawn on when challenges inevitably arise.
- **Treat relationships as human endeavors**: There's no formula for connection. These conversations are opportunities to build real understanding, not just to exchange project updates.
- **Welcome small talk, especially at first**: In early one-on-ones, light conversation about emotions, hobbies, and general well-being helps establish rapport. This human connection builds the trust needed for deeper collaboration later.
- **Shift toward deeper conversations over time**: Once a working relationship is more established, focus should evolve toward more meaningful topics—emotions, motivations, and work challenges—while still leaving space for the personal.
- **Listen with genuine care**: The most effective relationships are built on authentic interest. It’s not enough to ask personal questions—true connection comes from caring about and following up on what others share.

By using one-on-ones intentionally and empathetically, it's possible to create strong, lasting connections that enhance both individual performance and team effectiveness.

Not Getting Stuff Done? Find Someone To Call You Out

Why are accountability partners so helpful when it comes to productivity?

True or false: A good accountability partner is willing to shame you a bit sometimes.

How do good accountability partners help with excuses?

- Finding an accountability partner is one of the most powerful ways you can shore up your productivity.
  - You can understand your own potential when you see what your peers can do
  - They can offer help when you're feeling low or stuck
- Humans inherently don't like letting other people down: We're a social species. Just having someone who's expecting or even counting on you to make decent progress regularly makes you far more motivated to actually get stuff done out of fear of disappointing them.

Related resources:
- ["How do you network effectively within a company?"](https://link.jointaro.com/Hr1nr53D7sfQAEv3A)
- ["How can I better network with other software engineers in the Bay Area?"](https://link.jointaro.com/42JLsbppRMwAJAPUA)

Make Sure To Do This To Get Full Credit For Your Work

On top of doing the work, what else do you need to do in order to get full credit for what you are doing?

True or false: It is bad to give more public status updates for your project as it will come across as looking for attention.

Why should you not feel icky when you are properly broadcasting the status of your project?

Core points:
- *You don't get credit automatically for doing good work, especially if you work in a large company.*
- It is vital that you bring visibility to your work and claim credit for jobs well done in project updates, meetings, and other more public avenues.
- You may feel "icky" for sharing status updates - Don't! If your work is truly important, than it's worth sharing about and keeping the team in the loop. If you don't feel like your work is important, then you have a separate problem you need to address.
- Use project updates to thank others! Treat it as a mechanism to build social capital.

Related resources on how to write concise, impressive project updates:
- ["How can a painfully introverted person increase their visibility and promote themselves?"](https://link.jointaro.com/3XHsUifABjyN3Tq98) - From a SWE intern at Google
- ["How to get more visibility on work?"](https://link.jointaro.com/aQUHxnsNAJVcRgth6) - From a junior engineer [E3] at Meta

How The Best Software Engineers Learn A Tech Stack - The Lego Model

- "The Lego Model" is a way to view the world and understand your learning journey as a software engineer.
  - Technical components (e.g. rendering a list of items) are the individual legos
  - Complete products (e.g. a food delivery app) are the full lego creations
- There are 3 axes to evaluate your legos:
  - **Quantity:** How many you have
  - **Quality:** How good and sturdy your legos are
  - **Commonality:** How "in demand" your legos are (i.e. how many creations they can fit into)
- Most earlier-in-career engineers understand the 1st axis of quantity and incorrectly spend a lot of time learning different tech stacks and frameworks.
- Those same engineers often don't even realize the 2nd and 3rd axes exist:
  - When they learn a component, they will build it out with very low quality.
  - They will learn "flashier" components that aren't even used by most products/companies.

For examples on how to excel at the 2nd and 3rd axes, check out the related resources below!

Related resources:
- [[Masterclass] How To Learn Quickly In Tech](https://www.jointaro.com/lesson/u9ldIvrTvV1wfWExccDR/masterclass-how-to-learn-quickly-in-tech/) - The full video this clip came from
- [This Is How Software Engineers Should Initially Learn](https://link.jointaro.com/iVBpCaB6pAHivhdi6)
- [Building Software For Optimal Learning Example - Login Flow](https://link.jointaro.com/oEkTB3pskKH6JHCX6)

Common Scenarios For Setting Up 1 on 1s

What is the main condition to look out for that could prompt you to set up new 1 on 1 meetings?

Which of the following scenarios is something you probably should set up some new 1 on 1 meetings for?

1 on 1s are meetings for the 2 people involved to connect and build a longer-term relationship. Here are 3 common scenarios where it makes a ton of sense to set up a 1 on 1:

1. **Incoming new hires**: Help the new person on the team feel welcome and get them onboarded
2. **You being the new hire**: When you're new, 1:1s help you build up valuable context and relationships from talking to existing teammates. Use your "new"-ness to setup meetings with anyone who might be relevant to your job [as described here](https://www.jointaro.com/lesson/xwldhYelyOFLjogs7RVA/onboarding-gives-you-special-powers-make-sure-to-use-them/)
3. **Working with a new team**: If you have a long-term relationship with a partner from another team, it could be worthwhile to setup a recurring one on one with them

Finding The Best Environment For Learning

True or false: The best way to level up is to join a team where you are the absolute strongest and know more than everybody. This way, you will get made the lead by default.

Why is it good to be the dumbest person in the room?

How can you really level up your skills building within a tech stack you are already familiar with?

The best environment for learning as a software engineer is one where you can get feedback and grow each day.

What Makes A Good Growth Environment For Promotion

Which of the following is a great way to increase your scope?

True or false: It is good to work in a company where there are constantly too many problems to solve.

Why is there always a plentiful supply of problems to solve in high-growth tech companies?

Start Your Day By Eating The Frog

When it comes to productivity, what is eating the frog?

True or false: To ease into your day, the best thing to do when you wake up is something easy and fun like checking your Instagram.

Easy Tactics You Can Apply Today To Increase Your Focus

Which of these are valid tactics to minimize the distraction from your phone?

True or false: As an engineer, it is important for you to attend every possible meeting so you can know everything that is going on, therefore empowering your productivity.

As a software engineer, why is it crucial to reject meetings when possible?

Maximize your focus and productivity as a software engineer by minimizing any distractions.

Suppress Your Instincts And Treat All Feedback As A Gift

True or false: If you get a piece of feedback, you should initially assume good intent and that it is correct.

What should be your immediate reaction when you get a piece of constructive feedback?

True or false: If you get feedback that you do not believe is 100% correct, you should just ignore it.

Which of the following are good things you can do when you get a piece of feedback that you genuinely believe is not constructive and is phrased in a harmful way?

True or false: One of the most straightforward ways to grow in tech is to just immediately incorporate every piece of feedback you get.

- **Don't be defensive at all when receiving feedback unless it is entirely incorrect.**
- If you have taken the time to find a supportive team, the vast majority of feedback you receive (95%+) will be correct and have value.
- Feedback is a gift and arguably the greatest gift you can possibly receive for your career. *One of the most common attributes among top performer engineers is that they take and apply feedback extremely well.*
- Have empathy for the feedback giver. They probably feel a bit awkward as they're unsure how you're going to receive the feedback. Make them feel comfortable after they share the feedback by thanking them immediately and earnestly.
- Write down all great feedback you receive and try to convert it into action items:
  - **Example:** "I feel like you could be more active in meetings." -> I will try to say at least 1 thing in every team meeting from now on.
- If you get feedback you genuinely believe is incorrect and hurtful:
  - Talk to your manager if you don't have a good relationship with that person.
  - If you feel comfortable enough to talk with that person directly, have a crucial conversation.

Related resources:
- ["How can I find more opportunities to grow when I'm getting very little real feedback?"](https://link.jointaro.com/TzKmgN5nLnLyXJ5G6)
- ["Everyone's telling me I'm doing great - How do I get actionable, constructive feedback?"](https://link.jointaro.com/ng6MUQy2yUfS8w4e8)
- [Effective Communication Guide - Giving Feedback](https://link.jointaro.com/VsQvnzsnJbbXUQDy6)

1 on 1 Meetings Are An Exercise In Proactivity

Why should you err on the side of creating a 1 on 1 meeting instead of waiting for it to be absolutely necessary?

True or false: Team meetings are more important than 1 on 1 meetings, so you should create them more aggressively for everyone to stay in sync.

Being proactive about setting up one-on-one meetings helps build strong relationships and avoid costly misalignments down the line.

- **Default to setting them up**: It’s better to create a recurring one-on-one and cancel it later than to realize too late that it was needed.
- **Low time cost, high value**: One-on-ones only use two people’s time, making them much less costly than poorly-run team meetings.
- **Prevent bigger issues**: Skipping one-on-ones can lead to being misaligned with key collaborators, which may cause serious problems later in a project.
- **Sync early with core stakeholders**: Especially in cross-functional teams or shared ownership scenarios, early and regular one-on-ones help prevent misunderstandings and build trust.

The Resource You Need For Promotion That Few Understand

Which of the following is the resource needed for promotion that many engineers don't understand or even realize exists, particularly more junior ones?

True or false: When you are onboarding as a software engineer, the one and only thing that matters is your ability to understand the codebase and extend it.

Why is social capital important for senior engineers?

How Software Engineers Are Measured For Promotion

What does additive value look like for a software engineer?

What's the main metric used to evaluate engineers for promotion and their overall seniority?

What kind of value is the following: Creating a team-wide initiative to write more unit tests, organizing regular hackathons to write hundreds of tests at once alongside creating a dashboard to measure which tests catch the most bugs

What kind of value is the following: Helping the company's ambitious hiring goal for web engineers by interviewing dozens of React developers in just a few weeks

What kind of value is the following: Taking an incredibly vague product idea and refining it into a well-defined product spec by bringing together dozens of engineers, product managers, data scientists, and designers and getting alignment on what the value proposition is and how that manifests as a product experience

What kind of value is the following: Building out the iOS portion of adding Twitter login to onboarding flow for your company's core app after getting high-quality mocks and requirements for it

The Importance of Reflection With Time Management

Why is reflection important when it comes to productivity?

True or false: If you aren't getting as much done as you want, you should just work harder.

Which one of these is a concrete tactic you can use to shore up your reflection?

Establish what you want to get done in a given day or week. But if you don't get it done, then you NEED to reflect on **"why"**? Some possible reasons you might come up with it: 
- Procrastination
- Lack of clarity
- Missing information 
- Ad-hoc meeting

Now use this as learning going forward to make better estimates. Reflection is important enough that you should block time your calendar for it.

A Simple Trick To Make Your Meetings More Efficient

What can you do before a meeting to empower it to achieve more outcomes?

You write down an agenda for your upcoming meeting, and you realize that it is incredibly rich and complex. What else can you do to level up the meeting?

Preparing and sharing an agenda before meetings—especially manager one-on-ones—leads to more thoughtful discussions and better outcomes.

- **Pre-fill the meeting agenda early**: Add discussion topics at least a day in advance to give others time to prepare.
- **Proactively notify participants**: Ping the other attendees to let them know the agenda is ready and encourage them to review it before the meeting.
- **Avoid putting others on the spot**: Sharing discussion points beforehand prevents “deer in the headlights” moments where participants may not be ready to respond thoughtfully.
- **Encourage richer conversation**: When participants have time to reflect, meetings become more action-oriented and less reactive.

How To Learn A New Codebase Fast

What is the best way to learn a codebase?

True or false: In software, experimenting and making changes is cheap, so a great way to learn is by trying a lot of things and seeing what happens, even if you do not fully understand the overall codebase yet.

Why is structured learning like tutorials and courses not effective for actually learning a codebase?

True or false: Before you jump into a codebase, you should ideally get a certificate in that tech stack before working with it.

Which of these is a good way to learn a codebase with your first code changes within it?

True or false: Breaking something locally is an effective way to learn a codebase.

- The best way to learn a new codebase is to learn by doing.
- Don't get paralyzed reading documentation or getting a certificate before jumping into a codebase.
- Start tinkering ASAP. It doesn't matter if you don't fully understand the codebase - Just do small changes like deleting a line or flipping a variable and then see what happens after you build the code.
- Alex's standard: Put out a commit/pull request for a new codebase within 2 days.
- You want to get code into review as soon as possible, because the feedback you get on your pull request is where the real learning happens. Don't worry about the quality; it's going to be bad in the beginning like with any newbie - The important thing is that you submit something out there into the world so your teammates can tell you how to get better.

Related resources:
- [How To Figure Out Which Parts Of A Codebase Matter](https://link.jointaro.com/PdpWBjAzU7NVTamf6)
- [Learning A New Codebase Fast As An Intern](https://link.jointaro.com/SMaLvqCVeoH9MmvV7)

Taking Amazing Meeting Notes

For any meeting, what should you make sure for it?

True or false: As long as you write down most of what was said in a meeting, you have taken a good set of meeting notes.

What can you do when someone else in a meeting says something really insightful?

Your meeting is winding down, and you have a good set of notes of what was said during the meeting. What should you do next?

Meetings can easily become unproductive unless there is a clear sense of ownership and structure. This segment emphasizes taking initiative and being proactive with note-taking and follow-up.

- **Take initiative to capture takeaways**: Especially when meeting with a manager, take responsibility for writing down notes and summarizing key points. Don’t assume they’ll do it—they likely have too much on their plate.
- **Communicate your intent**: Let the other person know that you’re taking notes because their input is valuable. This builds mutual respect and sets the tone for accountability.
- **Clarify ownership of action items**: Don’t leave to-dos ambiguous. Specify who will do what—whether it’s you, your manager, or another teammate.
- **Create space for note-taking**: Pause briefly during the conversation when something important is said. Say things like “Let me write that down” to signal that you’re capturing key information.
- **Follow up consistently**: Revisit the notes in future meetings and check progress. This keeps everyone aligned and ensures that good ideas don’t get lost.
- **Adapt for walking meetings**: For more casual one-on-ones (like walking meetings), carve out 10 minutes afterward to document and share what was discussed. This keeps the informal meeting just as productive as a formal one.

Make It Easy For You To Receive Help

True or false: If you ask for help on a coding issue, link the entire repo of the codebase you are working on to be safe. This guarantees that helpers have all the context they need.

What can you do to really sharpen your question before asking it?

"I am having trouble getting a button to appear above an image in my webpage. Can someone help with this?" - Which of the following are questions that should have been anticipated beforehand for this question?

The Best Gift You Can Give Yourself When It Comes To Productivity

Which of these is the best gift you can give yourself when it comes to productivity?

True or false: Phones are great productivity tools as they allow us to accomplish almost anything in a really convenient way. This is why we should make sure that we always have our phones close by as we are working.

Where should you have your phone when you are trying to do deep work?

Between flow state and context switching, which is the safer option to invest into to make yourself more productive?

One of the best ways to improve your productivity is to block off chunks of time where you can focus without having to context switch.

Tech Career Growth Videos

Our instructional videos provide software engineers with insights needed for career growth. Masterclasses go incredibly in-depth on a specific tech topic while case studies are real examples from established engineering leaders.