Getting Your Next C# ASP.NET Job: Part 2

Introduction

This is the second part of a series of posts I am writing on "Getting your next C# ASP.Net job ". This article has two sections:

  1. Deciding to get a new job
  2. Finding the Job

Deciding to get a new job

So there's many reasons you need to get a job and although its not a major part of this series it is worth considering because sometimes you might not realize it's time to move on.

  • First job: So anyone out of University or School or just someone starting in the industry must go through this at some point in time. It's not that easy because you have never been through the process but as long as you enter an organization at the correct level you will have an even chance. This is important though, it is important to make sure if you are a new graduate you go into a role as a junior developer and not a mid level or senior role. Learning the ropes is key and working with a good mentor is so important - and that's not going to happen with senior roles; further, you will have much greater expectations.
     
  • Its time: Many people get to the stage in any role when its just time to move on. There are many reasons for this but at the end of the day its just plain and simple as one great developer once said to me "When the love is gone, the love is gone".
     
  • Still writing VB3: Not that there is anything wrong with VB3 but unless it's a cracker of a job, it probably is time to move on into the new world.
     
  • The jobs not the job: This is when your job has changed and its not really up your alley. This can happen when you get promoted, start taking on team lead roles or just stop coding for one reason or another. Whatever the reason, if you aren't coding anymore and you want to code, if your work can't give you the coding job then have a look around.
     
  • Organisation change: A bit like the point above. When the organization/company has changed or enforced a structure change it's possible that the environment and the job will change too and if that doesn't suit your ability to code happily again then it might be worthwhile looking for a new job.
     
  • End of Contract/Getting fired: This can happen to any of us and when it does, get back on the horse cowboy.

Finding the Job

Sometimes you might be lucky enough to get a call from a friend or colleague for a new job. That's great when it happens but when it doesn't there are a few things to do when looking for that new job.

Keep a network and use it now. Whenever you move (i.e. leaving University/College, leaving a workplace, leaving a development conference etc…) keep in contact with your colleagues. Get their email address and keep them in the loop with what you are doing. When looking for a new job its always worthwhile checking with your contacts in regards to what cool roles are going around. It's all about networking.

  • Job Search Engines- There are many job search engines - they can all be beneficial!!
  • Your Referee is your friend- I'll cover Referee's in the Resume section but always remember, if they are good enough to vouch for your work then they are good enough to contact and say "Hey its me - anything happening at your work?"
  • Developer Shop Websites- All the big development shops in Australia have websites where they look for new talent. Always check out the employment section on the site for details.
  • Conferences/Code-Camps- I know a few developers who have picked up jobs at conferences.