Extract. Transform. Read.A newsletter from Pipeline: Your Data Engineering ResourceHi past, present or future data professional! Somewhere along your professional development journey someone lied to you. They told you to crank out resumes because no one reads cover letters. This couldn’t be further from the truth as 87% of hiring managers read cover letters. Such a high read rate represents a compelling opportunity to sell your data skills and showcase a bit of personality. The problem? Those pesky 3 paragraphs take way too long to write—as long as 30 minutes per job. Assuming you’re applying to 3-5 jobs per day, you’re looking at 2.5 hours of cover writing time. Earlier this year, while helping a friend apply for data science positions, I created a simple Python script to auto-generate cover letters based on input. In addition to generating a cover letter based on my more than 500 hours as a career advisor, it will convert your output to a PDF, the preferred format for cover letters and resumes. Even if this helps you generate cover letters faster, you might want to think twice about “spamming” your resume/cover letter. Only use a bulk application method if:
Since I’m not trying to ask you to spend 30 minutes on this email, here are this week’s links:
Finally, this week is significant to me because 9/13 marks 3 years in data engineering. Read my story and advice for following a similar path. Why I Nearly Turned Down A 30k Raise And A Data Engineering Job Questions? You know where to find me: zach@pipelinetode.com. Until next time - thanks for ingesting, -Zach Quinn |
Reaching 20k+ readers on Medium and nearly 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 past, present or future data professional! If you’re in the U.S., Happy Thanksgiving! I’m prepping for my food coma, so I’ll make this week’s newsletter quick. Like millions of Americans, I’ll be watching NFL football (go Ravens!). The average NFL game is 3 hours. If you can skip just one of today’s games and carve out that time for professional development, here’s how I’d spend it. In the spirit of football, I’ll split the time designation into 4 quarters. Documentation pass - if you read...
Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! In 2 weeks or so The Oxford English Dictionary will reveal its 2025 word of the year, a semi-democratic process that lends academic legitimacy to words like “rizz” (2023’s pick). If you’re currently employed or interact with white collar workers, you would think the word of the year is “headwinds.” Used in a sentence: “We’ve pivoted our AI strategy but still encountered headwinds that...
Extract. Transform. Read. A newsletter from PipelineToDE Hi past, present or future data professional! After choosing a dataset, one of the most significant decisions you must make when creating displayable work is: How am I going to build this thing? For some, you may try to “vibe code” along with an LLM doing the grunt technical work. If you choose this approach, be warned: Nearly half of all “vibe code” generated contains security vulnerabilities and that’s before you even consider its...