Read time: 3 minutes

Hey there 👋🏼 - Ali here

Welcome to the 4th edition of Career Science

👋🏼 to all the data job seekers who are curious to learn the science behind landing their dream data role.

This Wonky Wednesday (somehow I always end up with a good W adjective) we’ll be discussing 5 mistakes to avoid to network like a pro (& avoid getting 100s of unanswered DMs).

Hold on to your SQL tutorials cause this one is a 3-minute read. Read this and ignore those job postings that require cover letters. The only time I am every submitting a cover letter is for a job as an astronaut.

Ready for the search science? Well then, let’s dive in.

😂 Meme of the Week

😵‍💫 Crazy Job Search Story

Just read that somebody turned down a job offer given to them on the same day. The reason will shock you. Honestly, I’d be all over that job offer. People are weird.

🔆 My Weekly Highlights

🏗️ Building Career Science: I took a break last week from writing my newsletter so I am excited to be back this week. I am also building a high-performance notion template to make you a 10x productive data job seeker.

🥾 Weekend Pic (end of the 📧): My hiking trip

🤏🏽 Job Search Nano-tip: Asses your job search progress after every week. Don’t overthink every decision every day. It’s a quick ticket to burn out.

🔥 Favorite Tweet: By Naval

🎯 Ali’s Aces (end of the 📧): This week we have:

  1. A job board just for data jobs

  2. An AI tool to build the perfect memory

  3. A recruiter telling you to stop being the most qualified (wait what?)

  4. A dataset on ‘Extreme weather deaths’. I bet your weather news channel didn’t predict this.

⚒️ Data Tool Tip of the Week (new)

Sometimes, you need to break down the problem into smaller steps to make it easier to solve. In databases, a similar idea applies when working with complex queries. You can use tools called Common Table Expressions (CTEs) and subqueries to break down a big problem into smaller, manageable pieces.

Subqueries: A subquery is like a mini-puzzle within a bigger puzzle. It's a way to use one query (the small puzzle) inside another query (the big puzzle). You use subqueries when you want to get information from one table based on information from another table.

Let's say you have a school database with two tables: "Students" and "Grades".

Students Table:

| StudentID | Name      |
|-----------|-----------|
| 1         | Alice     |
| 2         | Bob       |
| 3         | Charlie   |
| 4         | David     |

Grades Table:

|StudentID|Subject|Grade|
|---------|-------|-----|
|1        |Math   | A   |
|2        |Math   | B   |
|3        |Math   | A   |
|4        |Science| A   |

You want to find all the students who got an "A" in Math. Here's where a subquery can help:

SELECT Name
FROM Students
WHERE StudentID IN (
    SELECT StudentID
    FROM Grades
    WHERE Subject = 'Math' AND Grade = 'A');

In this example, the inner query (SELECT StudentID FROM Grades WHERE Subject = 'Math' AND Grade = 'A') finds all the StudentIDs who got an "A" in Math. The outer query then uses this list of StudentIDs to retrieve their names from the "Students" table.

Running the given query would result in an output like this:

| Name    |
|---------|
| Alice   |
| Charlie |

CTEs (Common Table Expressions): A CTE is like a helper table that you create temporarily to make your query easier to understand. It's especially useful when you need to repeat a certain piece of logic multiple times in your main query.

Imagine you're running a bookstore, and you want to find all the books that have been sold more than average.

Books Table:

| Title         | Sales |
|---------------|-------|
| Book 1        | 120   |
| Book 2        | 90    |
| Book 3        | 150   |
| Book 4        | 200   |
| Book 5        | 80    |

You can use a CTE to calculate the average number of book sales first, and then use that in the main query:

WITH AverageSales AS (
    SELECT AVG(Sales) AS AvgSales
    FROM Books)
SELECT Title
FROM Books
WHERE Sales > (SELECT AvgSales FROM AverageSales);

The CTE named "AverageSales" calculates the average sales across all books. Then, the main query uses this average value to find books that have been sold more than the average.

In simpler words, a CTE helps you set up a smaller, easy-to-understand table (like a helper) that you can refer to later in your main query.

Running the given query would result in an output like this:

| Title   |
|---------|
| Book 3  |
| Book 4  |

This is because the query first calculates the average sales across all books (assuming it's calculated as (120 + 90 + 150 + 200 + 80) / 5 = 128) and then selects the titles of books where the sales are greater than this calculated average (i.e., sales greater than 128). So, "Book 3," and "Book 4" have sales higher than the calculated average and are included in the output.

So, whether it's using subqueries to fetch specific data or using CTEs to make your query steps clearer, both techniques help you break down complex database problems just like solving puzzles piece by piece.

🔬 Deep dive into search science

Networking is no mystery.

It’s a skill you can learn.

Here are 5 mistakes to avoid to network like a pro (& avoid getting 100s of unanswered DMs)

Mistake # 1) Quantity over Quality

Sending 100s of connection requests in the hopes that somebody will respond is a bad idea.

Even if someone does respond the conversation never goes beyond “Thanks for connecting”.

And you never hear from the person ever again.

Instead, do this:

  • Find a select few active people

  • Research their backgrounds & comment first

  • Find areas where you can add value & offer to help

If you are networking with everyone you are networking with no one.

Mistake #2) Me Mindset Networking

“Can you look at my resume”

”Can you help me make a portfolio”

“Can you mentor me? I need guidance”

None of these will get you responses.

Nobody has time for a stranger.

Instead, do this:

  • Recognize something amazing about the person’s profile

  • Help the person achieve his or her goals (inquire first)

  • Share articles & videos on the person’s interest

Don’t expect to withdraw $$ from an account you have invested $0 in.

Mistake #3) Making Big Asks

Messaging someone to mentor you?

They’ll get overwhelmed and won’t respond.

It’s because it's a huge time commitment to mentor someone.

Instead, do this:

  • Get their advice on a book or course

  • Keep reply choices as A or B

  • Keep it easy for them

A: Should I subscribe to DataCamp

B: Should I pursue a Google Certificate

Since it’s a super low-commitment task.

They are more likely to respond.

Bonus: Follow up & tell them about the results of the advice.

Big asks get you ignored while small asks get you in.

Mistake #4) Never Following Up

On average 80% of people ignore emails 4 times before they respond.

Just following up increases your response rates significantly

But never following up gets you nowhere.

Instead, do this:

  • Add a short blurb about how valuable their time is

  • Mention that you greatly appreciate them

  • Ask them if they can refer someone

"I know how valuable your time is. Apologies, if you're not the right person to assist, could you steer me in the right person’s direction?

This works because of the Dunning-Kruger effect.

When people get their egos bruised they tend to react emotionally.

“How dare he think I am not the right person??” I’ll show him.

Follow up, stroke their ego & see the responses roll in.

Mistake #5) Not Building a System

Getting overwhelmed is easy when networking.

Who to reach out to?

What did we last talk about?

Did he/she respond to my message?

How long has it been since I last contacted them?

People quit when they are overwhelmed.

Instead, do this:

  • Use Google Sheet or Notion

  • Columns for last contact date & meeting notes

  • Reference these meeting notes whenever you meet again

Create a 2nd brain & give the 1st one some rest will ya?

Bonus Tip:

Networking fails miserably when you are vague about your 3 Ws:

→ What - connect on a shared experience or goal

→ Who - connect with who you can relate to

→ Why - connect with purpose

What - connect on a shared experience or goal

🔴 “Can you get me a job?”

🟢 "Hey [name], I saw your data visualization project and I am super impressed. I am working on something similar. If you are open to connecting then I’d love to show you and get your feedback on how I can make mine better. No worries if swamped with work"

Who - connect with who you can relate to:

🔴 Stop sending out 100s of random connection requests

🟢 Start sending out 100s of targeted ones with people whom you have common ground with (boot camp, education, work experience, etc.)

Why - connect with purpose

🔴 “Hi, Ali”

🟢 Have a strong call to action (CTA)

“I imagine making the transition from sales to data analytics wasn’t easy. I would love to learn more about your journey and the obstacles you had to overcome. Do you have a few minutes to chat about it? No worries. if busy. I can understand" (give a soft exit)

Go from ‘Me Mindset’ → To ‘We Mindset’

🙋How I can help your Data Job Search

Thanks for reading!

Whenever you are ready, here are 2 ways for us to work together:

  1. Reply to this email with ‘resume’ if you want a resume review ($25 only)

  2. Reply to this email with ‘coaching’ if you want 1:1 personalized coaching (pay when you land a job)

📊 Are you looking for a role in data?

🌎 Where are you from?

🤔 Got a minute? I'd love your feedback on today's newsletter

🎯 Ali’s Aces (Weekly Resources)

💼 Job Boards: A job board for data jobs

📚 AI Job Search Playbook: 50+ AI Tools & MORE

📊 Dataset for Practice: Dataset on extreme weather deaths

🥾🧗🏞️ Weekend Pic: Hiking Trip!

You can even see the “hidden job market” from up here! (there’s no such thing)

👋🏼 See ya!

Reached the finish line? Awesome. I’d love to know what you thought of the 3rd edition of Career Science? Reply to this email. I respond to every email!

Written by someone who doesn’t ghost 👻.

Keep reading