Should I include not-yet released projects on my resume/CV?

Question

I finished a website project with new technologies such as HTML5 and CSS3. But my company will not let it go to production. They plan to launch the new site in their new project version function.

Should I include such a non-yet-online project on my resume/CV?. Maybe with an additional explanation such as "this project is not released"?

Answer 1

This question is more about professional advice, than programming. That said, yes - there's zero reason not to list projects that may never be directly viewable.

If you're concern is showing like work, well guess the first thing you need to realize is that when you take on work like this, there a tradeoff in the overall value of the project to you long term. Just like if you were to work on an open source project where it would be okay to not only see the website, but the code behind it; for example, Ruby Koans (GitHub) and Ruby Koans (Online).

The phrase "like this project not in online" is unclear to me, since it might mean you're attempting to compare the work to work you did, or that it's like someone's work that is online that's not yours; don't compare your work to others, just cite your own as best as possible. I'd suggests something like:

• Project-Name-01 (www.name.com)
• Project-Name-02 (offline)
• Etc.

Just to be clear, I'm NOT saying how to organize/present the information, only to add the metadata of a URL or 'offline' to your existing project metadata.

Answer 2

If it is part of your current set of skills and experience, and relevant to the job you're applying for, by all means list it.

Potential employers should (and usually do) be realistic about real-world employment situations - most code you write cannot be shared freely, because you're usually bound to NDA's, copyright transfer, and similar restrictions. Just indicating the kind of project and what your role was is fine.

Just keep these things in mind:

• You should be prepared to answer questions about any projects you list; ideally, this will not only convince the interviewer that you did in fact contribute significantly, but also spark a professional discussion, which gives you an opportunity to present yourself as a capable and passionate candidate.
• You should still include some code samples; many employers (at least the better ones) expect this, as it gives them an easy way to pre-filter applications. Quite often, the job description explicitly demands code samples. If you can't be bothered to send code, then you're not worth considering anyway, and if you do, a quick glance can reveal whether your code is completely atrocious or worth a second look. You can use personal projects, or open source projects you contributed to, or maybe some freelance / contracting work for which you still own the copyright; if at all possible, also provide a working instance or link to one.
• Whenever you feel uncomfortable about giving implementation details, or you are unsure whether you are legally allowed to, it is OK to say so - showing some loyalty toward your previous employer indicates that you are also going to be loyal to a new employer; violating previous NDA's suggests that you might treat your new employer's code the same way.
• Don't bluff. If you list projects you weren't really involved with in a meaningful way, any half-decent interviewer will see through you within minutes, and when that happens, it's "don't call us, we'll call you". So don't.

Answer 3

Yes, include projects that they can't see. Over your career expect to work on some projects that are for internal use only. They may be parts of an intranet, or behind a pay wall. If you do any work for a government contract it will be even harder to show it. Also after you leave a contract the project may continue to evolve, and can no longer be representative of your work.

Answer 4

Did you work on it? Would you like prospective employers to know about it? Then put it on your CV. It's unfortunate that you can't let them see it firsthand, but you can still tell them about it and use that as a way to tell them what you know, which is really all they're likely o care about.