As an applicant I've not had any on a technical basis. A few years ago: "Bit too much of a solo developer, which can be great but not what we're looking for."

As an applicant I've not had any on a technical basis. A few years ago: "Bit too much of a solo developer, which can be great but not what we're looking for." Which is fair given that the context was they were needing to rapidly build a new core team for their first foray into microservices. I was perfectly happy with the response, because I'd say it's a fair personal assessment, clearly at odds with how they planned to build the team, and my role at the time was very much a "Me and the Admin" type scenario. When I've declined a role it has usually been due to a faint whiff of "Desperate eyed non-technical founder with a great idea" which I've usually characterised to them as being "Too accustomed to security of a more traditional company". Or in once instance I advised the hiring manager that it didn't seem they needed more devs at all, that the two they had seemed by his description to be drowning in BAU and support tasks, that him training or hiring administrators would probably be a better use of his budget and more likely to retain the domain expertise already baked into his existing devs, before more of them left...Which was accurate even if he hadn't just also told me that he'd increased internal adoption of their CRM system by making it a disciplinary matter if usage was low.