They began with easy/simple questions and went from there. I found that they can use your answer to generate their next question(s). For example: "name a few algorithms that you know" - sorting, searching... "name a few sorting algorithms" - quick-sort, merge, heap, bubble, radix... "name a few searching algorithm" - linear, binary search... (then they'd ask another question based on the previous answers you just gave). The same rule applied to any hard skill/programming language I had on my resume. They began simple and expanded. If you don't know an answer, simply tell them. Do not try to b.s your way through an answer, it'll be obvious and it'll only hurt your chances. Expect behavioural questions as well. For example "describe to me a time when...", and it could be anything from - you had to work in a difficult team/group or you had to face a challenge and what you did to try to overcome it.
Applications Developer Interview Questions
6,897 applications developer interview questions shared by candidates
Commitment towards the job once selected
Exception class and RuntimeException class is checked or unchecked?
In Python, how does the garbage collector work?
Why did I leave my last job.
Describe a situation when I had to fire someone for a code of ethics violation. I never have and that response led to the question "why?". I've never had anyone violate a code of ethics rule so it has never come up. They seemed to get stuck on that even though this wasn't even a management position making that portion strange.
experience on issue resolving
Indexes in Db2
Discuss how you integrate a payment processing system on a PHP platform site?
Are you familiar with Entity Framework?
Viewing 1421 - 1430 interview questions