To understand why, think about what we hope to happen. If we do things right, then anybody we hire today will be a de-facto leader two years from now, because they're one of the people who's been around since the early days. Any code they write will be in core parts of the system. And they're going to have a big effect on who we can hire next, because potential hires are going to judge our company partly by them.
We definitely try not to waste anybody's time. But we also don't want to miss a good candidate; some really solid programmers don't interview well. But as soon as we're sure, we politely stop the process and thank them for their time.
If you keep getting passed over, however, I can see how that starts to really mount up.
If you keep getting contacted by companies for interviews, but fail to get past that stage, I would recommend two things. 1. Make absolutely sure that your resume is accurate. If, in the interview, it looks like you 'embellished' your qualifications on your resume a bit too much, it is guaranteed to get you tossed into the 'no' pile. 2. Work on your interview skills. It is surprising how bad some people interview. It took me a couple practice tries before I really became comfortable with the process.