I like this approach. I'm going to see what I can do to start incorporating more research into my application process. I always research the company to see if I even like them or their products. The thing I'm having trouble with right now is trying to figure out what stack a company is actually interested in using. Lots of job postings are very vague and list 5-6 languages, just as many frameworks, and some other vague bullet points. How is somebody even supposed to know what a company is asking for in their posting? It would be nice to know if I'd be a good fit without wasting time for both of us.
Yeah that can be really frustrating - one thing to point out is that sometimes such companies may be vague about tech stack (or list lots of different languages) because what tech you know isn't as important to them as, say, culture fit, business domain knowledge,etc.
Of course, this isn't the case all the time, but I've found it to be many times in my job searches.
And if the job posting itself is vague aside from tech stack, I've found that to be a red flag haha. I've found that companies that 1) know what they're looking for 2) know how to communicate that are usually better ones to work for. And I move on from the really vague ones
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.