1–10 of 26 posts
Unfortunately I’m also trying to find a job. I’ve been stuck at as a mid level engineer with a 5 YOE. I’m debating whether or not I should put it on my resume.
I love seeing our candidates having outside projects/etc but we make sure that there is a clear delineation between what our company offers vs what is done by the employee.
If not putting it on your resume will help filter them out.
Essentially put yourself in the hiring managers shoes and say 'what's in it for him/his company/the role being done well'.
On the positive side, it gives the hiring manager, if they care for that, a signal that you can build and ship stuff. You have tried building your own company and has more experience around the challenges that most devs do not have. I love to interview people who built stuff.
On the negative side, it also signals that you might not be as committed to the new company since you are pursuing something on the side, or has demonstrated that you want to pursue something other than the engagement you are applying for. I’m not saying that you can’t do both things at once, or that X is better than Z. Just stating how it might come across and can negatively affect your job search.
As long as you consider these two sides and come up with a “solution” to this, you are in the path to make an informed decision and can “defend” your position.
Good luck!
B) your resume should be tailored to the particular job. So you’d want to gauge whether it’s valuable on a case by case basis.