I will not put the questions down as I do not know if they would like that. It really doesn't matter the specifics of the question. They do not all relate with the position you are applying for and even the ones that do, they ask for contradicting pieces of information and you have to determine how to answer both and make sense of them. I believe some of the questions are written by non I.T. professionals, as do not come across as sound.
Casual formalities and greetings. The structural interview was rigid and purely objective, but this is standard procedure because of some lawsuit back in the day. The questions were pretty easy. Describe what happens with this piece of code. Define projects you've completed in the past. Define different software developing architectural patterns...
How would you react if your deadline for a project got extended? They said they had to ask this question, but it was weird because usually a project extension isn't 1) a thing unless you ask for it (it's not usually just handed out) or 2) a problem.
What can you bring to this role.
Technical questions about the position I applied for.
Is this salary range OK?
Would you have any times (evening hours) or dates that you would not be able to work?
Strenths/Weaknesses
Describe a time when you had disagreements with people.
Create a Google Account and set to sync IMAP with OSX Mail.app (timed)
Viewing 681 - 690 interview questions