Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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"?

share|improve this question

closed as off-topic by Snowman, gnat, MichaelT, Kilian Foth, durron597 Apr 7 '15 at 13:08

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking career or education advice are off topic on Programmers. They are only meaningful to the asker and do not generate lasting value for the broader programming community. Furthermore, in most cases, any answer is going to be a subjective opinion that may not take into account all the nuances of a (your) particular circumstance." – Snowman, gnat, Community, Kilian Foth, durron597
If this question can be reworded to fit the rules in the help center, please edit the question.

Could you explain what you mean by launch the new site in their new project version function. Is it an internal website? – PersonalNexus Jan 28 '12 at 6:22
Its My company website,. I added the new Project information in my project, Its not ready now. So they not put that in online. The Older site is still running. – Sagotharan Jan 28 '12 at 6:34
I wonder what people did before the Internet existed? What did they ever put on their CV? – Oded Jan 28 '12 at 11:33
Why the interview tag? – Burhan Ali Jan 28 '12 at 17:46
If people could only ever put on their CV things which went public, a great many of us would have almost completely blank CVs for much of our career. A CV is about what experience you have had, not what experiences other people can verify that you have had without contacting your referees. *8') – Mark Booth Jan 30 '12 at 19:26
up vote 3 down vote accepted

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 (
  • 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.

share|improve this answer
offline tag is very nice. Thanks. Can you tell me, this offline project affect my interview?. Will they want to show my Project?. – Sagotharan Jan 28 '12 at 6:36
@Sagotharan: Impossible to say for you, though for me it's never affected any professional dialogs to my knowledge in my case; clearly though, someone seeing a resume with viewable work is more likely to be contacted. – blunders Jan 28 '12 at 6:51

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.
share|improve this answer

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.

share|improve this answer

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.

share|improve this answer
Ya I am worked. In this project I am only worked. – Sagotharan Jan 29 '12 at 6:01

Not the answer you're looking for? Browse other questions tagged or ask your own question.