Top data engineering writer on Medium & Senior Data Engineer in media; I use my skills as a former journalist to demystify data science/programming concepts so beginners to professionals can target, land and excel in data-driven roles.
[ETR #27] 1 Sheet To Get You Promoted/Hired In 2025
Extract. Transform. Read.A newsletter from Pipeline Hi past, present or future data professional! It’s the most wonderful time of the year… performance reviews. Depending on your outlook on your job/org, that “wonderful” could be sarcastic. However, if you’ve landed on your manager’s nice list, this can be the time to recap your achievements to maintain credibility and work toward the next rung on the corporate ladder. If you’re on a small team serving demanding stakeholders it’s possible you’ve done way too much to easily recall individual achievements. Enter the brag sheet: A 1-page document recapping your contributions, initiatives and achievements. If you’ve heard the term, it was most likely in the context of college applications, as a prep sheet for your teachers to write nice stuff about you, aka recommendation letters. But you can use the same template to create a record of on-the-job wins you can reference to prep yourself for any formal reviews. I created and shared a “brag sheet” with my manager since he was on leave for most of the summer. In that situation, the doc is mutually beneficial because I maintain visibility for contributions and save a lengthy back-and-forth exchange to “get up to speed.” My sheet was a simple Google Doc with these headings:
Even if you’re not currently working in a data role, I would argue there’s definitely a benefit to recording skills, work and achievements you’re proud of. Your sheet might include headings like:
Instead of formally presenting this doc to a hiring manager, you have an opportunity to use it as an interview aid. It’s much more natural to recite your achievements written in casual language than it is to rattle off your resume’s bullet points. So take time to brag a bit—even if it’s just to yourself. Links:
Thanks for ingesting, -Zach Quinn |
Pipeline To DE
Top data engineering writer on Medium & Senior Data Engineer in media; I use my skills as a former journalist to demystify data science/programming concepts so beginners to professionals can target, land and excel in data-driven roles.
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! From 2014-2017 I lived in Phoenix, Arizona and enjoyed the state’s best resident privilege: No daylight saving time. If you’re unaware (and if you're in the other 49 US states, you’re really unaware), March 9th was daylight saving, when we spring forward an hour. If you think this messes up your microwave and oven clocks, just wait until you check on your data pipelines. Even though data teams...
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! As difficult as data engineering can be, 95% of the time there is a structure to data that originates from external streams, APIs and vendor file deliveries. Useful context is provided via documentation and stakeholder requirements. And specific libraries and SDKs exist to help speed up the pipeline build process. But what about the other 5% of the time when requirements might be structured, but...
Extract. Transform. Read. A newsletter from Pipeline Hi past, present or future data professional! To clarify the focus of this edition of the newsletter, the reason you shouldn’t bother learning certain data engineering skills is due to one of two scenarios— You won’t need them You’ll learn them on the job You won’t need them Generally these are peripheral skills that you *technically* need but will hardly ever use. One of the most obvious skills, for most data engineering teams, is any...