Senior devs. Is anyone else insulted by coding exams?
Hiring manager here-- we send out a coding assignment to do a small UI component.<p>It has its hits and misses.<p>Hits:<p>1. We suss out a lot of people who&#x27;ve been a senior engineer on their resume for years but aren&#x27;t up to date on practices we care about, like accessibility, semantic HTML, app architecture etc. That stuff is important, I don&#x27;t want to hire folks who ship apps, but the apps aren&#x27;t WCAG 2.0 compliant or poorly tested.<p>2. It can definitely help rescue a candidate that we&#x27;re on the fence about.<p>Misses:<p>1. Some candidates blow it off or phone it in, and out of fairness to those that did well, we can&#x27;t advance them. It&#x27;s a shame too, because often the reason they do that is because they have other offers on the table, or other companies they&#x27;re further along on, not because they have an attitude.<p>2. We say it&#x27;s a four hour assignment, but in truth people who do well take around 6-8. It&#x27;s not because the work takes 6-8 hours, but people go above and beyond, you can tell from the git commits.<p>Overall, I like it our coding challenge and won&#x27;t hire without it, but I&#x27;m not saying it&#x27;s perfect.