My comment is going to come across as mostly a nit - I'm definitely the target audience here as I'm just coming off of a short break and diving into interviews.

My comment is going to come across as mostly a nit - I'm definitely the target audience here as I'm just coming off of a short break and diving into interviews. I'll update my post with more thoughts as I go through it, as I'm sure it'll be a decent resource to brush up on my DS&A. There's kind of a focus on education here in the "skills section" that I don't find to be true after a certain level of experience. > "Must have" — Typically, most of the must-haves include a degree (or not) in a relevant technical field, some years (or not) of experience in a particular programming language or technology I'm not sure I agree with any of this - there are some domains like say embedded where having no C experience is an absolute must have, but to my knowledge almost nobody is thrown out of a pile for not using the specific key language a company is using, like say C# vs Java vs Cpp. Of course there's some red flags as in if you're doing modern frontend work and the resume only notes PHP4. Also I have always treated degree requirements as optional, unless the role focuses in a specific area of research rather than general SWE. All of my positions in my career have required a degree which I don't have and I don't feel held back by it at this point. IMO at least, accomplishments > YoE > degree is much better outside of entry level.