Tips for interview preparation

[Just4lol]

Hello, I just had a 27m phone interview today and I passed for the final interview. I have 12 days to prepare myself and to learn as much as I can about those tech :

• WCF, MVC, WPF - Only know MVC
• C#, Node.JS - Long time dint do a project with both
• SQL Server, NHibernate - Neaver worked with NHibernate
• HL7 - ?
• Environnement Cloud (AWS, Azure) - ?
• Visual Studio, JIRA, TestRail - TestRaill ?
• Scrum
• JavaScript, CSS3, HTML5, JQuery
• Webstorm, Semantic UI, Handlebars/Mustache - ?
• AngularJS

Link, in french, of the jobs http://www2.softinfo.ca/a-propos/carriere.html#op-122074-dveloppeur-net and http://www2.softinfo.ca/a-propos/carriere.html#op-121899-dveloppeur-web-front-end

I know I don't have to know all that but do you guys have any tips on how to prepare yourself for an interview? It will be my first job in prog  

[cdominic3]

2 minutes ago, Just4lol said:

I know I don't have to know all that but do you guys have any tips on how to prepare yourself for an interview?

Here's a pro tip:

 

Be knowledgeable of what is being asked for you before even applying. You don't have to fake or prepare for anything for the interview if you've already know these things.

[CostcoSamples]

You need to spend some time learning about the company!  

 

There are lots of good interview prep videos on Youtube - check them out.

[Mira Yurizaki]

A few things:

• Know what the company does. It shows you are interested in working for them.
• It'd be good to have something to talk about that's relevant to the position. In my case, I put down "success stories" (basically tasks that brought a lot of value to the company I worked for) in my resume and I talked about what that was in more detail.
• Figure out what you think are the relevant things to know based on the position you applied to. Knowing C is pretty worthless if the job position is a web app developer.
• You don't need to know software development life cycle processes down to a T. Every company does them differently.
• You may be asked to do a code assessment, which is solving a programming problem. Generally they'll be in the language they were looking for on the job posting. Don't worry about what problem they give you and I think it's detrimental to find out what it is. Why? Because they're not testing to see if you can complete the problem or not. They're testing to see how you approach things.
• The final, on-site interview is also a chance to see how well you mesh with the company. First impressions count hugely.

[vorticalbox]

Now a days it seems that so long as you know enough to get to a last interview at that point it's more about whether you'll fit into the team rather than can you do the job, they know you can.

 

I had an interview for a nodejs job half a year a go, I learnt node 1 week before my interview and I was up front about that fact and had a git with a few projects i had wrote in nodejs and asked for feed back.

 

Now I'm writing new platform sections and my own services. Which brings be back to my point. They knew I had programming knowledge just not in node and it was more about if I would get on with the rest of the team.

[wasab]

On 3/7/2018 at 11:11 PM, CostcoSamples said:

You need to spend some time learning about the company!  

 

There are lots of good interview prep videos on Youtube - check them out.

He’s talking about technical interview where HR, probably an expert in the field himself, will be black boarding the interviewees. There is no other way to prepare for it other than the old school method of grinding noses in books and work through example problems as if preparing for an exam.

[Mira Yurizaki]

17 minutes ago, wasab said:

He’s talking about technical interview where HR, probably an expert in the field himself, will be black boarding the interviewees. There is no other way to prepare for it other than the old school method of grinding noses in books and work through example problems as if preparing for an exam.

At my the company I work for now, the first person I spoke to was the group's manager. One of the first things he asked was if I knew what the company does. If you don't know what the company does, to them it shows you're just looking for a job and aren't interested in what the company does. They can infer all sorts of things that can leave a negative impression.

[wasab]

1 hour ago, M.Yurizaki said:

At my the company I work for now, the first person I spoke to was the group's manager. One of the first things he asked was if I knew what the company does. If you don't know what the company does, to them it shows you're just looking for a job and aren't interested in what the company does. They can infer all sorts of things that can leave a negative impression.

That isn’t part of the technical interview. 

[Mira Yurizaki]

6 minutes ago, wasab said:

That isn’t part of the technical interview. 

No, but it is part of the on-site one.

[Just4lol]

14 hours ago, M.Yurizaki said:

At my the company I work for now, the first person I spoke to was the group's manager. One of the first things he asked was if I knew what the company does. If you don't know what the company does, to them it shows you're just looking for a job and aren't interested in what the company does. They can infer all sorts of things that can leave a negative impression.

I already done a 27m phone interview with those kind of question. Ive done some reaserch on the history, product and project they have and what kind of client they are working for. In the end I still realy dont know what technologies I should learn and subjects I need to know for the final interview...

[Just4lol]

14 hours ago, wasab said:

He’s talking about technical interview where HR, probably an expert in the field himself, will be black boarding the interviewees. There is no other way to prepare for it other than the old school method of grinding noses in books and work through example problems as if preparing for an exam.

What do you mean by example problems?

[LAwLz]

What experience and knowledge do you have with web development and .NET right now?

Sounds like you applied for a job you're not all that prepared for.

 

5 hours ago, Just4lol said:

What do you mean by example problems?

He probably means they will ask you "how would you solve this" or "solve this for us" as a test.

For example:

Quote

Write a program that printers the numbers 1 to 100.

Numbers that are multiples of three should print "Fizz" instead of the number.

Numbers that are multiples of five should print "Buzz" instead of the number.

If a number is a multiple of both three and five, "FizzBuzz" should be printed".

 

So the output would look like this:

1

2

Fizz

4

Buzz

Fizz

7

8

Fizz

Buzz

11

Fizz

13

14

FizzBuzz

16

...

[Mira Yurizaki]

6 hours ago, Just4lol said:

I already done a 27m phone interview with those kind of question. Ive done some reaserch on the history, product and project they have and what kind of client they are working for. In the end I still realy dont know what technologies I should learn and subjects I need to know for the final interview...

That's what the job posting is supposed to tell you.

6 hours ago, Just4lol said:

What do you mean by example problems?

Lots of software development interviews will do code assessments by asking you to program something. However, I would advise to not try to find out what they do for assessment. The thing is, it's not really about whether or not you can solve the problem. It's about how you think and tackle the problem.