Great Article on Interviews for Software Engineers

Really excellent article for anyone thinking about a new job and in particular interviews.

I want to highlight some very important points raised by the author:


“Study Technical Questions – Basic Questions, Rehearse Difficult Questions, White Board, Write Down Missed Questions
  • Every time while going for any interview be prepared with basic questions, research some difficult questions with the answers prior to it.
  • After coming back from an interview, write down the missed questions.”

Prepare, Prepare, Prepare. This is an important event. Treat it like a really hard exam.

Also, learn from the experience. Keep a record of questions in a doc.


  • “Dress appropriately. Be on time. Arriving 30 minutes early is good
  • Take two forms of maps: Because sometimes you will get traffic on any road; you have to know another road. Also, sometimes if you have taken a photograph into mobile and unfortunately the battery of your mobile gets discharged, in these cases, you have to carry a print out of the maps with the detailed address.”

OK, that might seem very straightforward but rushing or being late to an interview.


Part 4 Getting your next c# job : finding the job

This is the fourth part of a series of posts I am writing on “Getting your next c# job ”

Sometimes you might be lucky enough to get a call from a friend or colleage for a new job. Thats 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 (ie leaving UNI, leaving a workplace, leaving a development conference etc…) keep in contact with your colleagues. Get there 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 what cool roles are going around. Its all about networking.

Seek /monster etc…  – Seek is big here in OZ. Monster is big everywhere – there are lots of 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 – they are good enough to contact and say “Hey its me – anything going at your work?”

Dev 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 devs who have picked up jobs at conferences – seriously if you don’t have a linked in profile – get one now

Next Part 5 Creating the Resume

Any other ideas let me know


Part 3 Getting your next c# job : Deciding to get a new job

This is the third part of a series of posts I am writing on “Getting your next c# job ”

So there’s lots of 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 realise it’s time to move on.

First job – so anyone out of Uni or School or just someone starting in the industry has to go through this at some point in time. Its not that easy because you have never been through the process but as long as you enter an organisation 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 thats not going to happen at senior roles – further, you will have much greater expectations.

Its time – lots of people get to the stage in any role when its just time to move on. There are lots of 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 there unless its 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 – have a look around.

Organisation change – a bit like the point above – when the organisation/company has changed or enforced a structure change it’s possible that the environment and the job will change too and it that doesn’t suit your ability to code happily again 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.

Next – Part 4 finding the job