[kunj2aan]

Well tell us how you arrived to the conclusion that you are good at coding, pick up new things quickly and you are a good hire.

Did you solve a problem that no one else did? Did you create something that you found amazing? Did you collaborate with someone and he told you that you are good? Did your previous manager/professor tell you this or evaluated you positively in a coding project? Did your peers in the technical community do anything that lead you to believe you are good? Did you build something that some one is using and he liked it enough that you felt you could do it again? Did you ace some CS related subject and you are very confident in that domain? Did you win an award in a competition?

Just tell us how you arrived to that conclusion.

[saber3004]

I got to that conclusion based on the work I did in a startup I interned at during the summer before my senior year. I had a project there where I worked with a more senior employee and was able to make significant contributions, despite having only recently learned the technology at that point. I suppose that he would make a good reference. For what it's worth, I've also been told that I'm good by my classmates based on my work on class-related projects or homework. Thanks for the question, though. It's really made me think.

[tsurantino]

Right but he mentioned resumes.

On resumes, the first filter is the most relevant degree. How do you bypass that in the context of HR filtering thousands of resumes?

A lot of this advice is stuff that you can talk about in an interview, maybe briefly in a cover letter. A resume? Might be tough (especially if you don't have a lot of previous employment experience).

I'm just trying to play a bit of devil's advocate here because I'm also very curious about this question.

[saber3004]

Thanks for the reply. You pretty much nailed my problem.