| Exactly. Has the author never worked for a different employer? It's very common in a lot of companies for developers to be excluded from (hearing about / learning about / have input on) something, simply because they don't have (specific job title). That's a legitimate concern. Even tiny 10-ish person companies often fall into this trap. The companies that promise candidates not to worry about job titles because "we're a flat organization", "we're agile", "we're a meritocracy" tend to fall into this trap even more than the older ones do -- knowing and using the right buzzwords is almost a red flag in itself. So, completely hypothetically, these are all problems that would be bad and should be avoided, as the author writes. But in practice, it sounds like a candidate was concerned about making sure they'd have enough authority to actually make improvements and not just shoved onto busywork at random. And instead of addressing that concern in any meaningful way, the company took that as an opportunity to respond with a bunch of buzzwords and ad-hominems, and then pat themselves on the back about it. |