4 ms·
To make it clear, these are questions for the interviewee to ask the interviewer. They are also designed for an candidate in a job working with many other deve
by dalke 11y ago
To make it clear, these are questions for the interviewee to ask the interviewer.
They are also designed for an candidate in a job working with many other developers, and deploying primarily web-based software in an IT-heavy environment.
If you are hired as the sole software developer for a non-programming group, then most of the questions make no sense. For example, I mostly work with chemical research groups, where there is no mandatory code review as I am the only developer, and where the deployment is to install to /usr/local/bin .
Also, '100% test coverage' is a meaningless goal. It's trivial to force 100% coverage, and does that mean line or branch coverage? Coverage testing is a way to find where you need more test, but it mustn't be the end goal.
- preston4tw 11y agoHey, thanks for taking a look. This is spot on. Most of the technical questions are aimed at startups / software shops that are hiring for growth / large enterprise companies with tons of IT. They become less relevant if you're the sole IT guy in a non-software shop. There still are a number of questions we feel are relevant to any position that are important to ask such as health care provider, retirement fund, etc. If you have any suggestions for questions to add we'd love to hear them. The removal of questions (ex. the test coverage) we put more consideration into. I think questions like that are valuable to the extent other people find it valuable. Certainly if no one thinks test coverage is a good question to ask then we'd remove it. Thanks for the feedback.