Helping tech recruiters vet client requirements and job candidates for technical roles by blending 20+ years of Engineering & Recruiting experience.
The end of the line
The last stop on the QA Job Hunt ExpressAnd not just because it's the 69th email I've sent It's been a ride. Maybe you loved it, maybe you hated it. Maybe you opened 1 out of 69 emails I've sent and forgot to unsubscribe. But it's been a thrill to write for you. So why am I hanging it up? Simple, I'm bored ¯\_(ツ)_/¯ Well, not entirely that. I'm embarking on a new chapter in my professional journey. Well, that's not quite right, either. Simply put, I'm refocusing my energy on building. Not building offers. Not building an email list. Not building a social media following. Even though I can now boast almost 5k followers on LinkedIn, 750 on Twitter, and this email list is closing out at 253 people...recently, I looked at:
I'm not measuring up to my own expectations. I want to change that, because I'm setting a terrible example for anybody who's job-hunting or breaking into tech right now. I say one thing, but am doing another. And no, I don't think you "earn the right" to slack off on your online presence after enough time. It's like your home. You can get away with inviting your family over when you haven't cleaned anything, and maybe if you're a celebrity, nobody would dare point out how gross your house looks. But that doesn't make it right. Besides, the person who doesn't work on side projects relies 100% on their job to teach them new skills. If your GitHub is gathering dust, you're probably letting your employer decide your skill set. That's fine, unless it's not, right? I think back to when I was at Trek and I got to choose my own test automation stack for the native app they were developing. I chose Playwright. It seemed like the best tool for the job, even if their support for Electron apps was still considered "experimentally supported". Fast-forward only a few months, other QA folks in Trek and outside of Trek are talking about Playwright like it's some out-of-reach thing:
I was puzzled. What's stopping these people? Most folks seem to think they need to be "allowed to learn" or "put on a project" or "given time during the workday". As someone who's gone the self-taught route into tech, this mentality is absurd to me. Every year, more tools and technologies come out, with the earliest adopters being the folks willing to do side projects or who happen to work for companies who like letting their team experiment with new tech. Most people aren't going to be the 2nd category. They'll need to do a side project on their own time, not at work. I used to do side projects all the time. Then I got comfy. I let work teach me stuff. That was fine for a few years. But now my appetite is growing again. I want to dive deeper into not just QA Automation but also Frontend Dev and DevOps skills. It's the kind of thing you need to do on the side. Eventually, I want to teach people how to become a QA Automation Engineer. I'll need to use practice projects in the course, anyway. Might as well build some now. So while I think you should absolutely know how to job hunt like a pro, I've said all I wanted to say on that topic. I feel confident if you read back through all my emails, you have everything you need. I've even made them publicly available here, so don't worry if you deleted them. If I ever start a newsletter again, it'll be on a different subject. But I may not start another one. So, as some parting suggestions for you on your "Test Quest,"
My advice can be summed up in 1 sentence: View the world as it is, not as you'd like it to be. Dream big, yes, but when you decide what skills to have, base it on the current landscape, not your opinions of how the world "ought to be". It'll keep you safe in the job market, and you might just change your mind on a few things. Folks on the sidelines can think whatever they want, but in the arena, you find out what's true and what's not pretty quickly. Happy testing, folks. And if you feel like chatting, you know where to find me. But just in case you don't, my website's almost done. Cheers, Steven |
The Better Vetter Letter
Helping tech recruiters vet client requirements and job candidates for technical roles by blending 20+ years of Engineering & Recruiting experience.
Reader, On Monday we covered who to contact and when. You did the work, found the right recruiter and team. Now what? Let’s talk about the message itself. I read a lot of outreach. And I'll be direct: most of it sounds the same. Not because the people sending it are bad candidates, but because they're following an outdated professional template that signals "I didn't really think about this." I’m guilty of it myself. I have looked back and read outreach for sales activity I’ve done and...
Reader, The generic "apply and pray" approach doesn't do anything. It sends you straight to the bottom of a pile that a recruiter may never actually touch. As someone who works in technical recruiting, I want to pull back the curtain a bit. Because the people who actually hear back are playing the game smarter. And it all starts with who to contact. Step 1: Find the Right Recruiter What you want is a recruiter who is actively working in your space, ideally the one listed directly on the job...
Reader, Part 2: Decide Fast, Apply Smart. So you've read the posting.You've done your self-assessment. Now comes the part that most people get wrong: They either spend three hours crafting the perfect application for a role they were never going to get without trying other channels, or they do nothing at all because it feels overwhelming and just submit the sample resume “as-is”. Here's the rule I give every candidate I work with: If you're going to apply, don't spend more than 10 to 15...