Expat Forum For People Moving Overseas And Living Abroad banner

1 - 7 of 7 Posts

·
Registered
Joined
·
832 Posts
Discussion Starter · #1 ·
Alright, so my case is a bit strange. Since I have only worked in a startup during the course of my entire professional career until now (total experience is nearly 5 years, as a software developer), the kind of projects I have worked on are fragmented and are not specific to any particular domain (although the base technology I use has remained constant). Another 'issue' (if you may call it an issue) is that almost all projects I have worked on are pretty small (due to the company being a startup), and have single-handedly completed entire projects on my own. This might give potential employers the impression that I'm not a 'team man'. Also, I have worked on way too many projects (probably more than 20).

Considering all this, would it be wise to simply not mention any projects on my CV at all, and only mention my general roles and responsibilities on my CV? If I am called for an interview, I can just take up a couple of projects related to the job I'm applying for and speak about it, right?

Kindly advice.
 

·
Registered
Joined
·
832 Posts
Discussion Starter · #2 ·
Could someone please answer this for me?
 

·
Registered
Joined
·
191 Posts
Show them as much as you can but don't lie. That's it
 
  • Like
Reactions: funkyzoom

·
Registered
Joined
·
832 Posts
Discussion Starter · #4 ·
Show them as much as you can but don't lie. That's it
Thanks for responding!

To avoid discrepancies, in my case, it is certainly better if I don't mention project details on my CV. Will employers/recruiters even shortlist candidates if the CV does not contain specific project details, but describes the roles and responsibilities in detail?
 

·
Registered
Joined
·
191 Posts
Thanks for responding!

To avoid discrepancies, in my case, it is certainly better if I don't mention project details on my CV. Will employers/recruiters even shortlist candidates if the CV does not contain specific project details, but describes the roles and responsibilities in detail?
In my opinion, just show what you have done, don't show details, for example: only show them the name and type of projects and you will explain more in the interview. It should be better. :fingerscrossed:
 
  • Like
Reactions: funkyzoom

·
Registered
Joined
·
832 Posts
Discussion Starter · #6 ·
In my opinion, just show what you have done, don't show details, for example: only show them the name and type of projects and you will explain more in the interview. It should be better. :fingerscrossed:
That seems to be a sensible 'middle path'. Thank you!
 

·
Registered
Joined
·
56 Posts
For smaller projects, you may want to bundle them under heading of 'Evergreening' or BAU or a single Maintainance project. Since your base technology is same, that should be fine. e.g As a Java developer, I've worked on Spring, Hibernate, Restful web services across multiple projects blah blah.

But yes, good to mention a few projects ( irrespective of size) which justify your job code description easily.
 
1 - 7 of 7 Posts
Top