I'm alive


Reader,

Yeah I know what I said.

But so much has happened and I can't stay silent about it. I like to share as I build.

This course is coming along nicely.

Remember I told you I was quitting my newsletter to do this?

You probably don't. It's fine. My plan was:

  • Make a portfolio website (check)
  • Create better projects
  • Build my dream QA course

Turns out bullets 2 & 3 go well together. This is the first course of many.

For each course, I'll build the project I ask you to build, as I build the course.

I call it "Lesson-Driven Development" or "Project-Based Teaching". Not sure. Not married to a term yet.

But you get it. I'm literally doing the thing and then teaching how to do it. One step at a time.

I've got a lucky group of beta testers sitting in a Telegram channel giving me feedback on the course as I build it.

They're so smart, I'm so grateful they're volunteering to help me make this course amazing.

The best projects are group projects, as I hope I've drilled into your head by now.

Not just for your QA Automation portfolio, but for anything in life.

A few updates you should be aware of:

  • I named my business "Modern QA" and bought a domain name for it
  • I'm using that domain for my newsletter signup page, so share it with your friends
  • My blog is on a subdomain of that domain, but you probably know that already
  • The Modern QA newsletter is not exclusively about job hunting anymore, but instead I am going for a "future-proof your QA career" theme. If you think that's cool, stick around. If not, the unsubscribe button's at the bottom of the page. That said, what I talk about will include job-hunting advice or at least be relevant to your job hunt.
  • The way I write emails won't change at all. If you loved 'em before, you'll still love 'em. But I am aiming for sending daily emails now. You've been warned.
  • I started mentoring on ADPList again, but in a limited capacity. If my availability works for you, feel free to book.
  • As far as products or services go, the only thing I'm working on now is this course. I'll occasionally mention it, especially as launch approaches. Launch will be sometime in November.

I probably missed a few things. But anything cool I've done since my last email can be found on my website.

As for you, I'm happy to be writing to you again.

I missed this. I don't think I'll ever stop loving how it feels to write these emails.

I hope you'll join me for this next chapter. If not, it's been good.

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.

Read more from The Better Vetter Letter

Reader, This is a Senior Full Stack Engineer req I pulled from LPL Financial's careers page. REQ: https://career.lpl.com/job/R-047752/Engineer-II-Net-Full-Stack-Engineer screenshot just in case it gets taken down over the weekend lol So how do you vet candidates for this? For an Engineer II (senior), you are looking for the transition from "following instructions" to "owning outcomes." Years of experience are irrelevant if the candidate can prove they’re achieving at the appropriate level....

Reader,You struggle to vet technical requirements and position yourself to manage the decision maker well enough to move the deal forward. I’m not asking you. I’m telling you. I’m a boots on the ground full desk rep. I’ve had to think creatively to make matches work. I’ve also worked with hundreds of sales and recruiting leaders and sat in on their client conversations. When capable operators stall on true opportunities, it usually comes down to one thing: insufficient technical depth to spot...

Reader, Let's recap. In Part One, we saw how a vague, canned requisition left a sales rep struggling to do 2 things: align with the hiring manager define a clear candidate profile He'd send resume after resume to the hiring manager as the candidate profile was constantly changing. It became a fool's errand trying to get the right candidate for the role. The breakthrough came when an engineer joined the process. Their perspective didn’t just clarify technical requirements. It gave the rep the...