[gtyruzzel]

I just today got an interview for a company fairly local to me. This is a role that I am passionate about ( Programming ) and I am obviously very keen to get this job. This however is my first real interview, other jobs I have always come into by chance with no real "interview". It is a Junior role so I believe they are hoping for someone who is passionate rather than having tonnes of relevant experience.

I can read all the guides and tutorials I want but I am after some real world experience of particular styles or things which may come up which potentially may help me along.

So any onions willing to help me get this job and take it into a career?

The interview is with the Senior software developer in a 1 and 1 with no technical questions.

[themsrsdude]

Just gotta climb the corporate ladder on your knees

[feqlmwtuqx]

Have a think about the types of question they might ask and have a vague answer prepared in your head before time.

I have no programming knowledge really but I guess you'd be looking at things like:
"When have you had to come up with a creative solution to a problem?"
"When have you had to work to a tight deadline and how did you deal with it?"
"Have you experienced a situation where you've had a disagreement with someone over a course of action and how did you resolve it?"

Don't come up with answers parrot fashion, just think of a few examples (exaggerate if needed) that could cover those sorts of questions and then just ad-lib if the questions come up. Personally, I'm sure it looks much better to be able to launch into an answer for those sorts of questions rather than sitting around for 30 seconds trying to quickly think of an example.

Also, think ahead to the "negative" type questions that people seem to enjoy asking - greatest weakness, areas that need developing, things like that and make sure you answer them in a way that still sounds positive - I.E suggest it, but follow up by saying how you feel you can make it better and some actions you are taking to improve it.

Although dependant on the company (Size etc) they might not ask any of that and just be using the interview to feel you out and get an idea of your personality etc, never hurts to have an idea of potential answers to those sorts of questions though.

EDIT - and good luck!!

[bellson]

The one question I really hate to get in an interview is:

'What are your weaknesses?'

Awful question and one that can trip you up if you're not prepared.

Think about how you would answer this one.

[Yessaniloas]

The one question I really hate to get in an interview is:

'What are your weaknesses?'

Awful question and one that can trip you up if you're not prepared.

Think about how you would answer this one.

Awful in general or awful for the interviewee? I agree as an interviewee, in that it's a difficult question and I guess awful in that way that pretty much everyone is prepared for it in that they have a canned "positive negative" answer ready. Mine for example is that I am occasionally too single-minded, which can be positive or negative depending on the situation. A bad answer would be something that can only construed as negative, such as being lazy.

As an interviewer, I prefer questions about failed projects or projects that could have been done better. If someone tells me they never had a failed project or any regrets about decisions made then they are full of ****. That question is not all that applicable to a junior position though so I wouldn't worry about it too much.

We always do a code test for our programmer interviews, even juniors, to make sure that the applicants can at least program simple things because a lot of them can't (also in my own experience). If there aren't going to be any technical questions there probably won't be a code test, but it's a good thing to be prepared for.

[Apparpsmose]

The one question I really hate to get in an interview is:

'What are your weaknesses?'

Awful question and one that can trip you up if you're not prepared.

Think about how you would answer this one.

Best answer I have heard and given is:

I'm a bit of a perfectionist, so I sometimes have to remind myself not to spend too much time on things.

Always put a positive spin on a weakness.

[Teligacio]

Best one I have had delivered to me was "I'm a bit of a CU*T. If we can all get over that, it'll be fine".

I think I had possibly made the interview a little too relaxed.

[Nicihntm]

I'm a bit of a perfectionist, so I sometimes have to remind myself not to spend too much time on things.

That's usually what my answer is, it's rather true in my case.

[violetgorman]

When we interview people (IT/Networking/Sys Admin/Exchange/VMware) and notice they write "Expert in" or give the impression they are a guru.... We grab our engineer that specialized in what ever they claim and ask him to ask extremely difficult questions to make the person sink. We hate it when someone claims to know everything about something... We like it when someone states "Working knowledge" on what ever it is they are applying for.

When I do interviews I actually state "I don't know everything and I don't expect my peers/co-workers to know everything. That is why it is so important to have a team full of sharp and experienced members, I know I can be a valuable member to the team with my knowledge and past experiences. I hope to join the team and make it whole as we take on existing and future challenges."

[pobrierce]

We like it when someone states "Working knowledge" on what ever it is they are applying for.

Really?? I want people working for me that are experts in their chosen field! Expert knowledge doesn't mean "I know everything", it means "I can tackle any problem given to me on this subject with the right timescale allowed". Working knowledge means they know how it works theoretically in a lot of cases.

There is something a bit backwards about your approach to hiring people IMHO. But then, there are a million interview techniques and criteria so don't take my opinion in the way that makes you think that I think I know more about your business than you. If it works for you that's all that matters.

[bumxumer]

The interview is with the Senior software developer in a 1 and 1 with no technical questions.

Why have a technical person there if there are no technical questions? I'd be prepared in any case.

[mr.calisto]

Don't be overawed by being the interviewee - remember that you should also be assessing the people interviewing you as well. You should be able to get an idea of not only whether you'd be right for them, but whether they'd be right for you.
Different type of work, but I've had interviews and trials at places where I definitely wouldn't want to work, from those doing the interviewing and/or the work conditions. If you NEED the job, that's one thing, but if you're going to be unhappy and be wanting to leave almost immediately, it'd be a big mistake.

[DoctoBuntonTen]

Really?? I want people working for me that are experts in their chosen field! Expert knowledge doesn't mean "I know everything", it means "I can tackle any problem given to me on this subject with the right timescale allowed". Working knowledge means they know how it works theoretically in a lot of cases.

There is something a bit backwards about your approach to hiring people IMHO. But then, there are a million interview techniques and criteria so don't take my opinion in the way that makes you think that I think I know more about your business than you. If it works for you that's all that matters.

I should have been clearer, we like it when someone states working knowledge and not expert under everything in their resume. If we are looking for a Snr Exchange engineer then we expect them to answer difficult questions related to Exchange. For example we had a guy come in last month for a Snr VMware position and he listed he was an expert in vmware, exchange, AD, windows, and even cisco switches. We grilled his ass with all of our snr engineers... Plus that ******* was chewing gum during the entire interview.
Too many people bullshit on resumes these days... I mean its ok to bullshit on a resume, we all have at one point but these guys bullshit 80% of it and dont have any of the knowledge to go with their claim. Not even general knowledge at times.

[klnbgqr]

Awful in general or awful for the interviewee? I agree as an interviewee, in that it's a difficult question and I guess awful in that way that pretty much everyone is prepared for it in that they have a canned "positive negative" answer ready.

Awful for the interviewee. Trying to highlight your weaknesses whilst making them sound positive and trying not to make it sound too rehearsed and 'canned' is a git to do in my opinion. It's one question I've always struggled to answer well in interviews.

[Onervemurce]

Don't be overawed by being the interviewee - remember that you should also be assessing the people interviewing you as well. You should be able to get an idea of not only whether you'd be right for them, but whether they'd be right for you.
Different type of work, but I've had interviews and trials at places where I definitely wouldn't want to work, from those doing the interviewing and/or the work conditions. If you NEED the job, that's one thing, but if you're going to be unhappy and be wanting to leave almost immediately, it'd be a big mistake.

Mmm you could turn every question back at the interviewer LOL.... So when he asks "so what do you do in your spare time" you go "but what do YOU do in your spare time" "why would you be suitable for this role" you say "but what can YOU do that makes this role suitable for ME"... And do that for every question haha

[venediene]

What I like in interviews is when the person interviewing me talks a lot before I do. I try to get some questions in there really fast to get them to talk a lot about what they do, blah blah blah. Gets me to settle my nerves a little bit and feel a lot more comfortable to talk to someone I have never seen in my life before until that point.

Good luck, dress nice and don't be too worried. I SUCK at interviews and still was able to land a killer job.

[Feelundseenna]

Hmm i can give you a few tips, having been on both sides of the table now.
First of all, a few days before the interview go through your personal data (your curriculum vitae), give it some thought on how you can present it in the best light, so that when asked about it you can roll it out with confidence, whilst highlighting the achievements and circling around the not so good parts (like if you ever got fired before, dropped out of school, whatnot)
To the big day, don´t show up in a Armani suite and crocodile leather shoes if the position you are aiming for isn´t in that league. Dress appropriate to the job you´re wanting to get and dress comfortably, the better you feel in your clothes the better you´ll feel during the interview.
Hmm what else is there to say, of course it´s good to be informed about the company and what it´s main operatives are, what exactly they do, be confident about what you can do, the things and projects you´ve worked on. Know how to sell yourself.
Here are some things i´ve noticed throws interviewers off when i ask them.
(If the Interviewer is married i like to ask): "If i were to call Mrs.XYZ, and would ask her how she would describe her husbands personality and traits, what would she answer?"
Or "If you could change your personal history/development, what would you change?"
another evil one is "Why haven´t you found a job yet?"
Ahh yes don´t be afraid, be confident, don´t let your head hang, try keeping eye contact, don´t be afraid of throwing in a little humor.

There are alot of other things, but my time is limited atm

[nerohedfrs]

I am going over potential questions he may ask me but I guess I just need to make sure I know the background and the main areas of the company and to how to sell myself...

It will be a little difficult since my programming is rather rusty having not programmed full time since well over a year ago. Instead doing smaller bits of XHTML, CSS and smaller bits of PHP in the meanwhile. Which to be honest is rather simple and doesn't stretch the mind with techniques and problem solving...