I think the 'correct' (from the perspective of getting an interview) approach would be to personalize your resume to include skills that are called out in the listing, even if you've just read a tutorial on it. Not to list a ton of irrelevant skills.
An example would be if you had 5 years of experience in AWS and only a few tutorials of GCP for experience, but the listing specifically wants GCP skills, you list it.
Not a case where you have 5 years of backend experience and start applying to senior frontend positions because you went through a React tutorial.
So it's not possible to be openly gay and hire-able?
I mean, sure, that must be true for some companies but I wouldn't want to work at those anyway.
edit: on second read, this might come off as more aggressive than I wanted, and the rest of the post is pretty good, but this part just stood out to me
Maybe it's just sour grapes from me, but it feels like a lot of these acquisitions are for has-been companies that were great 10+ years ago but haven't had much success lately. Bethesda, Double Fine, and now Activation Blizzard.
Just to add to this, I feel like there's a ton of ways to "accidentally" introduce a lot of bias in hiring: referring everyone from your college's club to the company, brain teasers that require some irrelevant cultural background, mandatory in office/remote cultures, off site decisions. Heck I even saw a company that advertised that they go surfing together every weekend for bonding.
I'm not sure what can be done with these cases, and I know people, of various protected out-groups, that have specifically mentioned those as reasons not to join a company.
Welcome to Q3 I guess. I'm going to be spending a large part of this time backing up various sites and creators that I want to keep track of, since I feel like this is going to get worse.
Another day of this, and this specific event (not counting the other outages) will bring Twitter down to two-nines of availability since the acquisition/layoffs.
I recently interviewed at a place where the interviewers kept calling me bro or dude, so maybe they'll match with each other at some point.
Without wanting to get into a discussion of the gender-neutrality of those words, I'm not a man and everyone that I talked with there was, and it just felt odd.
Late response, but in Q1 I got about 3 call backs, 2 turned into a full "onsite" loop, but both seem to have ended from things I couldn't control (position closed because startup's product launch got pushed back by almost a year; layoffs/weird decisions around monetization announced a month or two later.)
Q2 I feel like my resume response rate is better, and I've had 4-5 "onsite" loops, which got me 1 reject and 3 (all in June) where I'm waiting for a response.
5 years of experience at no name startups in data science/mle, hard req for fully remote positions, visibly part of a controversial minority.
but also, yes, I totally agree with you that some of this "oh you're a late bloomer, you'll want to do it when your older" stuff comes off as condescending if you actually just don't want to own a house with 2.5 kids.