|
Hi fellow data professional! Next time you think you’ve tried everything in your job search, remember: I once worked with a guy who got hired at a national broadcast network on the strength of his parody rap. The intern, Jake, didn’t have a network or elite contacts, but he wanted an internship at The Tonight Show, a competitive role with over 10,000 applicants per semester. So, he recreated a shot-for-shot parody of a song previously performed on the show, rewritten with lyrics specifically for the staff. The result? Jimmy Fallon hired him personally on-air. Now, a cynical read says he just did something "extreme." I take the optimistic view. He was purposeful, he was creative, and most importantly, he did the work. If you’re currently applying for Data Science or Engineering roles, you’ve seen that LinkedIn prompt: See how you compare to 1,000 other applicants. It’s the ultimate TMI for job candidates. That 1 line of text doesn't tell you who is a bot, who is unqualified, or who actually did the work. But it does fuel the "vicious cycle" of needing experience to get experience. In a tightening market, being "privately good" at what you do isn't enough. You need to build and market yourself in public. When my colleague Jake got hired for his rap, hundreds of people tried to copy him. The results were cringeworthy. They saw a "shortcut" when the "overnight success" they witnessed was actually built on 100+ hours of craft and creativity. Increasing your visibility isn't about LinkedIn "hacks" or asking for a job the day after graduation. It involves adapting a systematic Calling Card strategy:
If a hiring manager finds your work on r/dataisbeautiful or reads your technical breakdown on Medium, you aren't just an applicant anymore. You are a proven commodity. You’ve demonstrated domain knowledge, technical design, and, most importantly, the courage to go public with your work. Jake’s video wasn't just a gimmick; it was a resume-worthy product. In an era where AI can generate a basic Python script in seconds, your ability to document a complex, manual, and creative process is one of the remaining moats between those who learn how to code and those who can truly build. Read the full profile to learn how to build something you won’t want to keep private. Thanks for ingesting, -Zach Quinn Medium | LinkedIn | Ebooks |
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.
Hi fellow data professional! I learned one of the most important personal branding lessons in the basement of Arizona State University. I was seated at my desk in the Post Office/Writing Center as my coworker, a fellow writing tutor, reviewed my resume. “The content is good, but I won’t remember this. There’s no branding.” She thought for a second. “You know what? Change the font color to navy. Your brand is now blue.” I laughed but she was serious and the interaction imprinted on me not the...
Hi fellow data professional! This edition almost became an apology because I’ve been on a tight deadline and pre-baby morning wake up thinking/writing time has become GSD (get sh!t done) hour. Long story short: I got brought in late to a time-sensitive project that required me to speed through a planned pipeline migration. As a recovering news junkie (aka journalist), I used to live and die by deadlines. But, given the unpredictability of data-oriented work and internal deliverables, it’s...
Hi fellow data professional! For years, the opening of The Simpsons, specifically Bart writing lines on the chalkboard, has been incredibly relatable to me. Not because I’m up to mischief (none I’ll admit to here, anyway), but because I spend most days writing the same three lines of SQL over and over again. If you've ever been paranoid about a table's content, you might know what I'm talking about. It’s the aggregate COUNT(*) grouped by a date field, ordered by date DESC. The output of that...