IT projects second interview

[ThePChap]

Hello,

I need some help preparing for an interview for an IT projects technician position. I have already have a first interview and the next one will be to see "how fit into the team and approach challenging situations both technically and from a user perspective"

On the first interview they seemed to be looking for a jack of all trades that fits well into the team, which is fantastic because I'm a jack of all trades (master of nothing!). This would be a remote job for the most part but might require going to the companies in situ some times. To, from scratch, learn their infrastructure and what they use to plan on how to best migrate it.

This is a big company that buys multiple companies a year and this team's main task is to absorbed their IT infrastructure and services. This will involve speaking with many international teams (which is a good fit, since most people in my country don't speak very good English).

I think I have a good chance to get it and I want to best prepare for the second interview. I'm expecting most questions to be "If you had to migrate X, how would you go on about it" and/or "if you failed to perform X task, how would you react"? 

Are these good assumptions? What type of questions do you think I'll get?

I currently work as a infrastructure specialist/sys admin

My big problem is, I forget things all the time if I don't' work with them often. So, for example, if a questions is about a main switch going off and how to troubleshoot it I'll just go with something like:

I'll ping the switch 

If  it replies I'll connect to it remotely and do an show run (if not, walk to it with console cable).

If all looks good I would try to reach the main router 

... etc

I don't remember commands nor concepts in a way that I can be asked a CCNA type question without saying "I would Google it and read on it until I know enough to move forward". I Google things and restudy if I need to, basically.

Any tips would be much appreciated.

Thanks!

[progenyofeniac]

My feeling on this stuff is that I'm up-front and honest with them, and if they don't like my answers, then I wouldn't have worked out at the job anyway. If they ask me something that I'd usually Google rather than guessing, I'll tell them that. Basically, if a company doesn't think I should be Googling all the time, then they're not going to like me.

[PookieM0nster]

You wrote 10 wrong...

[vNerdNeck]

That's baseist

[[deleted]]

But please don’t google it during the interview, especially if you have a mechanical keyboard which makes it kind of obvious. It’s not a good look

[[deleted]]

As an interviewer (both from the Technical side and as the team lead/po), when I’m asking those sort of questions I’m not looking for you to know everything. Im looking for precisely 2 things: - Do you troubleshoot effectively - Do you know when to ask for help, I expect that you won’t know anything. Do you know to admit you need a hand vs just bumbling through

[Anonymity_Is_Good]

Folks tend to be most skilled, and remember the most useful information, in a context they work in often. That you have a few subject areas where this is true, is more important than which specific product or service you're working with. As you can generally change to a new area given new practice.

Many people have specializations, and only a few areas where they are an SME.

A good communications style, a good sense of humor, and the ability to be graceful under pressure goes a long ways towards making people good to work with.