|
Hi fellow data professional! Once, during a virtual interview, I had to nod politely as my interviewer apologized for coughing after their cigarette. Oh, and to make this situation even more cringe—they were driving. Some industries design stressful interview processes to psychologically test a candidate’s poise under pressure. Luckily (for the most part) the software engineering field is not included in this basket of high-stress tests. Sure, we are subjected to moderate stress in the form of whiteboard sessions or system design discussions, but nothing beyond the expected pressures of on-the-job development. So when something doesn’t go quite right during an interview, it’s understandably stressful. Handling unforeseen obstacles requires a mixture of calm and an ability to “read the room” to determine the severity of the interruption. In low stress situations, like when I forgot how to share my screen, it’s perfectly acceptable to call yourself out as long as it is done tactfully like: “Sorry; I’ve been coding all day and I’ve forgotten how to share my screen.” Bookending your humble admission with a statement about being so dedicated to work that a mundane task has slipped your mind can actually work in your favor. But if you find yourself in a “fish out of water” moment, like when I had a virtual interview my interviewer was clearly conducting while driving, it can be a bit difficult to maintain professionalism. In broadcast journalism I learned that the mark of a good reporter is being able to maintain composure in the face of technical failure. A trick I used if a mic wasn’t working or remote connection couldn’t be completed is to count backwards from 10 and try only one more time. If you can’t resolve an issue on 2 attempts, it’s best to quit and alert the other party to the issue rather than extending the awkwardness beyond a reasonable timeframe. Something candidates tend to forget is that you can end an interview for any reason; you’re not trapped. Personally, I’ve ended two interviews in the first 5 minutes because I felt that the recruiters misrepresented the role in the posting. Remember, when you accept a cal invite, an interview is your time too. Thanks for ingesting, -Zach P.S. One of the most deceptively difficult interview steps is nailing the phone interview; I wrote a guide to prepare you for technical phone screens in just 30 minutes. 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! In a previous newsletter, I mentioned an idea that I wanted to explore deeper. At the risk of double-quoting a la The Office’s Michael Scott quoting Wayne Gretzky (“You Miss 100% Of The Shots You Don’t Take - Waynze Gretzky - Michael Scott”), here is the idea. “To be marketable as a candidate, you don’t just want to show how you can go from A to B (requirements->pipeline). You need to go from A to C (requirements->pipeline->scale/support).” You might be asking...
Hi fellow data professional! Remember when the world ended? This month, 6 years ago, the world shut down and entered “unprecedented times.” Shortly after COVID-19 was designated a pandemic, I was unceremoniously furloughed from my day job at Disney World for 3-ish months. During COVID while others quarantined, I was on the move. After quickly feeling isolated in our third floor Central Florida apartment, my now-wife and I joined millions of other American 20-somethings who took a pandemic as...
Hi fellow data professional! I’ve broken my own data project rule. I’ve used the same data over and over again. For 3 years. It sounds boring but that depth exposure may actually be one of the few moats that slows encroaching AI. A little context: I support subscriptions, newsletters and growth for my employer. Spoiler alert: These areas are all basically the same thing. And they use basically the same three data sets. While I have opportunities to jump to other projects, this has been my...