|
Hi fellow data professional! In undergrad, in pursuit of a coveted TV internship, I once cold messaged an alum of my school using an email I found on his acting reel. When we finally got on the phone it wasn’t the warm handshake connection I was seeking; he spent time grilling me on my intentions and skills. After I hung up I thought “what a jerk.” In my yet-to-be-developed mind I thought as long as I went to the effort of getting someone on the phone they’d reward that initiative with a job, not greet my eagerness with skepticism. A few calls and emails later resulted in me skipping 2 interview rounds and getting a job offer. Recently, I saw the term “virtual coffee” used and I thought “oh, that's what I was doing...” "Virtual Coffee" is the act of creating favorable conditions for a cold conversation without expectation, the same reason single folks go on coffee dates. In the professional world, the "Virtual Coffee" is the "Third Door." Most folks are banging on the Front Door (the HR portal/ATS), competing with 500 other resumes for the attention of a tired recruiter. Others are looking for the Back Door (an employee referral), which is great, but requires you to actually know someone well enough to ask for a favor. The Virtual Coffee is the side entrance. It’s for the person who isn’t asking for a job today, but is asking for a blueprint. The reason this works (and the reason my undergrad self failed at first) is that a job request is a heavy lift. It requires the other person to stake their reputation on a stranger. A coffee chat, however, is a low-lift ego boost. People love talking about their work, their mistakes, and their "grizzled" opinions on whether Jupyter or VS Code is the best way to write production code. By framing your ask as a "virtual coffee," you’re signaling that you aren't there to sell; you're there to ingest. And that lack of pressure is exactly what creates the "favorable conditions" I mentioned earlier. Here is the secret: When you treat someone like an expert rather than a gatekeeper, they stop acting like a jerk and start acting like a mentor. That skeptical alum from my TV days wasn't trying to be a jerk; he was vetting me. Once I stopped looking for a handout and started looking for insight, the dynamic shifted. This extra step provides: • A role's "Unspoken" Requirements: Learning that the team actually hates dbt and wants someone who knows Airflow, which can be critical info that isn't in the job description • The Skip-Level Advantage: Transitioning from a "cold contact" to a "known entity" before an opening even goes live • Professional Enrichment: Sometimes, I just walk away with a new tool to research or a query optimization tip If you’re currently slogging through a job search or feeling stagnant in your current role, I suggest finding a side door. Find an alum, a LinkedIn connection, or an engineer at a company you admire. Offer them 15 minutes and a virtual coffee. No pitch, no resume attached to the first email, just a curiosity about how they built what they built. And if they’re too busy, the next best thing is to ask if you can send them specific questions to answer by email. It might be awkward at first, but it’s the most effective way to ensure your reception is as warm as that cup of coffee. And if you want to make yourself more findable, learn how to suppress any professional shyness and crush virtual introductions with my shameless approach to personal branding. 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! 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,...