Most of our vetting of candidates happens during the interview.  However, we use references as a sanity check before an offer is made.  If you are looking for a job, make sure you have someone who is willing to speak on your behalf.  

Going through an interview, then delay repeatedly when asked about references is a sure way of not getting an offer.  

If you are not ready for a new job, and just want to see what the market is out there.  Then you are wasting everyone's time.  

David in Vancouver

I was doing an interview today for a QA.  The candidate I was interviewing had 20+ year of experience in IT, 12 of which was in QA.  I want to like this guy.  But it wasn't meant to be.  My QA Manager asked the candidate how he would estimate the effort required for QA on a new project / product.  He went round and round about how there are many variables involved, and here are his considerations.  The only thing that tells me, is that if this guy works with us, he won't give us a straight answer.  Next!

The best thing anyone can do, when asked a question.  Is to answer it genuinely.  Really think about how you can answer.  If you don't know, just say I don't know how to go about answering that question.  I would like the opportunity to learn how to do that.

Answer the questions and be honest about it.

David in Vancouver

Some common sense tips from a Google Recruiter.  Have a read here. 

It is possible to get a job in technology without having a relevant degree.  Besides from my previous discussion about getting relevant experience in coding, there are other categories of jobs that doesn't require a technical background to start.

For e.g., in our Quality Assurance department, we often hire people that doesn't have the technical background.  A good QA is detailed oriented, and can plan and schedule activities.  The required knowledge around QA can be picked up in a matter of a week.  And most of it is common sense.  Note, you should know the difference between black-box versus white-box testing.  White box testing, automation, and regression frameworks will require a development background, whereas black-box testing does not.  

Is quality assurance right for you?  It depends.  Are you OK with repetitive tasks?  Do you enjoy finding issues and writing up reports?  Do you believe in quality?  If the answer is yes, then learn a bit more about QA and get started.  There are some strategies involved to get a non-technical person hired as a QA resource.  Interested?  Contact us.

I recently received a hand written note from an perspective hire after our interview.  The note was short and to the point.  The content isn't very different from a thank you email.  The difference is the effort required to write, and deliver the hand written note.  

He was hired on that same day.  

Be different than everyone else and stand above the crowd.

Good luck job hunting!

David in Vancouver

Resume Diarrhea is a resume where it is cluttered with experience, half of which isn't relevant.  I know you have years upon years of experience, but honestly, I don't care if you done work in Lisp back in the 80's.  Look at the position posting, figure out what's relevant, then trim.  Having a resume that's easy to read, which shows breadth of knowledge and expertise than one that's littered with 4 pages of technical projects using outdated technology.  

Don't have a resume diarrhea.  Be concise and clear!

Good luck job hunting.

David in Vancouver

Most people have 1 resume and a standard cover letter template that they use for all potential jobs and employers.  Be different.  Go through the company's website.  Determine if key executives have blogs.  Read these blogs to understand their corporate technology direction.  

Now, look  at your resume.  Is it relevant to what they are hiring and looking for?  If you have lots of C++ experience, and they are looking for a PHP developer.  You better make sure you highlight relevant experiences, and remove ones which aren't relevant.  If you have time, get some relevant experience by working on a personal project using the language that would most resonate with your future employer.

Good luck job hunting!

David in Vancouver.

Of the hundreds of people I have interviewed over the years, I had less than 10 people that brought their work to show me.  Of those 10 people, I think I hired 80% of them.  Build something, be proud of it, and showcase it.  It goes a long way.  As an employer, I no longer asked the question if he/she can do the work.  I think about how else I can use this person within my organization.

Make sure it's polished though.  Have a clear understanding of what you are trying to build that you can describe in one sentence and build it towards that story.  If you can't tell the interviewer what you have done in one sentence, it is too complicated and convoluted!

Good luck job hunting.

David in Vancouver

For your interview, should you dress up or dress down?  Some said to follow the dress code convention of your target employer.  I say to dress smart.  During your initial visit to the office to hand in your cover letter and resume, ask the receptionist what is the standard dress code at work there.  If the dress code is casual, go smart casual.  Nice ironed dress shirt, with a fitted pair of jeans and a suit jacket.  It will give impression that you are easy to approach but not a robot.

For larger organizations, go in a suit and a tie.  Larger = more than 100 people in the organization.  

Another suggestion is to be comfortable in your outfit.  If you are uncomfortable in your outfit, you will be uncomfortable during the interview.  One way to work around this, is to spend a day walking around the business area in your interview outfit.  By spending more time in the outfit, you will feel less self conscious, and more comfortable.  

Good luck job hunting!

David in Vancouver.

This is a continuation of whether or not schooling matters to get a job in information technology.  

Schooling matters until you get your first job.  After that it's all about experience.  In the last post, we talked about how hiring managers get tons of resumes, and you need a way to stand out.  If you don't have the required education, you must make up for it in practical experience.  

This means invest yourself and your time to learn.  Define an interesting, sample project for yourself.  And go ahead and do it.  From my 10+ years of experience in the software industry, I can safely tell you that most things school teach you is useless in your first job.  

Most people learn on the job.  Some excel, while others suffers.  If you want a job.  Learn on your own.  Figure out what your perspective employers are interested in and is doing.  What programming language are they using?  Can you think of a project that you can do, using that language?  Can you enhance their product somehow, or think of creative ways of using their product or services?  Your practical experience will trump any newly minted grad from a university. 

Good luck job hunting.

David in Vancouver