More frustrating is when you complete the assignment (all tasks) but still fail because an unspecified task was not completed. My biggest learning about softwa

More frustrating is when you complete the assignment (all tasks) but still fail because an unspecified task was not completed. My biggest learning about software interviewing is spotting immaturity. I have it down to three points: 1) The only purpose to software is automation. It’s not data, entertainment, or anything else. If an internal team is not aggressively applying automation like static analysis or automated tests to their code they are not mature and I will not work there. 2) Does the team or employer understand the software platform they are hiring for? Software platforms are things like web browser, a game engine, terminal emulator, and so forth. I most commonly see over confidence about this when the employer is fully reliant on some framework to do everything. That is serious code smell because any deviation or problem outside the framework results in serious emotional problems. I do tire of emotional junior developers trying to define my job as some sort of infantile pacifier. 3) Can the team communicate in writing? I mean specifically the other developers. These failures are what I see in 95%+ of software employers. I am willing to take a massive pay reduction to join an employer that doesn’t fail from such immaturity.