I'm a junior in college majoring in Electrical and Computer Engineering. I haven't "accomplished anything" that Evans would take seriously at this point. The main reason is that I'm extremely busy for most of the year. I work for probably between 55 and 65 hours a week on average. Could I contribute to open source projects or develop Android apps on the side? Sure, if I wanted to regularly stay up for four days at a time and accept a hit to my QPA. (I know people that do this.) Last summer, I wrote a good amount of code for internal use at the company I worked for, but I can't really go sticking that in portfolios. I hope that Evans will forgive me for taking an actual break on my winter break, as opposed to seeking out "real-world projects with real-world users" to contribute to in a way that I can demonstrate pre-interview. (I want to do systems software, so things that I would seek out to work on probably won't have that many direct "users.")
I can buy that a technical interview with no demonstration of coding ability might let through some inept people. I got my last internship with just one technical interview. I hope I turned out OK. The company I'm working for this summer had a more thorough process. The recruiter comes to campus and interviews people whose resumes they liked from the career fair a few weeks prior. I can't remember much about that interview, but I don't think it was very technical. It only lasted about half an hour. Later that day, everyone that interviewed got an email directing them to go to a website and take a timed test with various programming questions. Most or all of it was multiple-choice, and there might have been some short-answer questions. People who they liked on the basis of the interview and test came out for on-site interviews. There, I was given a programming problem and five hours by myself to solve it optimally. There was a guy somewhere else in the building who I think was looking at my code periodically who would come over at various times and ask me if I could do anything to improve performance for a particular input. After I was done coding (actually the next morning), the actual interview occurred. The interviewer had read my code (and maybe talked to the guy who watched me work), and he asked me to explain it and describe my thought process as I designed it. I'm pretty sure that was the most important interview. In the other one, I asked the interviewer how he liked the surrounding city, and he talked about that for 20 minutes.
I haven't started working there yet, so it's possible that I could still show up and be the new guy that can't code. I think I can code. In the last year, I've helped write most of a small OS kernel for ARM, and I've helped implement a basic MIPS processor in Verilog (not real programming, I know). Those were both partner projects, but the commit logs will show that I pulled my weight. Nevertheless, if Evans recruited for this company, he would probably complain that I was working on contrived problems and that nobody actually used my results. I don't think that means that it wasn't freakin' hard or that I didn't do a good job. The interview process seemed pretty solid, though. It also seemed pretty time-consuming. I've never hired or managed anybody, so I don't know how you decide how much time to spend on a candidate.