Mixing
How to mention project names on CV where name can't be disclosed due to non-disclosure agreement
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
22
down vote
favorite
As the title pretty much says, how should we mention a project name on a resume or CV where the actual name can't be revealed due to a non-disclosure agreement.
Funny it may sound, while the technology and overall purpose can be mentioned, the actual name can't be revealed.
How should we go about naming these projects?
Currently, I am using the following convention:
[Name not revealed due to NDA]:
Basic functionality of project...
Tools and Technologies...
resume non-disclosure-agreement
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
migrated from programmers.stackexchange.com Jul 27 '12 at 10:22
This question came from our site for professionals, academics, and students working within the systems development life cycle.
add a comment |Â
up vote
22
down vote
favorite
As the title pretty much says, how should we mention a project name on a resume or CV where the actual name can't be revealed due to a non-disclosure agreement.
Funny it may sound, while the technology and overall purpose can be mentioned, the actual name can't be revealed.
How should we go about naming these projects?
Currently, I am using the following convention:
[Name not revealed due to NDA]:
Basic functionality of project...
Tools and Technologies...
resume non-disclosure-agreement
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
migrated from programmers.stackexchange.com Jul 27 '12 at 10:22
This question came from our site for professionals, academics, and students working within the systems development life cycle.
5
Personally I'd replace the name of the project with a short description "Foobar Frobnicator based on Quux Technology" instead of "Frobnicatorator2000".
– Joachim Sauer
Jul 27 '12 at 8:08
5
This is not a problem that's unique to software development.
– ChrisF
Jul 27 '12 at 8:10
1
Why don't you just list what your job function is at the job instead of listing projects. What projects you worked on tells very little about what your actual skill set is. Somebody working on Office 2013 doesn't have to list they worked on Office only worked in the Office group within Microsoft.
– Ramhound
Jul 30 '12 at 14:33
add a comment |Â
up vote
22
down vote
favorite
up vote
22
down vote
favorite
As the title pretty much says, how should we mention a project name on a resume or CV where the actual name can't be revealed due to a non-disclosure agreement.
Funny it may sound, while the technology and overall purpose can be mentioned, the actual name can't be revealed.
How should we go about naming these projects?
Currently, I am using the following convention:
[Name not revealed due to NDA]:
Basic functionality of project...
Tools and Technologies...
resume non-disclosure-agreement
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
As the title pretty much says, how should we mention a project name on a resume or CV where the actual name can't be revealed due to a non-disclosure agreement.
Funny it may sound, while the technology and overall purpose can be mentioned, the actual name can't be revealed.
How should we go about naming these projects?
Currently, I am using the following convention:
[Name not revealed due to NDA]:
Basic functionality of project...
Tools and Technologies...
resume non-disclosure-agreement
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
edited Jan 12 '13 at 17:07
GreenMatt
15.6k1465109
15.6k1465109
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
asked Jul 27 '12 at 8:04
Shamim Hafiz
211126
211126
migrated from programmers.stackexchange.com Jul 27 '12 at 10:22
This question came from our site for professionals, academics, and students working within the systems development life cycle.
migrated from programmers.stackexchange.com Jul 27 '12 at 10:22
This question came from our site for professionals, academics, and students working within the systems development life cycle.
5
Personally I'd replace the name of the project with a short description "Foobar Frobnicator based on Quux Technology" instead of "Frobnicatorator2000".
– Joachim Sauer
Jul 27 '12 at 8:08
5
This is not a problem that's unique to software development.
– ChrisF
Jul 27 '12 at 8:10
1
Why don't you just list what your job function is at the job instead of listing projects. What projects you worked on tells very little about what your actual skill set is. Somebody working on Office 2013 doesn't have to list they worked on Office only worked in the Office group within Microsoft.
– Ramhound
Jul 30 '12 at 14:33
add a comment |Â
5
Personally I'd replace the name of the project with a short description "Foobar Frobnicator based on Quux Technology" instead of "Frobnicatorator2000".
– Joachim Sauer
Jul 27 '12 at 8:08
5
This is not a problem that's unique to software development.
– ChrisF
Jul 27 '12 at 8:10
1
Why don't you just list what your job function is at the job instead of listing projects. What projects you worked on tells very little about what your actual skill set is. Somebody working on Office 2013 doesn't have to list they worked on Office only worked in the Office group within Microsoft.
– Ramhound
Jul 30 '12 at 14:33
5
5
Personally I'd replace the name of the project with a short description "Foobar Frobnicator based on Quux Technology" instead of "Frobnicatorator2000".
– Joachim Sauer
Jul 27 '12 at 8:08
Personally I'd replace the name of the project with a short description "Foobar Frobnicator based on Quux Technology" instead of "Frobnicatorator2000".
– Joachim Sauer
Jul 27 '12 at 8:08
5
5
This is not a problem that's unique to software development.
– ChrisF
Jul 27 '12 at 8:10
This is not a problem that's unique to software development.
– ChrisF
Jul 27 '12 at 8:10
1
1
Why don't you just list what your job function is at the job instead of listing projects. What projects you worked on tells very little about what your actual skill set is. Somebody working on Office 2013 doesn't have to list they worked on Office only worked in the Office group within Microsoft.
– Ramhound
Jul 30 '12 at 14:33
Why don't you just list what your job function is at the job instead of listing projects. What projects you worked on tells very little about what your actual skill set is. Somebody working on Office 2013 doesn't have to list they worked on Office only worked in the Office group within Microsoft.
– Ramhound
Jul 30 '12 at 14:33
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
18
down vote
If your Project name is the same as the product name you need to modify it sufficiently enough to not let a person guess the name easily. But don't leave it blank. Use a one line description (really short) which will give an idea of the project.
But make sure you don't de-emphasise the importance of the client. That matters more than the name of the project.
Typically you will modify this:
Project Name: MegaERP System
Client: FloorMart Inc
to:
Project: A large ERP system to handle the entire end to end business of a retailer
Client: The Worlds largest (or "The country's largest") Retailer
If "Worlds largest" is not appropriate as it a dead giveaway you may want to use some ranking such as
Client: Among the top 3 retailers worldwide as per Fortune magazines 2012 ranking of
retailers (or any reputed business magazine who conducts such surveys).
edited Jul 27 '12 at 18:32
svick
12314
answered Jul 27 '12 at 10:18
DPD
53125
4
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
add a comment |Â
up vote
5
down vote
Another alternative is to have your resume be about tech and not about the project. As someone reading resumes, I don't care about the details of your project. I might care about the domain or the size. But not the name or what it does.
By explaining the basic functionality and tech stack you've covered everything I could reasonably need to know. So why waste a line on the CV saying that you can't say the name. That just calls attention to the fact that it isn't there.
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
18
down vote
If your Project name is the same as the product name you need to modify it sufficiently enough to not let a person guess the name easily. But don't leave it blank. Use a one line description (really short) which will give an idea of the project.
But make sure you don't de-emphasise the importance of the client. That matters more than the name of the project.
Typically you will modify this:
Project Name: MegaERP System
Client: FloorMart Inc
to:
Project: A large ERP system to handle the entire end to end business of a retailer
Client: The Worlds largest (or "The country's largest") Retailer
If "Worlds largest" is not appropriate as it a dead giveaway you may want to use some ranking such as
Client: Among the top 3 retailers worldwide as per Fortune magazines 2012 ranking of
retailers (or any reputed business magazine who conducts such surveys).
edited Jul 27 '12 at 18:32
svick
12314
answered Jul 27 '12 at 10:18
DPD
53125
4
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
add a comment |Â
up vote
18
down vote
If your Project name is the same as the product name you need to modify it sufficiently enough to not let a person guess the name easily. But don't leave it blank. Use a one line description (really short) which will give an idea of the project.
But make sure you don't de-emphasise the importance of the client. That matters more than the name of the project.
Typically you will modify this:
Project Name: MegaERP System
Client: FloorMart Inc
to:
Project: A large ERP system to handle the entire end to end business of a retailer
Client: The Worlds largest (or "The country's largest") Retailer
If "Worlds largest" is not appropriate as it a dead giveaway you may want to use some ranking such as
Client: Among the top 3 retailers worldwide as per Fortune magazines 2012 ranking of
retailers (or any reputed business magazine who conducts such surveys).
edited Jul 27 '12 at 18:32
svick
12314
answered Jul 27 '12 at 10:18
DPD
53125
4
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
add a comment |Â
up vote
18
down vote
up vote
18
down vote
If your Project name is the same as the product name you need to modify it sufficiently enough to not let a person guess the name easily. But don't leave it blank. Use a one line description (really short) which will give an idea of the project.
But make sure you don't de-emphasise the importance of the client. That matters more than the name of the project.
Typically you will modify this:
Project Name: MegaERP System
Client: FloorMart Inc
to:
Project: A large ERP system to handle the entire end to end business of a retailer
Client: The Worlds largest (or "The country's largest") Retailer
If "Worlds largest" is not appropriate as it a dead giveaway you may want to use some ranking such as
Client: Among the top 3 retailers worldwide as per Fortune magazines 2012 ranking of
retailers (or any reputed business magazine who conducts such surveys).
edited Jul 27 '12 at 18:32
svick
12314
answered Jul 27 '12 at 10:18
DPD
53125
If your Project name is the same as the product name you need to modify it sufficiently enough to not let a person guess the name easily. But don't leave it blank. Use a one line description (really short) which will give an idea of the project.
But make sure you don't de-emphasise the importance of the client. That matters more than the name of the project.
Typically you will modify this:
Project Name: MegaERP System
Client: FloorMart Inc
to:
Project: A large ERP system to handle the entire end to end business of a retailer
Client: The Worlds largest (or "The country's largest") Retailer
If "Worlds largest" is not appropriate as it a dead giveaway you may want to use some ranking such as
Client: Among the top 3 retailers worldwide as per Fortune magazines 2012 ranking of
retailers (or any reputed business magazine who conducts such surveys).
edited Jul 27 '12 at 18:32
svick
12314
answered Jul 27 '12 at 10:18
DPD
53125
edited Jul 27 '12 at 18:32
svick
12314
edited Jul 27 '12 at 18:32
svick
12314
edited Jul 27 '12 at 18:32
svick
12314
12314
answered Jul 27 '12 at 10:18
DPD
53125
answered Jul 27 '12 at 10:18
DPD
53125
answered Jul 27 '12 at 10:18
DPD
53125
53125
4
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
add a comment |Â
4
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
4
4
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
+1 When reading resumes, I don't care about the name of the project; "Project FooBar 9000" is meaningless. I want to know what you did and what effect it had on the business.
– Steven A. Lowe
Jul 27 '12 at 19:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
Yes, it actually doesn't matter much, but in my country it is the accepted practice. The only time it may become useful is when it is used in an intra-organization resume.
– DPD
Jul 30 '12 at 6:27
add a comment |Â
up vote
5
down vote
Another alternative is to have your resume be about tech and not about the project. As someone reading resumes, I don't care about the details of your project. I might care about the domain or the size. But not the name or what it does.
By explaining the basic functionality and tech stack you've covered everything I could reasonably need to know. So why waste a line on the CV saying that you can't say the name. That just calls attention to the fact that it isn't there.
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
add a comment |Â
up vote
5
down vote
Another alternative is to have your resume be about tech and not about the project. As someone reading resumes, I don't care about the details of your project. I might care about the domain or the size. But not the name or what it does.
By explaining the basic functionality and tech stack you've covered everything I could reasonably need to know. So why waste a line on the CV saying that you can't say the name. That just calls attention to the fact that it isn't there.
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
add a comment |Â
up vote
5
down vote
up vote
5
down vote
Another alternative is to have your resume be about tech and not about the project. As someone reading resumes, I don't care about the details of your project. I might care about the domain or the size. But not the name or what it does.
By explaining the basic functionality and tech stack you've covered everything I could reasonably need to know. So why waste a line on the CV saying that you can't say the name. That just calls attention to the fact that it isn't there.
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
Another alternative is to have your resume be about tech and not about the project. As someone reading resumes, I don't care about the details of your project. I might care about the domain or the size. But not the name or what it does.
By explaining the basic functionality and tech stack you've covered everything I could reasonably need to know. So why waste a line on the CV saying that you can't say the name. That just calls attention to the fact that it isn't there.
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
answered Jul 28 '12 at 20:04
Jeanne Boyarsky
4,7741934
4,7741934
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f2855%2fhow-to-mention-project-names-on-cv-where-name-cant-be-disclosed-due-to-non-disc%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
5
Personally I'd replace the name of the project with a short description "Foobar Frobnicator based on Quux Technology" instead of "Frobnicatorator2000".
– Joachim Sauer
Jul 27 '12 at 8:08
5
This is not a problem that's unique to software development.
– ChrisF
Jul 27 '12 at 8:10
1
Why don't you just list what your job function is at the job instead of listing projects. What projects you worked on tells very little about what your actual skill set is. Somebody working on Office 2013 doesn't have to list they worked on Office only worked in the Office group within Microsoft.
– Ramhound
Jul 30 '12 at 14:33