Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My opinion on the matter is that every employer has unique expectations that they pretend are industry standard and obvious. I'll relate this to your statement by saying, they don't know how to try because interviews as a process are like crossing a field of landmines.

Too much academic work or management responsibility, they call you overqualified. To little: they say you aren't trying.

Enthusiastic for a low end job: we shouldn't hire them because their expectations are too high. To low of energy: they aren't the right fit.

This goes on and on and on as hirers act like their individual set of criteria bias are obvious -- likely because the interviewer themselves has limited experience.

Most people do best when they are told what to do in blind situations. Help them out with a few tips on what to expect and I'm guess you'll find much better applicant quality.



Sure, there are certainly some land mines, but then there's also pure sloppiness.

A double digit percentage of the resumes I see have spelling and grammatical errors in them. How hard is it to spend a few minutes checking over a document that is pretty key to your career?


Good engineers can be bad at English. I've seen C-suite briefings and strategy docs with obvious errors in them.

Unless you're working in publishing, I'd pay less attention to trivial errors than to evidence of an ability to get useful things done.


This is proof that you can counter-argument anything. Just proofread your damn resume (or engineer yourself a spellchecker).


Bad at English and attention to detail are two different things. Thoroughness, attention to detail, and knowing how to rigorously shake something down for at-a-glance defects are all skills -- disciplines -- I would expect out of a good software developer.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: