I am currently applying for a position and have been asked to essentially write two small apps. I started wondering if I should put some license on the code before I submit. I honestly do not keep up with all the different licenses, but know there are many to choose from.
The question is should I put a license on the code? If so which one and why?
You are writing, for free, an application he specifies to apply for the job? Wow.
Yeah, I'd submit it with a copyright message with your name at the top of each file. After all, its your work. Either he won't care (its just a test), he'll think you're paying attention (likely to do well, and you might get paid for the small app), or he'll object (at which point you should run).
I would not give my intellectual property away so freely. I believe this is a dangerous precedent. I would instead demo an existing application or send them code snippets.
Personally, I recommend you do not write these small applications.
CodeProject has a nice page that summarizes various licenses at http://www.codeproject.com/info/Licenses.aspx
[Is] a rough guide to the current licenses supported on The Code Project. Please read them carefully by following the links to the license pages themselves because some categorisations (such as whether code can be used commercially, or whether extensions must be release to the public) depends on the situtation. This is merely a guide: it's up to you to read the actual license carefully before using code licensed by each license or assigned a license to code you submit.
Your comment:
[Done] at home, and I was asked when I would have them done. They are definitely trivial type applications, that really seem to be designed to be thought provoking and to help them get an idea about how you think. They do want a copy of the code. Essentially the next interview would be a code review around the code I wrote. As you pointed out, I have no way to know the true intent of the company.
If they are trivial, then I would only include your contact information that you use in your resume at the top of each source code module. (You should do this for anything submitted to potential employer.) Copyright is implied, so leave it out to show good faith on your part. Anything else is too formal.
I already expressed my concerns and will not repeat them. Therefore, I hope this is good company and presents a positive long-term career move. Good Luck.
You are saying "put a license" like (or at least I got this impression) you're putting some restrictions on your code. But it's exactly the opposite. The license, by definition, gives some rights, not restricts them.
Your work is copyrighted by default. Without the license they have no rights on your code -- no right to distribute, modify, use, sell, whatever.
(IANAL)