DSA Crash Course [Part 21] - Sum Numbers Recursive Walkthrough

In this lesson, Alvin walks through the python implementation for the *sum_numbers_recursive* problem.

Code along and test your work in the following editor workspace: <https://structy.net/problems/sum-numbers-recursive?language=py>

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: <https://www.linkedin.com/in/alvin-zablan-b73a92117/>

DSA Crash Course [Part 18] - Recursion Intro Lecture

In this lecture, Alvin introduces the mental model we should use when applying recursion.

If you need additional support taking these DSA skills and actually applying them, take [**Alvin's**](https://www.linkedin.com/in/alvin-zablan-b73a92117/) *complete* data structures and algorithms course on [**Structy**](https://structy.net/?utm_source=taro). You can try out the concepts yourself in their interactive code editor and learn advanced DSA patterns like stack exhaustive recursion.

Use [**this link to get 20% off**](https://structy.net/purchase?promo_code=taro20) the entire Structy DSA learning experience.

Follow Alvin on LinkedIn: <https://www.linkedin.com/in/alvin-zablan-b73a92117/>

Break Into Tech And Become A Software Engineer [Part 6] - Build A Side Project

In this lesson, Brian explains the value of building side projects that not only boost your technical skills but also help you stand out in the job market.

This lesson covers:

- How a well-crafted side project can help you learn new technologies and fill knowledge gaps without needing formal training or mentorship
- The importance of focusing on meaningful, long-term projects that you are passionate about, rather than numerous small, disconnected ones
- Using a self-assessment worksheet to identify your knowledge gaps, create a learning plan, and design side projects that address those gaps and align with your career goals

If you need extra help breaking into tech, join Brian's exclusive, cohort-based bootcamp (just 10 students per batch). Use this special link for $800 off: <https://www.parsity.io/taro>

Connect with Brian on LinkedIn: <https://www.linkedin.com/in/brianjenney/>

Career roadmap worksheet: <https://docs.google.com/document/d/1OpjXtJeQ93TGIz8z9u-p_lYNbhSbk32rPFPDecNMDyM/edit?usp=sharing>

How side projects can even get you into FAANG: [\[Case Study\] Building An App With 1,000,000+ Users To Get Into Facebook](https://www.jointaro.com/lesson/jly45Gx6qR1kqQwBmJEy/case-study-building-an-app-with-1000000-users-to-get-into-facebook/)

Become An Open Source Master [Part 24] - Anticipate Common Pushback

- We might get pushback on our pull requests if we don't address all edge cases or introduce performance regressions.
- Follow the project's coding conventions and make sure our code is clean and well-tested.
- Be gracious and adaptable when contributing to someone else's project.

Taro discussions about testing: 

- [What are your thoughts about Test Driven Development?](https://www.jointaro.com/question/SYwVplJYcyO8Sr7PLT2j/what-are-your-thoughts-about-test-driven-development-do-you-think-it-adds-value-in-your-career/)
- [Automated vs manual UI testing?](https://www.jointaro.com/question/frpv5BLQ63ZqvmDcTIkY/automated-vs-manual-ui-testing/)

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Become An Open Source Master [Part 7] - Improve Something You Use

The video advises that we should start by finding a project that we're passionate about, rather than aiming for the biggest or most well-known ones.

- **Choose projects that you already use or are familiar with**, as this gives you a head start in understanding the project's goals and potential areas for improvement.
- **The dependency graph on GitHub can help you identify potential projects** by showing the dependencies of projects you're already working on.
- **Consider contributing to smaller or medium-sized projects by companies**, as these can offer valuable learning experiences and opportunities to build relationships with professional developers.
- **Contributing to open source can lead to career opportunities**, as demonstrated by the example of Sophie Alpert and her work on the React project.

Article shown by Sophie Alpert: [Using React to speed up the Khan Academy question editor](https://sophiebits.com/2013/06/09/using-react-to-speed-up-khan-academy)

Connect with James:

- GitHub: <https://github.com/jamesgpearce>
- Twitter (X): <https://twitter.com/jamespearce>

Grow From Junior To Mid-Level Engineer [Part 14] - 1 on 1 Meetings

1 on 1 meetings are some of the most important and powerful uses of time... when leveraged properly (which junior engineers often don't). This lesson teaches you:

- The difference between junior and mid-level engineers when it comes to 1 on 1 meetings
- The simple, proactive tactic you should use for every single 1 on 1 meeting you have to make them far more useful

Grow From Junior To Mid-Level Engineer [Part 8] - Debugging

When it comes to software, there will always be bugs. What many realizes don't realize is that your attitude towards bugs is a huge marker of your seniority. This lesson teaches you:

- Why junior engineers usually don't get assigned bugs
- The differences between junior engineers and mid-level engineers when it comes to bugs
- How to evaluate bug complexity overall
- What a mid-level engineer bug looks like vs. a junior engineer bug

Improve your debugging ability with our masterclass: [\[Masterclass\] How To Become A Debugging Master And Fix Issues Faster](https://www.jointaro.com/lesson/ioR6WzamAIUTpySLAr7o/masterclass-how-to-become-a-debugging-master-and-fix-issues-faster/)

Grow From Junior To Mid-Level Engineer [Part 3] - It's On You

For later promotions (i.e. senior and beyond) there are many other factors at play besides your personal skill and growth. This isn't the case for junior engineer -&gt; mid-level engineer. This lesson teaches you:

- The fundamental difference between the junior -&gt; mid-level promotion and others when it comes to landing impact
- How to choose teams and projects as a junior engineer aiming to grow fast
- What matters when it comes to the junior -&gt; mid-level promotion

Understand more about project credit for promotion here: <https://www.jointaro.com/course/nail-your-promotion-as-a-software-engineer/its-not-just-about-impact/>

Clear Communication For SWEs [Part 14] - How Communication Changes With Seniority

I discuss how communication expectations evolve from junior to senior engineer roles. Junior engineers focus on asking insightful questions and providing clear updates. Mid-level engineers lead projects, suggest improvements, and collaborate effectively. Senior engineers take on leadership roles, communicate strategic decisions, and provide insights based on experience. Adapting communication styles based on audience expertise is crucial for career growth.

Connect with me on LinkedIn: <https://www.linkedin.com/in/ryan-wiens/>

The How of the Engineering Career Ladder: Five Essential Foundations for Advancement

Session led by [Shine Garg](https://www.linkedin.com/in/shinegarg/)

Engineering career ladders lay out the “what” of the software engineering career path—what competencies and behaviors are needed at each milestone. However, they often lack guidance on the “how.”

Understanding how—and how quickly—you can acquire and exhibit these competencies significantly impacts your career trajectory, financial future, and sense of fulfillment in life.

This talk demystifies the process of climbing the engineering career ladder. Join us to learn the five essential foundations for advancing your career and achieving your goals.

Asking Great Questions [Part 6] - Be Clueless In Public

The best software engineers are those who embrace their lack of knowledge. This lesson teaches you:

- Why it's better to ask your question in a broader audience
- The difference levels of visibility when asking a question with higher being better
- A huge, often unknown benefit that comes with asking questions in public which allows even junior engineers to become leaders
- Why you should always try to create a record of your question and its answer(s)

[Timeless Career Advice] Startup vs Big Tech

One of the fundamental questions you face as an engineer is where to work. Should you join a startup, medium-sized company, or Big Tech? What are the pros or cons of working at a tech or non-tech company?

Connect with Louie:

- SmallBets community: [**https://smallbets.com/?utm_source=taro**](https://smallbets.com/?utm_source=taro)
- Twitter: [**https://twitter.com/LBacaj**](https://twitter.com/LBacaj)
- Newsletter: [**https://newsletter.memesmotivations.com/**](https://newsletter.memesmotivations.com/)

Write A Stellar Resume As A Software Engineer [Part 16] - Leveling

For the vast majority of engineers, they want to get the highest level they possibly can from an interview opportunity. How you write your resume is a substantial part of achieving this goal. This lesson teaches you:

- How to format your resume based on what level you were at different points in time
- How including your exact promotions can actually hurt you
- When to include your level on a resume vs. not

Write A Stellar Resume As A Software Engineer [Part 13] - ATS Obsession

With so many resumes being sent in to any decent engineer job opening, automation is often deployed to filter out resumes. The big piece behind this is the ATS. This lesson teaches you:

- What an ATS (Applicant Tracking System) is
- How the ATS fits into the tech recruiting pipeline and how engineers commonly misunderstand that process
- What engineers usually do to incorrectly optimize for the ATS while sabotaging their overall changes
- What you need to do to properly get past the ATS

Write A Stellar Resume As A Software Engineer [Part 6] - Poor Spelling And Grammar

The vast majority of software engineers don't have English as their first language, and this leads to many basic spelling and grammar mistakes on resumes. Unfortunately, this hurts engineers far more than they realize. This lesson teaches you:

- Why there is 0 tolerance for spelling and grammar errors on a resume (i.e. 1 mistake is enough to get your resume tossed out entirely)
- How spelling and grammar mistakes speak volumes about a software engineer's overall skill
- Basic ways to perfect the spelling and grammar of your resume, even if English isn't your first language

Negotiation Course: Negotiating With An Exploding Offer

An exploding offer is an offer that must be accepted within a time limit (potentially as short as a few hours), otherwise it will expire.

**Exploding offers are often fake** and you can take longer than the supposed deadline. However, you should protect yourself in the small chance that the explosion is real by having backup options.

If you face an exploding offer, the first step is to understand where the urgency is coming from:

> What’s the timing constraint? I’ve dedicated 3 weeks interviewing here and enjoyed meeting the team, but I'm curious why there's such an urgency at this point in the process?

A few options for how to request more time: 

- **(less effective)** Explain that you’re still collecting data and wrapping up the process so you’d like another week. Something like: "*I’m in the last round with the company so I’m confident I can get back to you by Monday.*"
- **(more effective)** Ask for more information. "*One thing I heard in the interview is that many of the mobile developers have transitioned to work on dev infra, which is interesting for me. Could I chat with someone who does made that transition?*" 
  - In a similar way, you can also request to chat with folks in the management chain, e.g. the director or VP.
  - When Rahul was at Meta, he’d do calls with people who got offers coming from Pinterest

Worst case scenario, you have to renege or quit shortly after joining. You should avoid this if possible (there is potential reputational damage), but we'll talk about this scenario in the next video.

Negotiation Course: Negotiation Starts Now

It's critical that you only start negotiations when a company has verbally given you an offer.

Leveling is very important since it’ll dictate your salary band and equity. If you’re at a larger company, ask what level you’re coming in at, and see what kind of wiggle room there is.

If possible, talk to the hiring manager or people involved in your interview"

- You can learn advice on what you could work on.
- You can hear what the business need was to hire a role and why they picked you. 

The above points give you “ammunition” for negotiation: you want to understand how badly the company wants you.

Negotiation Course: Why Negotiation Is Extremely High Leverage

Negotiation may take a few hours of time (and a bit of uncertainty/discomfort), but the result could be life-changing for you. In a place like Silicon Valley, where engineers are highly paid, successful negotiation could easily net you 5 or 6 figures of additional income.

In addition, an increase in salary will “anchor” your compensation and the benefit will compound since raises are based on this. e.g. a 5% raise is a larger dollar value compared on a $120K salary ($6K) compared to a $100K salary ($5K).

The Steve Ballmer story when he joined Microsoft is an example of one of the largest wealth increases ever due to negotiation: his net worth today is $120B (that's $120 billion!). Even though he joined Microsoft as employee #30 in 1980, he ended up negotiating 8% equity ownership of Microsoft, a deal that made him a billionaire many times over. (Read more about [Steve Ballmer's deal here](https://www.forbes.com/sites/georgeanders/2014/09/30/long-ago-twist-yielded-ballmer-a-fortune-in-microsoft-stock/?sh=16d42b7736a5).)

The famous article from Patrick McKenzie ([patio11](https://twitter.com/patio11)) about negotiation: [Salary Negotiation: Make More Money, Be More Valued](https://www.kalzumeus.com/2012/01/23/salary-negotiation/)

Nail Your Promotion As A Software Engineer [Part 26] - Peer Feedback Squad

In order to get promoted as a software engineer, you need several important people to have your back. This is especially important for senior level and above promotions where you might need 10+ pieces of glowing feedback. This lesson teaches you:

- How to identify the critical peers you need to vouch for you in performance review
- What "feel good" and ultimately near useless feedback looks like, which is what a lot of stagnant engineers are stuck with
- What powerful, meaningful feedback that actually makes a difference in promotion cases looks like
- How your peer feedback should look based on the seniority of the peer giving it to you

Nail Your Promotion As A Software Engineer [Part 23] - Sell Yourself, Claim Your Wins

So many software engineers don't realize that perception and reality are 2 very different things that often drift apart. The painful truth is that perception is far more important than reality. This lesson teaches you:

- How software engineers can do amazing work but their teammates actually think they're mediocre
- Why you need to put in the work to get full credit for your work, especially for promotion
- Why you shouldn't only wait for huge launches to communicate progress
- Which mediums to use when it comes to sharing progress updates
- The many benefits of high-quality project updates

For more concrete tactics on writing a top-notch project update, check this out: ["How to get more visibility on work?"](https://www.jointaro.com/question/XA0X51AypDLCeVeleJv4/how-to-get-more-visibility-on-work/)

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.