[yamtaddle]

> > 2. Employers are overwhelmed with large numbers of applicants, most of whom don't meet the requested minimum requirements.

> Because many/most employers are willing to hire people who don't meet the minimum requirements. Or rather, they are sloppy when they made the job posting. Therefore, applicants who actually honor the minimum requirements are at a disadvantage.

Seriously—treat "requirements" as "a wishlist" is basically job hunting 101—because it works. Sucks for the employers who really, super-duper mean it when they write "requirements", but that's not most of them.

> 5. Write in reasonable detail about the interview process. Will it involve Leetcode style questions? Etc.

I swear to god, some companies protect this stuff like it's a state secret. I promise you that making details of your process public, or at least sharing them with applicants on first contact, won't ruin it. If FAANG can practically provide a study guide and get by, I'm pretty sure Jim Bob's House of Software or Boring Business Bank Incorporated isn't going to be ruined by providing a schedule and some guidance on the kind, difficulty, and broad domain of any technical assessments that will be performed. Meanwhile, leaving candidates with no clue what to expect when the real-world range of what happens in these interviews is unreasonably enormous, is simply shitty.