Build Deep Relationships Quickly In Tech [Part 4] - The 2-Step Process

Networking doesn't have to be overly complicated and fuzzy. This lesson teaches you:

- A very basic 2-step framework to approach networking with
- The spectrum of help and providing value to people
- How much help you should provide to someone, especially prospective people you want in your network
- Why you should always give a non-zero amount of help in a work environment, especially if you work at a strong tech company

Build Deep Relationships Quickly In Tech [Part 3] - The #1 Rule Of Networking

Many engineers struggle with networking as they don't fundamentally understand how it's supposed to work. This lesson teaches you:

- The #1 rule of networking and how not following it completely messes up your social circle
- A very tactical, mathematical framework from which to view networking
- How giving more than you take creates an infinite amount of value
- Why you're not a "loser" for being benevolent and kind
- The pain and toxicity of being in a fake network, which many engineers are a part of
- The powerful benefits of being in a true network

Build Deep Relationships Quickly In Tech [Part 2] - Why A Strong Network Isn't Optional

No engineer is an island. And if they are, they're going to have a bad time. This lesson teaches you:

- How a strong network helps with job searching
- How a strong network helps with promotion and overall on-the-job performance
- How a strong network helps with general learning
- Why you need to start networking *now*, and how starting "early" actually makes the networking way easier

To better understand the difference between a strong referral vs. a weak referral: <https://www.jointaro.com/course/ace-your-tech-interview-and-get-a-job-as-a-software-engineer/referrals/>

Build Deep Relationships Quickly In Tech [Part 1] - How This Course Works

Trying to break into FAANG, but you have no close friends there willing to give you a strong referral? Aiming for a promotion, but you don't have enough senior peers to vouch for you? These are career shortfalls engineers face constantly, and it's because *they don't have a strong enough network*.

This course is here to fix that issue for you, because at the end of the day, your network is your net worth, especially in a hyper-competitive tech market. Here are the core parts of the lesson:

- Your instructor [Alex Chiou](https://www.linkedin.com/in/alexander-chiou/) walks you through his extensive 10+ year Silicon Valley background with rapid career advancement, ending up as a high-performing tech lead making $750k at Robinhood. Most importantly, he goes through how he's built a massive network full of talented people willing to fight for him across his career and the many career benefits he's reaped from that.

- We walk you through the course objectives. By the end of the course, you will:

  - 🌟 Understand the **\#1 rule** of networking

  - 2️⃣ Set up a basic **2-step process** for networking

  - 🤝 Know how to find the **best people** for your network

  - 🏃 Develop tools to **build relationships fast**

  - 🛑 Save time by **avoiding common mistakes**

Expert Secrets of Successful Big Tech Interviews

**Event description**

Join this special NEW session where I interview "Mr. X" –– a former Amazon Bar Raiser and current Head of Talent Acquisition at a top tech company that must remain nameless ;)

Together, we'll take you beyond the basic tips you already know and unveil **specific, winning strategies** that actually separate you from other candidates in competitive interviews.

If you have the job skills and a solid work history (but interviewing continues to be where you "fall down" in the job search) this event will be an absolute game-changer.

**After This Masterclass, You Will:**

- **Eliminate Blind Spots**

  - **You’re making mistakes every time you interview, that you don’t see, that cost you job offers. Get ready to hear what they are.**

- **Own Your Story**

  - **The winning candidates aren’t necessarily the most skilled––they have the best stories. Soon, YOU will be that candidate.**

- **Read Minds (Literally)**

  - **Hiring managers speak in code. What they say is often totally different from what they’re thinking. Now you’ll know the difference.**

If you need additional support with your job search, you can get coaching from Alan and Kadima Careers. Join with a discount here: [**https://signup.kadimacareers.com/mQBsDvu**](https://signup.kadimacareers.com/mQBsDvu)

SWE Internship Survival Guide [Part 20] - Go Deeper: Follow Through

Congrats on making it to the end of the course! Here are additional resources to help you follow through with nailing your internship return offer:

- Take the code quality course: [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)
- Take the question asking course: [Ask Great Questions That Get Great Answers Quickly](https://www.jointaro.com/course/ask-great-questions-that-get-great-answers-quickly/)
- Take the onboarding course: [The Complete Onboarding Guide For Software Engineers](https://www.jointaro.com/course/the-complete-onboarding-guide-for-software-engineers-succeeding-when-youre-new/)
- To become a rockstar (Top 5%) intern: [Grow From Junior To Mid-Level Engineer: L3 To L4](https://www.jointaro.com/course/grow-from-junior-to-mid-level-engineer-l3-to-l4/)

SWE Internship Survival Guide [Part 19] - The Real Treasure

Internships are a unique chance to grow your network alongside your technical skills. Here are the core points from the lesson:

- The other interns you work with often become valuable long-term connections—professionally and personally
- Shared experiences during an internship create natural bonding opportunities, so don’t miss out by being overly heads-down
- Building your network isn’t just about being social—it’s also about doing great work and being helpful to others

Learn how to build relationships here: [**\[Masterclass\] How To Build Deep Relationships Quickly In Tech**](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

SWE Internship Survival Guide [Part 18] - Plot Your Growth Trajectory

Wrapping up all the advice and strategies into something actionable can feel overwhelming—so this video offers a clear, week-by-week roadmap to help you stay on track throughout your internship. Here are the core points from the lesson:

- **Weeks 1–2**: Embrace your newbie status—ask lots of questions, explore the codebase, and focus on learning, even if it means breaking things (safely)
- **Weeks 3–4**: You should start contributing code more regularly, with fewer basic mistakes in PRs, and begin transitioning from onboarding tasks to your main project
- **Weeks 5–7**: You’re gaining confidence—PR feedback is more meaningful, your code is smoother, and a midpoint check-in should help confirm you’re on track
- **Weeks 7–10**: You’re hitting your stride—code velocity and quality are high, you’re asking sharper questions, and maybe even helping others on the team
- **Weeks 11–12**: Finalize your project, document it, reconnect with your network, and take a moment to enjoy the end of a hard-earned, productive summer

SWE Internship Survival Guide [Part 17] - Midpoint Check-In

When you’re aiming for a return offer as an intern, your final performance review can feel like a high-stakes moment. But it *shouldn’t* feel like a mystery. This lesson focuses on how to avoid surprises by being proactive about getting feedback and tracking your progress during the internship. Here are the core points from the lesson:

- Performance reviews shouldn’t be surprises—interns should proactively schedule a midpoint check-in (around week 5 or 6 of a 12-week internship) to gauge how things are going
- Use this check-in to ask honest questions about how you’re doing, what areas need improvement, and how you’re trending toward a return offer
- Treat it as a formal feedback session: retitle the meeting, extend its duration, and come prepared with your accomplishments and areas for growth
- Ask for clarity on how interns are typically evaluated and where you currently stand—phrasing questions with curiosity can unlock more candid feedback

SWE Internship Survival Guide [Part 16] - Diversify Your Mentors

As you approach the end of your internship, one of the most important factors in getting a return offer is how you’re evaluated during your performance review. This lesson focuses on how to set yourself up for success by building strong relationships across your team. Here are the core points from the lesson:

- Don’t rely solely on your assigned intern mentor—build relationships with multiple teammates to avoid single points of failure
- You’ll receive 360 feedback at the end of your internship, so proactively engage with others who can speak positively about your work
- Identify 2–3 potential advocates by week two and keep them updated through code reviews, one-on-ones, or casual check-ins

Learn how to build relationships here: [\[Masterclass\] How To Build Deep Relationships Quickly In Tech](https://www.jointaro.com/lesson/tyaPFMXPoz2pmzB7OVzt/masterclass-how-to-build-deep-relationships-quickly-in-tech/)

SWE Internship Survival Guide [Part 15] - AI Tools

With AI tools becoming increasingly embedded in the software development workflow, it’s important for interns to use them wisely without compromising their own growth or credibility. Here are the core points from the lesson:

- Interns should embrace AI tools but avoid over-reliance, as teams are assessing *their* engineering abilities—not the tool’s
- Use of AI must comply with company policies, and interns should always understand and be able to defend the code they submit
- AI is best used for boilerplate and simple tasks, but the intern should remain the core problem solver and decision-maker

SWE Internship Survival Guide [Part 14] - Debugging

Debugging is a vital yet often underestimated skill for software engineers, especially interns who are frequently tasked with bug fixes or need to debug their own code. Here are the core points from the lesson:

- Interns often start with low-priority bugs or tackle backlog issues, making debugging a key part of ramping up and delivering impact
- Effective debugging requires identifying the relevant code, using logs or dashboards, and writing down your hypotheses to stay focused
- Reframing debugging as evidence gathering for a potential question helps you avoid tunnel vision and often leads to discovering the root issue
- Common mistakes include poor organization, incorrect environment setup, and focusing on irrelevant details—clarifying these with teammates is encouraged

Go through the debugging masterclass here: [\[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/)

SWE Internship Survival Guide [Part 13] - Code Review

As an intern, your ability to navigate code reviews can significantly impact your chances of getting a return offer. It’s not just about code correctness — how you engage with feedback and your team matters just as much. Here are the core points from the lesson:

- Code reviews are mandatory for shipping code and are a key mechanism for maintaining quality, sharing knowledge, and passing on team culture
- Interns often struggle with code review because it’s rarely taught; expect lots of feedback early on, and aim to show progress by reducing repeated comments over time
- Your *dynamic* — how open, curious, and quick you are in responding to feedback — is often more important than just the *substance* of your code
- Always respond quickly to feedback, ideally within an hour, and never land a PR with unresolved comments unless clearly communicated and agreed upon
- For large or confusing feedback, escalate to a synchronous conversation (e.g., a call) instead of dragging it out over multiple asynchronous review rounds

SWE Internship Survival Guide [Part 12] - Code Quality

Writing a lot of code isn’t enough to secure a return offer — it also needs to meet your team’s quality standards. Clean, thoughtful code makes it easier for others to review, trust, and approve your changes. Here are the core points from the lesson:

- Poor quality code, even if it’s high in volume, will cost you a return offer
- High-quality code means making your changes easy to review by including a clear commit message, test plan, and relevant context
- Interns often overlook non-code details like documenting edge cases and adding screenshots or videos to demonstrate what changed
- Good code quality is about reducing friction for your reviewers — make their job easier and they’ll be more likely to trust and support you

Take the code quality course here to instantly boost your return offer chances by +50%: [Level Up Your Code Quality As A Software Engineer](https://www.jointaro.com/course/level-up-your-code-quality-as-a-software-engineer/)

SWE Internship Survival Guide [Part 11] - Code Velocity

Your success as a software engineering intern hinges on one key metric: your ability to ship code consistently. Here are the core points from the lesson:

- Code velocity is the primary way interns are evaluated, so focus your time on writing and shipping impactful code
- Every company has a different pace, but you should ask your manager for benchmarks and observe full-time engineers to calibrate your own output
- Structure your day around long blocks of uninterrupted coding time, and avoid distractions like intern socials or long-term architecture meetings
- Make small, frequent code changes instead of large ones to make code review easier, allow quicker course correction, and prevent painful merge conflicts
- Communicate your approach with your team so they understand your intent to seek faster feedback through smaller pull requests

SWE Internship Survival Guide [Part 10] - Understanding The Codebase

Understanding a large codebase can feel overwhelming at first, but you don’t need to master everything to make an impact. Here are the core points from the lesson:

- Use the Pareto principle to focus on the small portion of code that matters most for your project rather than trying to understand everything
- Avoid getting stuck reading docs and aim to quickly build the code, add logs, and view those logs to gain hands-on comprehension
- Identify key parts of the codebase by asking your manager or teammates for pointers and using exploratory techniques like print logging
- Treat code understanding as a “multiplayer” activity by asking questions, pair programming, reviewing commit history, and engaging with teammates
- Operating in multiplayer mode not only accelerates your learning but also strengthens relationships and increases your chances of getting a return offer

SWE Internship Survival Guide [Part 9] - Build In Public

It’s not enough to quietly ship code during your internship—sharing your progress publicly is a key strategy for visibility and success. Here are the core points from the lesson:

- By default, no one except your mentor may know what you’re working on, so it’s your job to build in public and generate awareness
- Visibility leads to stronger relationships, more feedback, and more people who can advocate for you when return offer decisions are made
- Intern projects often aren’t on the critical path, making it even more important to market your work through demos, updates, and conversations
- Reusing assets like screenshots or videos from your pull requests is a great way to showcase progress
- Use team standups, Slack channels, emails, and meetings to share what you’ve built and invite feedback, always including links and tagging collaborators to maximize engagement

SWE Internship Survival Guide [Part 8] - Ask Great Questions

As an intern, asking high-quality questions is one of the most important ways to learn quickly, make progress on your project, and build strong relationships with your team. But not all questions are equal—there’s a right way to do this that can significantly increase your chances of getting a return offer. Here are the core points from the lesson:

- There’s a sweet spot between asking too few questions (and struggling in silence) and asking too many low-effort ones (which can burden your team). Most struggling interns fall on the “not asking enough” side
- Every question is a chance to build trust and relationships. They help others evaluate your growth and give you valuable feedback—so don’t underestimate their importance
- High-quality questions include just enough context (like screenshots or code snippets), are well-structured, and are ideally asked in public forums like Slack channels to benefit others too
- Avoid “leading hellos” (e.g. *“Hey, got a sec?”*). Instead, ask your question directly in the first message to reduce unnecessary back-and-forth and show respect for others’ time

Take the full question asking course here: [Ask Great Questions That Get Great Answers Quickly](https://www.jointaro.com/course/ask-great-questions-that-get-great-answers-quickly/)

SWE Internship Survival Guide [Part 7] - Feedback Is Your Growth Fuel

Feedback is the most important growth tool for interns—and how you seek, receive, and apply it can define your success. Here are the core points from this lesson:

- Regularly ask for feedback (ideally weekly or biweekly), and be specific—ask what you should start, stop, or continue doing to improve
- Synchronous conversations (in-person or video) lead to deeper, more honest feedback than async messages—don’t rely only on Slack or email
- Always thank people for feedback, turn it into action items, and follow up to show progress—this builds trust and reinforces your coachability
- Make your improvements visible (e.g. call out test validation or coding pattern adherence in PRs) so your growth is legible to others
- Interns are evaluated heavily on growth rate (“slope”)—even if you start off behind, showing fast, consistent improvement is what earns return offers

SWE Internship Survival Guide [Part 6] - Onboard Efficiently

Onboarding efficiently is one of the most critical phases of your internship. Here are the core points from this lesson:

- Embrace being new—ask questions early and often, seek feedback, and don’t waste time being stuck on problems for longer than an hour
- Prioritize setting up your environment and making small code changes early to learn workflows and gain confidence
- Build relationships immediately: meet with your intern manager and schedule one-on-ones with at least two other teammates for broader support and perspective
- The sooner you engage and request help, the more value you’ll get from the relationship—and the less it will feel awkward or overdue later in the internship

Take the full onboarding course here: [The Complete Onboarding Guide For Software Engineers](https://www.jointaro.com/course/the-complete-onboarding-guide-for-software-engineers-succeeding-when-youre-new/)

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.