5

I'm a new professional software developer and I have a rather odd situation.

My job, while being technical, is not in a tradional software environment. I am the sole developer who was hired to slowly take over a senior developer as he is edged out since he decided to take another job.

I accepted my current job after I submitted a code sample, my senior project in school, and they extended an offer. I do not plan on leaving, as I love the atmosphere and my co-workers, but if I ever do want to leave or if something happens and I get let go, should I have code samples for future employers since my current job isn't easily compared with bigger companies and the heirarchy they may use? I.e. Junior Dev, Dev, Senior Dev, etc..

I classify myself as a Junior Software Developer, if that matters to anyone.

  • 4
    It can't hurt to have samples, some employers want them, others don't, but the more arrows to your bow the better. – Kilisi Oct 2 '16 at 2:44
  • 2
    Get involved in an Open Source – paparazzo Oct 2 '16 at 3:41
  • 7
    @Micheal: You have to get involved in open source, or have a side-project. You can't just go giving out code samples of your employers code (you don't own it) to other people without permission. – PeteCon Oct 2 '16 at 8:06
  • 4
    As a caution. NEVER give out code samples from your previous employers, in case this didn't really cross your mind. You WILL BE SUED. – Nelson Oct 3 '16 at 1:24
  • 4
    Even if you didn't sign NDAs, code you produce have assumed IP rights of the company because you are producing said code under employment. Code created under employment is the company's, not yours. I forgot the specific term at the moment, but I've read about it couple times here. – Nelson Oct 3 '16 at 1:31
4

Yes! You should have code samples (but not of code you wrote at work unless you have permission in writing from your employer - that code is theirs, not yours) regardless of anything unusual about your current job, it can't hurt you to have them handy and might help a lot.

since my current job isn't easily compared with bigger companies and the hierarchy they may use? I.e. Junior Dev, Dev, Senior Dev, etc..

I think specific titles on a resume are less interesting than details about what you did, so you shouldn't worry too much about that. Everyone who has been in the industry long enough to be reviewing resumes as part of their job has seen bad developers with senior titles and great ones with junior titles. Just describe what you did on your resume and you'll be fine.

  • 2
    Code samples are always good... To Mel's point, you can't give out your company's property, unless, of course, you convince them to open-source some of the work, in which case you get the benefit of building your portfolio while at work! – silencedmessage Oct 5 '16 at 2:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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