Skip to main content

Top 10 Job Interview Tips for Software Developers

This post maybe a little off the usual thread of my usual Technical posts but I feel it has to be said.

Since moving to Singapore and trying to build a development team I have found myself inundated with resumes, in the last 6 months alone I have probably read in excess of 500 resumes and interviewed less than 5% of that number and thought I would share some tips for any hopeful developers.

Most of this should be common sense, but the funny thing about common sense is that it’s not so common.

1. Prepare
Research the company before going for an interview. If you know who’s interviewing you then Google them and see what they’re about. This can help give you an idea of the types of questions you will get in the interview.

There’s no excuse for not even having a basic idea of what the companies core business is.

2. Acronyms != Interesting Resume
There are no prizes for the most acronyms you list. As a rule only list those that you are able to discuss in detail for two minutes or more.

3. Relevance
Customize your resume for the specific role you are applying for.

If it’s a C# role, then a full page dedicated to a project you did using COBOL back in the 80’s is not going to win you any points.

4. Keep It Simple Stupid (KISS)
Keep your resume to four pages or less. Write it so that all the important information can be viewed in 10 seconds or less.
Bullet points are as always a great way of conveying concise information.

I usually read resumes on my iPhone whilst on the daily commute so less is best.

5. Be Honest
Don’t exaggerate your years of experience. The fact you did a one month internship in your final year of study does not equate to one years work experience.

6. Read the Ad
Read the job ad carefully and follow any instructions. If the ad says “Please apply via our Job Portal” then actually apply via their job portal and not via the website the ad is on. 

Attention to detail and the ability to follow instructions are paramount to the success of a developer.

7. Not too Early, Not too Late
There is a fine line between arriving too early and arriving too late, for me that line is 15 minutes either side of the interview time.

Even though it is annoying I am less concerned with candidates who arrive more than 15 minutes early. But if you’re more than 15 minutes late and don’t call then to let me know you’ll be late then you shouldn’t bother coming in at all.

8. Communication
Communication is key to the success of any development team & it’s important to demonstrate this in the interview.  
Listen to the questions and take the time to formulate answers before speaking, avoid mono-syllabic answers but also be careful not to hijack the interview. An interview is not the time for you to rant incessantly about the latest “X” technology.

9. Ask Questions
Asking questions shows that you are inquisitive mind and able to communicate effectively, again both skills that are important for an aspiring Developer.

10. Keep your Web Presence Clean
The first thing I do and many recruiters do is type the name of a candidate into Google and see what results it brings up.

No presence at all can show that you’re not engaged with the community. On the flipside those photos of you wasted at the weekend do nothing to help your cause.

My usual process is to search Google, Facebook, Twitter and LinkedIn.


Well that’s my list.

If you’re a C# Developer or JavaScript whizz and fancy working in Singapore then check out some of our job openings or drop me a line on

Popular posts from this blog

Freeing Disk Space on C:\ Windows Server 2008

  I just spent the last little while trying to clear space on our servers in order to install .NET 4.5 . Decided to post so my future self can find the information when I next have to do this. I performed all the usual tasks: Deleting any files/folders from C:\windows\temp and C:\Users\%UserName%\AppData\Local\Temp Delete all EventViewer logs Save to another Disk if you want to keep them Remove any unused programs, e.g. Firefox Remove anything in C:\inetpub\logs Remove any file/folders C:\Windows\System32\LogFiles Remove any file/folders from C:\Users\%UserName%\Downloads Remove any file/folders able to be removed from C:\Users\%UserName%\Desktop Remove any file/folders able to be removed from C:\Users\%UserName%\My Documents Stop Windows Update service and remove all files/folders from C:\Windows\SoftwareDistribution Deleting an Event Logs Run COMPCLN.exe Move the Virtual Memory file to another disk However this wasn’t enough & I found the most space was

3 Reasons Why Progressive Web Apps (PWAs) Won’t Replace Native Apps

Many people believe Progressive Web Apps (PWAs) are the future of the mobile web, but in my opinion, PWAs are not a replacement for native mobile apps. Here are three reasons why: 1. Native mobile apps provide a smoother & faster experience  Mobile websites, progressive or otherwise are slower and not as smooth. 90% of the time spent is spent using apps vs the browser . The single most significant contributing factor to a smooth experience on mobile is the speed of the network and latency of the data downloaded and uploaded. When you visit websites on desktop or mobile, there is a lot of third-party code/data that gets downloaded to your device, which more often than not has zero impact on the user experience. This includes: CSS (Cascading Style Sheets) JavaScript Ad network code Facebook tracking code Google tracking code The median number of requests a mobile website makes is a shocking  69 . On the other hand, native apps only get the data that is requi

Unit Testing Workflow Activities in .NET 4.0

  Recently during a catch up with my buddy Keith Patton I was (as I tend to do) singing the praises of the Workflow in .NET 4.0. The all important question about Unit Testing support was raised, I tried as best as I could to explain the new In and Out Arguments but I didn’t feel I was convincing enough, so I though I would clarify with a blog post. If you developed Workflows in .NET 3.5 then you will be well aware of the lack of Unit Test support which was due to many reasons but mostly in part to the complex Workflow hosting environment. When moving to .NET 4.0 Workflow Foundation from .NET 3.5 it pays to be conscious of that fact that there is no longer a distinction between Activities and Workflows. Everything derives from the System.Activities.Activity class. So the definition of a Workflow is just a collection of of 1 or more Activities. I have designed a very simple Rental Car Activity which takes the an Applicants age as the input and outputs a True or False depending o