Interview Advice..

[chemicalNova]

Howdy all,

I was just wondering if any of you could give me interview advice?

I've been programming since I was 11, in various different languages and now have a C++ certificate (Level 4 IT). I've been a Network Engineer for an ISP for just under a year now.. but I really want to be a programmer.. not a network engineer.

I've found a few jobs available to me. I have the certifications and all of the experience required.. but my main concern is the interview. I've never actually been to an interview for a programming job before. What do people expect? Should I take a portfolio? My certificate?

I'm really feeling quite helpless at the moment.. anyone able to give me some advice? If you've had personal experience.. I'd love to hear how you went.

Cheers,

chem

[nemaroller]

Nothing glamorous about programming.
What's wrong with being a network engineer?

Probably pays about the same.

Interviews are all different.

Mainly, don't come across as some lonely sociopath, and you'll do just fine. Eh, you may just want to stay home.

[chemicalNova]

I figure if I've been programming for almost 8 years now and not bored with it.. its probably the career choice for me.

My current job doesn't really keep me entertained.. that, and I'm horribly underpaid

chem

[MaximilianMayrhofer]

the serious tag really does mean serious, nema, even in CC.

As for the interview, definitely bring along a portfolio with all of your certification. A list containing the types of applications you are skilled in coding is also useful. A background in network engineering can be a plus. Explain how it has helped you make your code more efficient and systems-friendly.

If you bring along your laptop, why not compile one of your cooler (but businesslike and functional) apps and then put your laptop to sleep. If you're given the chance, you can just pop open your notebook and give a 30 second introduction to your program and its functionality. Practical examples of your abilities go a lot further than just paper certification.

And don't show an MCP cert if it's more than 1.5 years old.

[penagate]

Sell yourself. Don't just brandish a huge list of portfolio items, but explain exactly how you can be of value to the company. Do some background research on the company if you haven't already; find out what they do (and what tech they use, if possible) — then you can say things like "I can help you with X because I can do Y". It's all very well being impressive, but you've got to hit home at the same time.

[chemicalNova]

Thanks for the replies guys! That really helps me think about what to do.

With the amount of formats I've done.. I don't think I have any fully-functional applications I've written anywhere anymore. I mostly have compiled examples, tutorials I've written, etc, just sitting there..

.. might have to write something.. LOL.

I think I still have my Mario clone from my Game Development Diploma still sitting around.. I think..

Guess I'll see how I go.. cheers again

chem

[timeshifter]

Be confident. I got this job very easily on interviews alone, no certificates and less than a year of professional programming experience. I knew what I was talking about and also showed that I could implement a level of data communication that they hadn't had time to create. A month into the job, and I've already made changes to a couple of programs used by a national retail store, who is starting to go international.

[Shaggy Hiker]

Also keep in mind that studies have shown that for most interviews, the panel knows whether you have a shot in something like the first 15 seconds, which means that they are basing a huge portion of their opinions on a first impression. Get that wrong, and you will have a tough time getting out of the hole you have put yourself in. Therefore, I find myself actually agreeing with TS. Be confident, and if you can't be confident, then for heavens sake ACT confident!

[chemicalNova]

Thing is..

I have a shaved head.. I'm fairly buff.. and I have a few .. scuffle marks here and there. Knowing that, sorta puts me off a bit, thinking that the second I walk in there they'll be like "is this guy for real?".

I just had a 40 minute C++ test over the phone. Man that was interesting.. extremely nervous. Interesting that it was a C++ test for a C# job.. I found that odd..

Doesn't feel like I got anything wrong.. I went and checked googles definition of Polymorphism afterwards to see if I explained it in an understandable way.

..turns out I almost explained it word-for-word, LOL.

chem

[Shaggy Hiker]

With that description, perhaps you could cultivate either a high falsetto voice or a lisp. Either way would have them running for the exits (to some extent, Mike Tyson had both, but I wouldn't be telling him that).

Phone interviews generally suck. That impression can make more difference than knowledge alone. As for physical appearance, I'm not sure how much difference that's going to make, you aren't applying for a position as a model. The stereotype for young coders tends to be something along the punk lines, so I wouldn't think that would hurt you any. I'm a tall, rugged, guy with a bushy red beard, and it hasn't hurt me any in interviews. Clean cut doesn't seem to make much difference, but perhaps it has to do with the type of company.

[szlamany]

Right Said Fred? Or more Midnight Oil??

I've had just about every "physical" form of person work for me that's possible.

Stocky southern boys through eccentric I'm-off-to-India-to-see-my-guru-next-month girls.

The crew-cut quiet guy was a good programmer. As was the long-haired musician one...

I never judge capability on appearance - hopefully any successful firm has the same point of view.

I personally feel the non-technical personality traits are almost more important. The work-ethnic - ability to see something to completion - thoroughness - can you talk to a customer? Can you understand something without being taught? Self-starter? Can you research a problem on vbforum and get an answer?