[ETR #98] The $100K Pre-Graduation Email You Must Send


Hi fellow data professional!

It’s baseball season in the U.S., a game defined by the "on-deck" line up. Before a player takes a big swing at the plate, they are already there, weighted bat in hand, timing the pitcher (who has to move a bit faster now thanks to the pitch clock), fully prepared for their moment. They don’t start looking for their helmet only after the umpire calls them up.

In your early career perhaps you're considering "taking a big swing" by applying for that dream role at a company aligned with your business interests or pivoting into a higher-impact position.

Undoubtedly, you're focusing intently on the technical screen and system design interviews. In the process, however, you're leaving out a key part of the process.

Setting your line up.

Aka confirming a reliable group of professional references.

I learned this the hard way while working at a Disney resort (Fort Wilderness for any WDW frequent travelers).

At the time, I was working a bike rental window, sweating through a shift while balancing a 4-stage interview process for my first data role. I had nailed the interviews. The hiring manager was ready to make an offer. Then came the inevitable HR email: "Please provide three professional references who can speak to your technical competence by EOD."

I spent the next three hours in a frantic, cold-sweat scramble. Between checking out surrey bikes for guests, I was ducking behind the counter to text old supervisors and email former colleagues I hadn't spoken to in a year.

It was unprofessional and stressful.

And entirely avoidable.

Upon reflection, I've contrasted that period with my high school self. Back then, I was methodical about gathering recommendation letters for college months in advance. Somewhere between graduating and entering the workforce, I lost that discipline. I assumed the "big swing" was the only thing that mattered.

If you are a new grad, or a professional eyeing a change, the time to line up your references is now, not when you’re 48 hours away from a potential offer. For those of you finishing up the semester, the "dead week" between final exams and graduation is the perfect window. Your favorite professors are still in "student mode," and the impact of your work is fresh in their minds. Don’t just let those relationships fade into a halfhearted LinkedIn connection; cement them with a commitment to ongoing dialogue.

Not sure what to say? Use this relationship-building template that can be customized for either a professor or former colleague.

Subject: Professional Reference / Catching up - [Your Name]

Hi [Name],
I hope you’re doing well! I’m currently [graduating/moving into a new phase of my career] and am starting to interview for [Job Title] roles.
Because we worked together on [Project/Class], I’ve always valued your perspective on my [specific skill, e.g., SQL optimization/Python ETL logic]. Would you be comfortable serving as a professional reference for me if I reach the final stages of a hiring process?
I’ll be sure to give you a heads-up and send over the job description before anyone reaches out.
Best,[Your Name]

And if you need to brush up on your cold messaging skills, check out this guide.

By doing the legwork now, you ensure that when you finally take that big swing, the only thing you have to focus on is knocking it out of the park.

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,...