[ETR #99] You're Doing Nepotism Wrong


Hi fellow data professional!

For my health I try not to argue with my wife; but when she told me her networking plan I had to push back.

Some context.

She’s exploring career paths within the multinational corp she works for and wanted to meet with a friend of a family member.

The catch? She felt weird about leveraging a personal connection and wanted to reach out cold.

This is the wrong approach.

Western culture demonizes nepotism but, truthfully, sometimes a connection is so painfully obvious it would be stubborn to not leverage it. Besides, over 50% of professionals report landing a job as a direct result of a personal connection (MyPerfectResume). Either the other half of respondents didn’t have a connection or were too “uncomfy” by the idea.

The worst thing that could come of this is making the connector (family member) feel awkward if the candidate turns out to be a bust. Reaching out cold to a family connection might make you feel like you’re playing “fair” but this is risky.

If you haven’t worked in a corporate environment, org IT teams create as many guardrails as possible to deter unsolicited communication. Taking the “right” path would most likely land you in the spam filter and if you have an uncommon domain like .aol or .yahoo your message might be rejected entirely.

My prevailing stance on networking is never outright ask for a job, as it puts the other party in the uncomfortable position of rejecting you.

Since you’re most likely not the child of an executive you’ll still need to apply and interview, even with a (person) on the inside.

Tactful nepotism involves these asks:

  • Information on the scope/availability of roles
  • “Inside info” on interview questions, including possible business quirks/problems
  • A “fast pass” to breeze past ATS so you’re not rejected just because you didn’t upload your resume as a PDF

I’ve never benefited from nepotism in the data/tech world.

But, coming from a journalism background, the entire field was built on human relationships, from source cultivation to internships with the explicit goal of getting “an in.” You’d have to look no further than my career advisor’s social handle, (at)mr.connect, to see how ingrained personal connections were in us baby reporters.

Based on that imperative I made intentional connections, like cold messaging an alum who got me one of those ATS fast passes, and incidental connections, like a former intern who happened to sit next to my friend at a finance event.

The latter proved to be invaluable in providing the exact questions my interviewer asked.

Look, we know it’s a tough market. If you haven’t thought about asking your uncle for an intro to his frat brother who’s a director of dev ops at a Fortune 500, this is your permission to do that (of course, this works on a much smaller scale).

Because while you might feel weird about the reason you got your first job, your fellow candidate definitely won’t.

Don't have any connections currently? Read about the odd but effective tactic to master low-pressure networking.

Thanks for ingesting,

-Zach Quinn

Medium | LinkedIn | Ebooks

Extract. Transform. Read.

Reaching 20k+ readers on Medium and over 3k learners by email, I draw on my 4 years of experience as a Senior Data Engineer to demystify data science, cloud and programming concepts while sharing job hunt strategies so you can land and excel in data-driven roles. Subscribe for 500 words of actionable advice every Thursday.

Read more from Extract. Transform. Read.

Hi fellow data professional! SQL Lite, the database you most likely learned SQL on, is built atop 100k lines of source code. Sound like a lot? Compare that to Chromium, the engine for Google Chrome, which boasts 30+ million lines of code under the hood. Shortly after acquiring Twitter/X, the world's first trillionaire, Elon Musk, famously asked engineers to tell him how many lines of code they wrote per day, igniting a debate among engineers throughout the software and data domains. When I...

Hi fellow data professional! If you read my note on Tuesday you’ll know I’m coming off of the data engineering week from hell that seeped into my personal life, and delayed the launch of something cool I was planning to share with you; if you want to know more about that, scroll to the end of this message. Last week a flagship data source had a major problem and since it’s within my ownership area, I was the one with the knowledge and responsibility to fix it. I wanted to share the experience...

Hi fellow data professional! Hardly a work day goes by without receiving a request from a data analyst. They range from the mundane “Can you add this column?” to the occasional emergency “The data didn’t load all weekend and the leadership call starts in 15 minutes!” At the end of a jam-packed week I received an unusual request: Help with a Python script. My teammate wanted to know: Best practices How to commit to GitHub What the best way to deploy is They admitted the task was simple,...